<?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 05:40:20 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-90255 — Bluetooth: hci_conn: fix the SCO setup context lifetime</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-90255</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: hci_conn: fix the SCO setup context lifetime&lt;/p&gt;
&lt;p&gt;hci_setup_sync() queues a conn_handle_t with a NULL destroy callback, so
the context is only freed if hci_enhanced_setup_sync() actually runs. An
entry that is cancelled instead is leaked, as
_hci_cmd_sync_cancel_entry() does not release entry-&amp;gt;data when there is
no destroy callback, and hci_cmd_sync_clear() cancels every pending entry
when the controller is unregistered.&lt;/p&gt;
&lt;p&gt;The context also stores a bare hci_conn pointer, so the connection can be
freed while the work is queued. The dequeue in hci_conn_del() does not
cover it either, as it matches on entry-&amp;gt;data == conn and entry-&amp;gt;data is
the wrapper here. Same problem as commit 2f5d635ad590 (&amp;#34;Bluetooth:
hci_sync: hold conn in hci_connect_acl/le_sync() callbacks&amp;#34;).&lt;/p&gt;
&lt;p&gt;Hold the connection and release both from a destroy callback. The
submission failure path drops both, since hci_cmd_sync_submit() does not
call the destroy callback when it fails to queue.&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: hci_conn: fix the SCO setup context lifetime&lt;/p&gt;
&lt;p&gt;hci_setup_sync() queues a conn_handle_t with a NULL destroy callback, so
the context is only freed if hci_enhanced_setup_sync() actually runs. An
entry that is cancelled instead is leaked, as
_hci_cmd_sync_cancel_entry() does not release entry-&amp;gt;data when there is
no destroy callback, and hci_cmd_sync_clear() cancels every pending entry
when the controller is unregistered.&lt;/p&gt;
&lt;p&gt;The context also stores a bare hci_conn pointer, so the connection can be
freed while the work is queued. The dequeue in hci_conn_del() does not
cover it either, as it matches on entry-&amp;gt;data == conn and entry-&amp;gt;data is
the wrapper here. Same problem as commit 2f5d635ad590 (&amp;#34;Bluetooth:
hci_sync: hold conn in hci_connect_acl/le_sync() callbacks&amp;#34;).&lt;/p&gt;
&lt;p&gt;Hold the connection and release both from a destroy callback. The
submission failure path drops both, since hci_cmd_sync_submit() does not
call the destroy callback when it fails to queue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-90255</guid>
    </item>
  </channel>
</rss>
