Adjacent kernel memory corruption via stale memdump pointer
Published Aug 10, 2026 · Updated Aug 10, 2026
Use-after-free in the Linux kernel hci_qca Bluetooth driver allows adjacent attackers to corrupt kernel memory via crafted HCI events. On a sequence-zero memdump packet advertising a zero size, qca_controller_memdump() frees qca->qca_memdump but leaves the saved pointer and collection state intact, so later work dereferences freed memory. An attacker controlling the controller-to-host HCI stream after a firmware crash can disclose or overwrite kernel memory, hijack control flow, or persistently wedge Bluetooth handling without host credentials or user interaction.
Summary
What happened
Use-after-free in the Linux kernel hci_qca Bluetooth driver allows adjacent attackers to corrupt kernel memory via crafted HCI events. On a sequence-zero memdump packet advertising a zero size, qca_controller_memdump() frees qca->qca_memdump but leaves the saved pointer and collection state intact, so later work dereferences freed memory. An attacker controlling the controller-to-host HCI stream after a firmware crash can disclose or overwrite kernel memory, hijack control flow, or persistently wedge Bluetooth handling without host credentials or user interaction.
The record
- CVE
- CVE-2026-68389
- Published
- Aug 10, 2026
- Updated
- Aug 10, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-825, T1203
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 10, 2026CVE publishedPublication date reported by the CVE source.
- Aug 10, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=06d3fdfcdf5cefb06f2024b9d3dad356779399cf <069258d5111eed9ac9586bee42d03d38e2975715
- Affected versionversion=06d3fdfcdf5cefb06f2024b9d3dad356779399cf <2363a757694752426fc47f3eadde15cf5f791fa5
- Affected versionversion=06d3fdfcdf5cefb06f2024b9d3dad356779399cf <5a3945e8dea6c9a8ec9e981169ac9487e1d6ad6a
- Affected versionversion=06d3fdfcdf5cefb06f2024b9d3dad356779399cf <bf587a10c33e5571a299742e45bc18960b9912e7
- Affected versionversion=06d3fdfcdf5cefb06f2024b9d3dad356779399cf <cefb44c367b2b52e50f97bc8526d39df9bcf5e60
- Affected versionversion=6.6
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo