CVE detail
CVE-2026-68389
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_qca: Clear memdump state on invalid dump size qca_controller_memdump() allocates qca->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. If the controller reports a zero dump size, the error path frees the local qca_memdump object and returns without clearing qca->qca_memdump or undoing the collection state. A later memdump work item initializes its local pointer from qca->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. Clear the saved pointer and memdump state before returning from the invalid-size path, matching the cleanup used when hci_devcd_init() fails. A static analysis checker reported the stale memdump state, and manual source review confirmed the invalid-size failure path.
Buzz score
Why this CVE is surfacing
This all-time snapshot uses the same composite formula as Trending across a 30-year evidence window, rather than a current rolling window.
Buzz score components · mention 19.5 · diversity 10.0 · KEV 0.0 · OTX 0.0 · PoC 0.0
Why it matters now
Mention timeline
- Total mentions
- 6
- within the 30d window
- Peak daily
- 5
- highest bucket
Evidence
Source links by recency
6 source links · newest first
Information published.
vendormsrc.microsoft.comAug 11, 2026, 8:10 AMNo excerpt available.
Exploitgit.kernel.orgAug 10, 2026, 1:20 PMNo excerpt available.
Exploitgit.kernel.orgAug 10, 2026, 1:20 PMNo excerpt available.
Exploitgit.kernel.orgAug 10, 2026, 1:20 PMNo excerpt available.
Exploitgit.kernel.orgAug 10, 2026, 1:20 PMNo excerpt available.
Exploitgit.kernel.orgAug 10, 2026, 1:20 PM
Exploit code
Public exploit repository references
Public PoC repositories are third-party, potentially unsafe artifacts. Treat their code as untrusted and use it only on authorized systems in an isolated, least-privilege environment. cvebuzz does not execute the code or verify that an exploit works.