CVE-2026-68389
Last modified
CVE-2026-68389 is a vulnerability of currently unknown severity. 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.
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.
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 06d3fdfcdf5cefb06f2024b9d3dad356779399cf, < 5a3945e8dea6c9a8ec9e981169ac9487e1d6ad6a; >= 06d3fdfcdf5cefb06f2024b9d3dad356779399cf, < 069258d5111eed9ac9586bee42d03d38e2975715; >= 06d3fdfcdf5cefb06f2024b9d3dad356779399cf, < cefb44c367b2b52e50f97bc8526d39df9bcf5e60; >= 06d3fdfcdf5cefb06f2024b9d3dad356779399cf, < 2363a757694752426fc47f3eadde15cf5f791fa5; >= 06d3fdfcdf5cefb06f2024b9d3dad356779399cf, < bf587a10c33e5571a299742e45bc18960b9912e7 |
| Linux | Linux | 6.6 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-68389?
How severe is CVE-2026-68389?
How do I fix CVE-2026-68389?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-68383In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68384In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68385In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68386In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68387In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68388In the Linux kernel, the following vulnerability has been re…
- CVE-2026-6839Improper validation of STRING tensor offsets could allows ma…6.6
- CVE-2026-68390In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68391In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68392In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68393In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68394In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-68389?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
