Kernel crash via Bluetooth device use-after-free
Published Apr 4, 2024 · Updated Aug 5, 2026
Use-after-free in the Linux kernel Bluetooth subsystem allows local users to crash the kernel during an unresponsive controller reset. HCI hardware-error handling invokes GPIO reset, which can release hci_dev while hci_error_reset is still using it because event processing does not hold a device reference. Reachability requires an HCI hardware-error event and an unresponsive Bluetooth controller; the bounded impact reported by Linux is a kernel crash.
Summary
What happened
Use-after-free in the Linux kernel Bluetooth subsystem allows local users to crash the kernel during an unresponsive controller reset. HCI hardware-error handling invokes GPIO reset, which can release hci_dev while hci_error_reset is still using it because event processing does not hold a device reference. Reachability requires an HCI hardware-error event and an unresponsive Bluetooth controller; the bounded impact reported by Linux is a kernel crash.
The record
- CVE
- CVE-2024-26801
- Published
- Apr 4, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-416, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 4, 2024CVE publishedPublication date reported by the CVE source.
- Aug 5, 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=4.0
- Affected versionversion=c7741d16a57cbf97eebe53f27e8216b1ff20e20c <2449007d3f73b2842c9734f45f0aadb522daf592
- Affected versionversion=c7741d16a57cbf97eebe53f27e8216b1ff20e20c <2ab9a19d896f5a0dd386e1f001c5309bc35f433b
- Affected versionversion=c7741d16a57cbf97eebe53f27e8216b1ff20e20c <45085686b9559bfbe3a4f41d3d695a520668f5e1
- Affected versionversion=c7741d16a57cbf97eebe53f27e8216b1ff20e20c <6dd0a9dfa99f8990a08eb8fdd8e79bee31c7d8e2
- Affected versionversion=c7741d16a57cbf97eebe53f27e8216b1ff20e20c <98fb98fd37e42fd4ce13ff657ea64503e24b6090
- Affected versionversion=c7741d16a57cbf97eebe53f27e8216b1ff20e20c <da4569d450b193e39e87119fd316c0291b585d14
- Affected versionversion=c7741d16a57cbf97eebe53f27e8216b1ff20e20c <dd594cdc24f2e48dab441732e6dfcafd6b0711d1
- Affected versionversion=c7741d16a57cbf97eebe53f27e8216b1ff20e20c <e0b278650f07acf2e0932149183458468a731c03
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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