Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-98737 Overview
CVE-2026-98737 is a use-after-free vulnerability in the Linux kernel Bluetooth subsystem. The flaw resides in the hci_sync command worker, which accesses inquiry-cache entries without holding hdev->lock. A concurrent HCIINQUIRY ioctl can flush the cache and free an entry while the worker still references it. Kernel Address Sanitizer (KASAN) reported slab-use-after-free conditions in both hci_acl_create_conn_sync() and hci_stop_discovery_sync(). The race occurs because the sync worker holds only hdev->req_lock, while inquiry cache updates and flushes are serialized by hdev->lock.
Critical Impact
Local attackers with access to the HCI socket interface can trigger memory corruption in kernel space, potentially leading to privilege escalation or denial of service on systems with Bluetooth enabled.
Affected Products
- Linux kernel versions containing the affected hci_sync Bluetooth code paths
- Distributions shipping kernels prior to the fixes referenced in the upstream commits
- Systems with Bluetooth hardware or stacks exposing the HCIINQUIRY ioctl
Discovery Timeline
- 2026-10-18 - CVE-2026-98737 published to NVD
- 2026-10-21 - Last updated in NVD database
Technical Details for CVE-2026-98737
Vulnerability Analysis
The vulnerability is a classic locking-discipline mismatch in the Linux Bluetooth Host Controller Interface (HCI) layer. The command sync worker, running under hci_cmd_sync_work, holds hdev->req_lock when preparing HCI commands. However, inquiry cache management functions such as hci_inquiry_cache_update() and hci_inquiry_cache_flush() protect the cache using hdev->lock instead.
Two code paths illustrate the problem. In hci_acl_create_conn_sync(), the worker looks up a cache entry and reads its fields without acquiring hdev->lock. In hci_stop_discovery_sync(), the worker similarly dereferences a cache entry pointer. A concurrent HCIINQUIRY ioctl issued from userspace via hci_sock_ioctl() can flush the cache between the lookup and the field reads.
KASAN confirmed both races, reporting slab-use-after-free accesses in the two sync functions after cache entries were freed by hci_inquiry_cache_flush().
Root Cause
The root cause is inconsistent lock usage across code paths touching the same data structure. The inquiry cache is protected by hdev->lock, but the sync command worker reads cache entries while holding only hdev->req_lock. List traversal in the worker also races with concurrent updates and removals, producing both use-after-free reads and potential list corruption [CWE-416].
Attack Vector
Exploitation requires local access to the Bluetooth HCI socket. An unprivileged or low-privileged process invokes the HCIINQUIRY ioctl on an HCI socket while a discovery or connection operation runs on the sync workqueue. By racing the flush against the worker's lookup, the attacker frees cache entries that the worker subsequently dereferences, corrupting kernel heap memory.
The fix holds hdev->lock across each lookup and all reads from the returned entry. It copies the remote Bluetooth address before unlocking, so cancellation paths do not retain a stale pointer. The lock is released before issuing synchronous HCI commands, since their completion handlers may re-acquire it. See the upstream patches: Kernel Git Commit 333257e, Kernel Git Commit 52edf1c, Kernel Git Commit 8ed6753, Kernel Git Commit a642f4f, and Kernel Git Commit ddc9edb.
Detection Methods for CVE-2026-98737
Indicators of Compromise
- KASAN kernel log entries reporting slab-use-after-free in hci_acl_create_conn_sync or hci_stop_discovery_sync.
- Unexpected kernel oops or panic events referencing hci_cmd_sync_work in the call trace.
- Unexplained crashes on systems using Bluetooth discovery or connection workflows.
Detection Strategies
- Enable KASAN on test and staging kernels to surface use-after-free accesses in the Bluetooth stack before production impact.
- Monitor dmesg and journald for kernel warnings referencing hci_inquiry_cache_flush, hci_inquiry_cache_update, or hci_sock_ioctl.
- Audit which processes hold open HCI sockets (AF_BLUETOOTH, BTPROTO_HCI) and correlate with inquiry ioctl usage.
Monitoring Recommendations
- Collect kernel crash dumps and kernel log telemetry centrally to identify repeated Bluetooth subsystem faults across the fleet.
- Track installed kernel versions against the fixed commit list to confirm patch coverage on all Bluetooth-enabled hosts.
- Alert on new or unexpected processes opening raw HCI sockets, particularly on servers where Bluetooth is not an operational requirement.
How to Mitigate CVE-2026-98737
Immediate Actions Required
- Apply the upstream Linux kernel patches referenced in the external advisories as soon as distribution builds become available.
- Disable the Bluetooth subsystem on servers and workstations that do not require it, using rmmod bluetooth or blacklisting the module.
- Restrict CAP_NET_ADMIN and raw HCI socket access to trusted administrators and services only.
Patch Information
The fix is distributed across five upstream commits. The patch holds hdev->lock across inquiry cache lookups, copies the remote address before releasing the lock, and ensures synchronous HCI commands are issued without holding the lock. Review the commits at Kernel Git Commit 333257e, Kernel Git Commit 52edf1c, Kernel Git Commit 8ed6753, Kernel Git Commit a642f4f, and Kernel Git Commit ddc9edb.
Workarounds
- Unload the bluetooth kernel module on systems that do not require Bluetooth functionality.
- Blacklist Bluetooth modules at boot to prevent automatic loading by udev.
- Limit which users and services can open AF_BLUETOOTH sockets through seccomp, AppArmor, or SELinux policies.
# Disable and blacklist the Bluetooth kernel modules
sudo systemctl stop bluetooth.service
sudo systemctl disable bluetooth.service
echo "blacklist bluetooth" | sudo tee /etc/modprobe.d/blacklist-bluetooth.conf
echo "blacklist btusb" | sudo tee -a /etc/modprobe.d/blacklist-bluetooth.conf
sudo rmmod btusb bluetooth 2>/dev/null || true
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

