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-98738 Overview
CVE-2026-98738 is a use-after-free vulnerability in the Linux kernel Bluetooth subsystem. The flaw resides in the Security Manager Protocol (SMP) code path, specifically in build_pairing_cmd(). This function reads remote Out-of-Band (OOB) pairing data without holding the hdev->lock that serializes list writers. A concurrent management command can unlink and free an OOB entry while SMP is still accessing it. The issue was identified through Kernel Address Sanitizer (KASAN) reports showing a slab-use-after-free condition during Bluetooth L2CAP receive processing.
Critical Impact
Concurrent Bluetooth management operations can trigger a kernel use-after-free, potentially leading to memory corruption, information disclosure, or denial of service on affected Linux systems.
Affected Products
- Linux kernel Bluetooth subsystem
- Systems with Bluetooth hardware and SMP pairing enabled
- Multiple stable kernel branches referenced in upstream commits
Discovery Timeline
- 2026-10-18 - CVE-2026-98738 published to NVD
- 2026-10-21 - Last updated in NVD database
Technical Details for CVE-2026-98738
Vulnerability Analysis
The vulnerability is a race condition that produces a use-after-free in the Linux kernel Bluetooth stack. When two threads interact with the remote OOB data list concurrently, memory safety guarantees break down. One thread executes build_pairing_cmd() as part of SMP pairing on the L2CAP receive path. A second thread processes a management Remove Remote OOB Data command via hci_sock_sendmsg(), which calls hci_remote_oob_data_clear() and frees the entry.
Because build_pairing_cmd() does not hold hdev->lock, the removal path can unlink and free the entry after SMP locates it but before SMP reads the present flag or copies the random and confirmation values. Removal can also invalidate an entry mid-traversal. KASAN flagged the resulting access as slab-use-after-free in build_pairing_cmd+0x948/0x9b0.
Root Cause
The root cause is missing serialization between SMP readers and management writers of the per-device remote OOB data list [CWE-416, CWE-362]. Acquiring hdev->lock inside build_pairing_cmd() was not viable because callers already hold it in some paths, and taking it on the receive path would invert the established device-to-L2CAP lock order.
Attack Vector
An attacker with the ability to issue Bluetooth management commands can race Add Remote OOB Data and Remove Remote OOB Data operations against an in-progress SMP pairing exchange. The exploitation window exists during list traversal and the subsequent field reads in build_pairing_cmd(). The fix introduces a dedicated remote_oob_lock mutex that is held across the SMP lookup and value copies, and by the add, remove, and clear helpers. Initialization and in-place updates are also covered so SMP cannot observe partially initialized OOB values. See the upstream patches at Kernel Commit 889c61e and Kernel Commit df5162e for implementation details.
Detection Methods for CVE-2026-98738
Indicators of Compromise
- KASAN reports containing slab-use-after-free in build_pairing_cmd in kernel logs.
- Kernel oops or panic traces referencing smp_recv_cb, l2cap_recv_frame, or hci_rx_work.
- Unexpected Bluetooth stack crashes during SMP pairing when management commands are issued concurrently.
Detection Strategies
- Enable KASAN on test and canary kernels to catch slab-use-after-free conditions on the Bluetooth receive path.
- Monitor dmesg and journald for Bluetooth subsystem call traces that correlate with hci_sock_sendmsg activity from add_remote_oob_data or remove_remote_oob_data.
- Audit which processes hold CAP_NET_ADMIN and can issue HCI management commands against local Bluetooth adapters.
Monitoring Recommendations
- Collect kernel crash dumps and KASAN output centrally for review by security operations.
- Track Bluetooth management command activity on endpoints to spot abnormal add and remove sequences targeting remote OOB data.
- Alert on repeated Bluetooth stack faults on systems where Bluetooth is required and cannot be disabled.
How to Mitigate CVE-2026-98738
Immediate Actions Required
- Apply the stable kernel updates referenced in the upstream fix commits as soon as vendor packages are available.
- Disable the Bluetooth subsystem on systems that do not require it by unloading the bluetooth and btusb kernel modules.
- Restrict local access and CAP_NET_ADMIN privileges that allow issuing HCI management commands.
Patch Information
The fix adds a per-device remote_oob_lock mutex held across the SMP lookup, value copies, and by the add, remove, clear, initialization, and in-place update paths. Writers retain their existing hdev->lock protection. The new critical sections acquire no device, connection, or channel locks, avoiding lock inversion. Patches are available via these upstream references: Kernel Commit 1e11412, Kernel Commit 81a2345, Kernel Commit 889c61e, Kernel Commit 94afa17, and Kernel Commit df5162e.
Workarounds
- Blacklist Bluetooth kernel modules on servers and workstations where Bluetooth is not operationally required.
- Avoid using OOB pairing workflows until the patched kernel is deployed.
- Limit which users can access /dev/rfkill and HCI sockets to reduce the attack surface for racing management commands.
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

