<?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>Tue, 29 Sep 2026 04:52:57 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-64404 — Bluetooth: ISO: avoid NULL deref of conn in iso_conn_big_sync()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-64404</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: avoid NULL deref of conn in iso_conn_big_sync()&lt;/p&gt;
&lt;p&gt;iso_conn_big_sync() drops the socket lock to call hci_get_route() and
then re-acquires it, but dereferences iso_pi(sk)-&amp;gt;conn-&amp;gt;hcon afterwards
without re-checking that conn is still valid.&lt;/p&gt;
&lt;p&gt;While the lock is dropped, the connection can be torn down under the
same socket lock: iso_disconn_cfm() -&amp;gt; iso_conn_del() -&amp;gt; iso_chan_del()
sets iso_pi(sk)-&amp;gt;conn to NULL (and the broadcast teardown path can also
clear conn-&amp;gt;hcon on its own). When iso_conn_big_sync() re-acquires the
lock and reads conn-&amp;gt;hcon, conn may be NULL, causing a NULL pointer
dereference (hcon is the first member of struct iso_conn).&lt;/p&gt;
&lt;p&gt;This path is reached from iso_sock_recvmsg() for a PA-sync broadcast
sink socket (BT_SK_DEFER_SETUP | BT_SK_PA_SYNC), so the dropped-lock
window can race with connection teardown driven by controller events.&lt;/p&gt;
&lt;p&gt;Re-validate iso_pi(sk)-&amp;gt;conn and its hcon after re-acquiring the socket
lock and bail out if the connection went away, as already done in the
sibling iso_sock_rebind_bc().&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: avoid NULL deref of conn in iso_conn_big_sync()&lt;/p&gt;
&lt;p&gt;iso_conn_big_sync() drops the socket lock to call hci_get_route() and
then re-acquires it, but dereferences iso_pi(sk)-&amp;gt;conn-&amp;gt;hcon afterwards
without re-checking that conn is still valid.&lt;/p&gt;
&lt;p&gt;While the lock is dropped, the connection can be torn down under the
same socket lock: iso_disconn_cfm() -&amp;gt; iso_conn_del() -&amp;gt; iso_chan_del()
sets iso_pi(sk)-&amp;gt;conn to NULL (and the broadcast teardown path can also
clear conn-&amp;gt;hcon on its own). When iso_conn_big_sync() re-acquires the
lock and reads conn-&amp;gt;hcon, conn may be NULL, causing a NULL pointer
dereference (hcon is the first member of struct iso_conn).&lt;/p&gt;
&lt;p&gt;This path is reached from iso_sock_recvmsg() for a PA-sync broadcast
sink socket (BT_SK_DEFER_SETUP | BT_SK_PA_SYNC), so the dropped-lock
window can race with connection teardown driven by controller events.&lt;/p&gt;
&lt;p&gt;Re-validate iso_pi(sk)-&amp;gt;conn and its hcon after re-acquiring the socket
lock and bail out if the connection went away, as already done in the
sibling iso_sock_rebind_bc().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-64404</guid>
    </item>
  </channel>
</rss>
