<?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 21:27:00 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-68389 — Bluetooth: hci_qca: Clear memdump state on invalid dump size</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-68389</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_qca: Clear memdump state on invalid dump size&lt;/p&gt;
&lt;p&gt;qca_controller_memdump() allocates qca-&amp;gt;qca_memdump before processing
the first dump packet. For a sequence-zero packet it then disables IBS,
marks memdump collection active, and reads the advertised dump size.&lt;/p&gt;
&lt;p&gt;If the controller reports a zero dump size, the error path frees the
local qca_memdump object and returns without clearing qca-&amp;gt;qca_memdump
or undoing the collection state. A later memdump work item initializes
its local pointer from qca-&amp;gt;qca_memdump and skips allocation when that
pointer is non-NULL, so it can operate on freed memory. The stale
collection and IBS-disabled flags can also leave waiters or later
transmit handling blocked behind an aborted dump.&lt;/p&gt;
&lt;p&gt;Clear the saved pointer and memdump state before returning from the
invalid-size path, matching the cleanup used when hci_devcd_init() fails.&lt;/p&gt;
&lt;p&gt;A static analysis checker reported the stale memdump state, and manual
source review confirmed the invalid-size failure path.&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_qca: Clear memdump state on invalid dump size&lt;/p&gt;
&lt;p&gt;qca_controller_memdump() allocates qca-&amp;gt;qca_memdump before processing
the first dump packet. For a sequence-zero packet it then disables IBS,
marks memdump collection active, and reads the advertised dump size.&lt;/p&gt;
&lt;p&gt;If the controller reports a zero dump size, the error path frees the
local qca_memdump object and returns without clearing qca-&amp;gt;qca_memdump
or undoing the collection state. A later memdump work item initializes
its local pointer from qca-&amp;gt;qca_memdump and skips allocation when that
pointer is non-NULL, so it can operate on freed memory. The stale
collection and IBS-disabled flags can also leave waiters or later
transmit handling blocked behind an aborted dump.&lt;/p&gt;
&lt;p&gt;Clear the saved pointer and memdump state before returning from the
invalid-size path, matching the cleanup used when hci_devcd_init() fails.&lt;/p&gt;
&lt;p&gt;A static analysis checker reported the stale memdump state, and manual
source review confirmed the invalid-size failure path.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-68389</guid>
    </item>
  </channel>
</rss>
