<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Thu, 01 Oct 2026 10:21:41 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-56694 — bpf: fix recursive lock when verdict program return SK_PASS</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-56694</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bpf: fix recursive lock when verdict program return SK_PASS&lt;/p&gt;
&lt;p&gt;When the stream_verdict program returns SK_PASS, it places the received skb
into its own receive queue, but a recursive lock eventually occurs, leading
to an operating system deadlock. This issue has been present since v6.9.&lt;/p&gt;
&lt;p&gt;&amp;#39;&amp;#39;&amp;#39;
sk_psock_strp_data_ready
    write_lock_bh(&amp;amp;sk-&amp;gt;sk_callback_lock)
    strp_data_ready
      strp_read_sock
        read_sock -&amp;gt; tcp_read_sock
          strp_recv
            cb.rcv_msg -&amp;gt; sk_psock_strp_read
              # now stream_verdict return SK_PASS without peer sock assign
              __SK_PASS = sk_psock_map_verd(SK_PASS, NULL)
              sk_psock_verdict_apply
                sk_psock_skb_ingress_self
                  sk_psock_skb_ingress_enqueue
                    sk_psock_data_ready
                      read_lock_bh(&amp;amp;sk-&amp;gt;sk_callback_lock) &amp;lt;= dead lock&lt;/p&gt;
&lt;p&gt;&amp;#39;&amp;#39;&amp;#39;&lt;/p&gt;
&lt;p&gt;This topic has been discussed before, but it has not been fixed.
Previous discussion:
https://lore.kernel.org/all/6684a5864ec86_403d20898@john.notmuch&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bpf: fix recursive lock when verdict program return SK_PASS&lt;/p&gt;
&lt;p&gt;When the stream_verdict program returns SK_PASS, it places the received skb
into its own receive queue, but a recursive lock eventually occurs, leading
to an operating system deadlock. This issue has been present since v6.9.&lt;/p&gt;
&lt;p&gt;&amp;#39;&amp;#39;&amp;#39;
sk_psock_strp_data_ready
    write_lock_bh(&amp;amp;sk-&amp;gt;sk_callback_lock)
    strp_data_ready
      strp_read_sock
        read_sock -&amp;gt; tcp_read_sock
          strp_recv
            cb.rcv_msg -&amp;gt; sk_psock_strp_read
              # now stream_verdict return SK_PASS without peer sock assign
              __SK_PASS = sk_psock_map_verd(SK_PASS, NULL)
              sk_psock_verdict_apply
                sk_psock_skb_ingress_self
                  sk_psock_skb_ingress_enqueue
                    sk_psock_data_ready
                      read_lock_bh(&amp;amp;sk-&amp;gt;sk_callback_lock) &amp;lt;= dead lock&lt;/p&gt;
&lt;p&gt;&amp;#39;&amp;#39;&amp;#39;&lt;/p&gt;
&lt;p&gt;This topic has been discussed before, but it has not been fixed.
Previous discussion:
https://lore.kernel.org/all/6684a5864ec86_403d20898@john.notmuch&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-56694</guid>
    </item>
  </channel>
</rss>
