CVE-2026-99015 — Bluetooth: hci_sock: Serialize dead-device detachment
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+1
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ 4.4.281 and < 4.5≥ 5.10.58 and < 5.10.273≥ e04480920d1eec9c061841399aa6f35b6f987d8b and < 362126f739889436048f5573ebc87466d2525fd9≥ e04480920d1eec9c061841399aa6f35b6f987d8b and < 304adbdb96b0491c2b377e216b0bf417fc8e69a9≥ f2f856b65ac4b77049c76c0e89ecd3a177e9fcd1 and < 88f47e66b1a6e0bfc350676937f3b552b434e74cversion 5.14≥ 5.13.10 and < 5.14≥ 5.4.140 and < 5.5 and 14 more≥ 4.19.203 and < 4.20≥ 4.14.244 and < 4.15≥ 4.9.280 and < 4.10≥ e04480920d1eec9c061841399aa6f35b6f987d8b and < 37cef0c8fb537f40600910d2c2e5f2d5509305f3version 75dd00b755ebfa9b24eaedc9f42e9adfc00ae00cversion ff29fe26ab8679bc13a3f0bf5b2911535a1cfc35version 3719acc161d5c1ce09912cc1c9eddc2c5faa3c66version 0782c8c7f80c9dd457acdfe16fd0f339f0e73093version 0e77f979a97d3d517fad0b51249ba6fb8ae2d365version d6ef8bb00aa65eceb413fc165a55086459863e38≥ e04480920d1eec9c061841399aa6f35b6f987d8b and < 381a0925c556a8d91a80a9b9e3e86651d60ffee3≥ e04480920d1eec9c061841399aa6f35b6f987d8b and < e660a22402944f2615a16fde7129a3c497537329≥ e04480920d1eec9c061841399aa6f35b6f987d8b and < c3d2799877906d0c8392d96e14216cd82b020330≥ e04480920d1eec9c061841399aa6f35b6f987d8b and < 76f2e2665697340ac719e7ff1bf148dd014e55c1 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 24, 2026 → Oct 30, 2026 · 7 reading(s) · max 0.21%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products removed · 2
- Affected products added · linux/linux
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 3× References added · Oct 23, 2026 – Oct 30, 2026
- 1× Official description updated · Oct 23, 2026 – Oct 23, 2026
References
10 on the record
- github.com/advisories/GHSA-fj4j-9cqw-5cxw
- git.kernel.org/stable/c/362126f739889436048f5573ebc87466d2525fd9
- git.kernel.org/stable/c/c3d2799877906d0c8392d96e14216cd82b020330
- git.kernel.org/stable/c/e660a22402944f2615a16fde7129a3c497537329
- git.kernel.org/stable/c/88f47e66b1a6e0bfc350676937f3b552b434e74c
- git.kernel.org/stable/c/304adbdb96b0491c2b377e216b0bf417fc8e69a9
- git.kernel.org/stable/c/37cef0c8fb537f40600910d2c2e5f2d5509305f3
- git.kernel.org/stable/c/76f2e2665697340ac719e7ff1bf148dd014e55c1
- nvd.nist.gov/vuln/detail/CVE-2026-99015
- git.kernel.org/stable/c/381a0925c556a8d91a80a9b9e3e86651d60ffee3
Elsewhere on this site
Related CVEs (same products)
- Unknown CVE-2026-99216 Drivers: hv: Don't reset VMBus connection state on error/exit paths 2d
- Unknown CVE-2026-99215 power: supply: core: prevent unregistering a power supply while a callback runs 2d
- Unknown CVE-2026-99207 scsi: target: Disable interrupts while holding delayed_cmd_lock 2d
- Unknown CVE-2026-99208 drm/xe/oa: Zero OA buffer at allocation 2d
- Unknown CVE-2026-99209 drm/xe: skip eviction of a BO with no resource 2d
- Unknown CVE-2026-99210 accel/rocket: clear rdev on device init failure 2d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-99015 is "Bluetooth: hci_sock: Serialize dead-device detachment", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.17% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.