CVE-2026-99015 Bluetooth: hci_sock: Serialize dead-device detachment
- Exploited in the wild
- Not known
- Fix
- Available
What is CVE-2026-99015?
CVE-2026-99015 is a vulnerability in Linux, published on 23 Oct 2026.
Official 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.
Which versions are affected by CVE-2026-99015?
How do I fix CVE-2026-99015?
Upgrade to a fixed version.
Is CVE-2026-99015 being exploited?
There is no known exploitation of CVE-2026-99015 in the wild and no public exploit code.
Sources
Also known as AZL-110864, BELL-CVE-2026-99015, DEBIAN-CVE-2026-99015, GHSA-fj4j-9cqw-5cxw, UBUNTU-CVE-2026-99015.