<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-29T22:06:25.690096+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2026-68389</id>
    <title>CVE-2026-68389 — Bluetooth: hci_qca: Clear memdump state on invalid dump size</title>
    <updated>2026-09-29T22:06:26.383546+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>Bluetooth: hci_qca: Clear memdump state on invalid dump size</p>
<p>qca_controller_memdump() allocates qca-&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.</p>
<p>If the controller reports a zero dump size, the error path frees the
local qca_memdump object and returns without clearing qca-&gt;qca_memdump
or undoing the collection state. A later memdump work item initializes
its local pointer from qca-&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.</p>
<p>Clear the saved pointer and memdump state before returning from the
invalid-size path, matching the cleanup used when hci_devcd_init() fails.</p>
<p>A static analysis checker reported the stale memdump state, and manual
source review confirmed the invalid-size failure path.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-68389"/>
  </entry>
</feed>
