CVE-2026-99015Bluetooth: hci_sock: Serialize dead-device detachment
- —Not scoredno CVSS score yet
- 0.18%Exploitation in 30 daysEPSS · top 93% 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_sock: Serialize dead-device detachment Rebinding an HCI socket after its controller is unregistered can race monitor control replay and crash the kernel. hci_sock_bind() clears hci_pi(sk)->hdev and drops the device reference under only the socket lock, whereas send_monitor_control_replay() holds hci_sk_list.lock for reading. Replay can observe a non-NULL hdev, then bind can clear it and drop the last reference before create_monitor_ctrl_open() reads hdev->id. This can cause a NULL pointer dereference if the pointer is reloaded, or a use-after-free if the old pointer is retained. The kernel reported: KASAN: null-ptr-deref in range [0x0000000000000068-0x000000000000006f] RIP: 0010:create_monitor_ctrl_open+0x579/0x800 Call Trace: hci_sock_bind+0xd96/0x1190 __sys_bind+0x166/0x200 __x64_sys_bind+0x6d/0xb0 do_syscall_64+0xdd/0x4a0 entry_SYSCALL_64_after_hwframe+0x77/0x7f The same missing serialization lets hci_send_to_sock() select a socket for the old device and queue its frame after bind has detached the socket or installed a new binding. Take hci_sk_list.lock for writing when clearing the device pointer and resetting the socket state. This waits for existing replay and delivery readers to finish before detachment and prevents later readers from using the old binding. Keep hci_dev_put() outside the critical section because the final device release can sleep.
Timeline
ID reserved
By Linux
- 28 days later
· 28 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
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.18% · top 93% of all CVEs (12 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected f2f856b65ac4b77049c76c0e89ecd3a177e9fcd1 – < 88f47e66b1a6e0bfc350676937f3b552b434e74c
- affected e04480920d1eec9c061841399aa6f35b6f987d8b – < 304adbdb96b0491c2b377e216b0bf417fc8e69a9
- affected e04480920d1eec9c061841399aa6f35b6f987d8b – < 362126f739889436048f5573ebc87466d2525fd9
- affected e04480920d1eec9c061841399aa6f35b6f987d8b – < 37cef0c8fb537f40600910d2c2e5f2d5509305f3
- affected e04480920d1eec9c061841399aa6f35b6f987d8b – < 76f2e2665697340ac719e7ff1bf148dd014e55c1
- affected e04480920d1eec9c061841399aa6f35b6f987d8b – < c3d2799877906d0c8392d96e14216cd82b020330
- affected e04480920d1eec9c061841399aa6f35b6f987d8b – < e660a22402944f2615a16fde7129a3c497537329
- affected e04480920d1eec9c061841399aa6f35b6f987d8b – < 381a0925c556a8d91a80a9b9e3e86651d60ffee3
- affected d6ef8bb00aa65eceb413fc165a55086459863e38
- affected 0e77f979a97d3d517fad0b51249ba6fb8ae2d365
- affected 0782c8c7f80c9dd457acdfe16fd0f339f0e73093
- affected 3719acc161d5c1ce09912cc1c9eddc2c5faa3c66
- affected ff29fe26ab8679bc13a3f0bf5b2911535a1cfc35
- affected 75dd00b755ebfa9b24eaedc9f42e9adfc00ae00c
- affected 5.10.58 – < 5.10.273
- affected 4.4.281 – < 4.5
- affected 4.9.280 – < 4.10
- affected 4.14.244 – < 4.15
- affected 4.19.203 – < 4.20
- affected 5.4.140 – < 5.5
- affected 5.13.10 – < 5.14
- affected 5.14
- unaffected < 5.14
- unaffected 5.10.273 – ≤ 5.10.*
- unaffected 5.15.224 – ≤ 5.15.*
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.160 – ≤ 6.6.*
- unaffected 6.12.113 – ≤ 6.12.*
- unaffected 6.18.57 – ≤ 6.18.*
- unaffected 7.2.11 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References8
- https://git.kernel.org/stable/c/88f47e66b1a6e0bfc350676937f3b552b434e74c (opens in a new tab)
- https://git.kernel.org/stable/c/304adbdb96b0491c2b377e216b0bf417fc8e69a9 (opens in a new tab)
- https://git.kernel.org/stable/c/362126f739889436048f5573ebc87466d2525fd9 (opens in a new tab)
- https://git.kernel.org/stable/c/37cef0c8fb537f40600910d2c2e5f2d5509305f3 (opens in a new tab)
- https://git.kernel.org/stable/c/76f2e2665697340ac719e7ff1bf148dd014e55c1 (opens in a new tab)
- https://git.kernel.org/stable/c/c3d2799877906d0c8392d96e14216cd82b020330 (opens in a new tab)
- https://git.kernel.org/stable/c/e660a22402944f2615a16fde7129a3c497537329 (opens in a new tab)
- https://git.kernel.org/stable/c/381a0925c556a8d91a80a9b9e3e86651d60ffee3 (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-108809 (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-99015)Record last updated .