<?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>Fri, 02 Oct 2026 01:49:04 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-74537 — Bluetooth: ISO: hold sk properly in iso_conn_ready</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-74537</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;Bluetooth: ISO: hold sk properly in iso_conn_ready&lt;/p&gt;
&lt;p&gt;sk deref in iso_conn_ready must be done either under conn-&amp;gt;lock, or
holding a refcount, to avoid concurrent close. conn-&amp;gt;sk is currently
accessed without either:&lt;/p&gt;
&lt;p&gt;[Task 1]            [Task 2]
                        iso_sock_release
    iso_conn_ready
      sk = conn-&amp;gt;sk
                          lock_sock(sk)
                            conn-&amp;gt;sk = NULL
      lock_sock(sk)
                          release_sock(sk)
                          iso_sock_kill(sk)
       UAF on sk deref&lt;/p&gt;
&lt;p&gt;Fix possible UAF by holding sk refcount in iso_conn_ready().  Also
recheck after lock_sock that the socket is still valid.  Adjust locking
so conn-&amp;gt;sk is cleared only under lock_sock.&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;Bluetooth: ISO: hold sk properly in iso_conn_ready&lt;/p&gt;
&lt;p&gt;sk deref in iso_conn_ready must be done either under conn-&amp;gt;lock, or
holding a refcount, to avoid concurrent close. conn-&amp;gt;sk is currently
accessed without either:&lt;/p&gt;
&lt;p&gt;[Task 1]            [Task 2]
                        iso_sock_release
    iso_conn_ready
      sk = conn-&amp;gt;sk
                          lock_sock(sk)
                            conn-&amp;gt;sk = NULL
      lock_sock(sk)
                          release_sock(sk)
                          iso_sock_kill(sk)
       UAF on sk deref&lt;/p&gt;
&lt;p&gt;Fix possible UAF by holding sk refcount in iso_conn_ready().  Also
recheck after lock_sock that the socket is still valid.  Adjust locking
so conn-&amp;gt;sk is cleared only under lock_sock.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-74537</guid>
    </item>
  </channel>
</rss>
