CVE-2026-68389Bluetooth: hci_qca: Clear memdump state on invalid dump size
- 8.8HighCVSS base score
- 0.25%Exploitation in 30 daysEPSS · top 83% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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.
Timeline
ID reserved
By Linux
- 11 days later
· 11 days later
Published
- 7 days later
· 7 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High8.8 | CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Received | 3.1 | High8.8 | CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.25% · top 83% of all CVEs (17 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.8.
Affected products
- affected 06d3fdfcdf5cefb06f2024b9d3dad356779399cf – < 5a3945e8dea6c9a8ec9e981169ac9487e1d6ad6a
- affected 06d3fdfcdf5cefb06f2024b9d3dad356779399cf – < 069258d5111eed9ac9586bee42d03d38e2975715
- affected 06d3fdfcdf5cefb06f2024b9d3dad356779399cf – < cefb44c367b2b52e50f97bc8526d39df9bcf5e60
- affected 06d3fdfcdf5cefb06f2024b9d3dad356779399cf – < 2363a757694752426fc47f3eadde15cf5f791fa5
- affected 06d3fdfcdf5cefb06f2024b9d3dad356779399cf – < bf587a10c33e5571a299742e45bc18960b9912e7
- affected 6.6
- unaffected < 6.6
- unaffected 6.6.148 – ≤ 6.6.*
- unaffected 6.12.101 – ≤ 6.12.*
- unaffected 6.18.42 – ≤ 6.18.*
- unaffected 7.1.6 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References5
- https://git.kernel.org/stable/c/5a3945e8dea6c9a8ec9e981169ac9487e1d6ad6a (opens in a new tab)
- https://git.kernel.org/stable/c/069258d5111eed9ac9586bee42d03d38e2975715 (opens in a new tab)
- https://git.kernel.org/stable/c/cefb44c367b2b52e50f97bc8526d39df9bcf5e60 (opens in a new tab)
- https://git.kernel.org/stable/c/2363a757694752426fc47f3eadde15cf5f791fa5 (opens in a new tab)
- https://git.kernel.org/stable/c/bf587a10c33e5571a299742e45bc18960b9912e7 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-55575 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-68389)Record last updated .