Kernel crash via Bluetooth socket detachment race
Published Oct 23, 2026 · Updated Oct 23, 2026
Linux Bluetooth HCI socket code allows local users to crash the kernel via a rebinding race after controller removal. The hci_sock_bind() function clears the device pointer and releases its reference without synchronizing with monitor replay, leaving create_monitor_ctrl_open() to dereference a null or freed device. Triggering requires an existing HCI binding, controller unregistration, and concurrent monitor replay; the disclosed evidence establishes a kernel crash, not code execution.
Summary
What happened
Linux Bluetooth HCI socket code allows local users to crash the kernel via a rebinding race after controller removal. The hci_sock_bind() function clears the device pointer and releases its reference without synchronizing with monitor replay, leaving create_monitor_ctrl_open() to dereference a null or freed device. Triggering requires an existing HCI binding, controller unregistration, and concurrent monitor replay; the disclosed evidence establishes a kernel crash, not code execution.
The record
- CVE
- CVE-2026-99015
- Published
- Oct 23, 2026
- Updated
- Oct 23, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 23, 2026CVE publishedPublication date reported by the CVE source.
- Oct 23, 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=0782c8c7f80c9dd457acdfe16fd0f339f0e73093
- Affected versionversion=0e77f979a97d3d517fad0b51249ba6fb8ae2d365
- Affected versionversion=3719acc161d5c1ce09912cc1c9eddc2c5faa3c66
- Affected versionversion=4.14.244 <4.15
- Affected versionversion=4.19.203 <4.20
- Affected versionversion=4.4.281 <4.5
- Affected versionversion=4.9.280 <4.10
- Affected versionversion=5.10.58 <5.11
- Affected versionversion=5.13.10 <5.14
- Affected versionversion=5.14
- Affected versionversion=5.4.140 <5.5
- Affected versionversion=75dd00b755ebfa9b24eaedc9f42e9adfc00ae00c
- Affected versionversion=d6ef8bb00aa65eceb413fc165a55086459863e38
- Affected versionversion=e04480920d1eec9c061841399aa6f35b6f987d8b <37cef0c8fb537f40600910d2c2e5f2d5509305f3
- Affected versionversion=e04480920d1eec9c061841399aa6f35b6f987d8b <381a0925c556a8d91a80a9b9e3e86651d60ffee3
- Affected versionversion=e04480920d1eec9c061841399aa6f35b6f987d8b <76f2e2665697340ac719e7ff1bf148dd014e55c1
- Affected versionversion=e04480920d1eec9c061841399aa6f35b6f987d8b <c3d2799877906d0c8392d96e14216cd82b020330
- Affected versionversion=e04480920d1eec9c061841399aa6f35b6f987d8b <e660a22402944f2615a16fde7129a3c497537329
- Affected versionversion=f2f856b65ac4b77049c76c0e89ecd3a177e9fcd1
- Affected versionversion=ff29fe26ab8679bc13a3f0bf5b2911535a1cfc35
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
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.
Activity data is delayed. The latest report is Sep 28, 2026.
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Contact us