Skip to main content
Vulnerability Database/CVE-2026-97975

CVE-2026-97975: Linux Kernel Bluetooth Race Condition Flaw

CVE-2026-97975 is a race condition flaw in the Linux kernel Bluetooth subsystem causing NULL pointer dereference during device unregistration. This article covers the technical details, affected versions, and mitigation.

Published:

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-97975 Overview

CVE-2026-97975 is a NULL pointer dereference vulnerability in the Linux kernel Bluetooth subsystem. The flaw resides in hci_sysfs.c and triggers through a race condition between hci_conn_del_sysfs() and concurrent child device unregistration, such as a BNEP network device in bnep_session. When device_del() runs in parallel with hci_conn_del_sysfs() reparenting child devices, klist_put() dereferences a stale node, causing a kernel NULL pointer dereference.

Critical Impact

The race condition in the Bluetooth hci_sysfs subsystem can cause kernel crashes on systems using BNEP or related Bluetooth child devices, resulting in denial of service.

Affected Products

  • Linux kernel versions containing commit 27aabf27fd01 ("Bluetooth: fix use-after-free in device_for_each_child()")
  • Linux distributions shipping the vulnerable Bluetooth hci_sysfs implementation
  • Systems using BNEP (Bluetooth Network Encapsulation Protocol) or RFCOMM TTY devices

Discovery Timeline

  • 2026-09-25 - CVE-2026-97975 published to NVD
  • 2026-09-25 - Last updated in NVD database

Technical Details for CVE-2026-97975

Vulnerability Analysis

The vulnerability is a NULL pointer dereference triggered by a race condition in the Linux kernel Bluetooth sysfs handling code. When a child device such as a BNEP network device registered under a Bluetooth connection is being unregistered concurrently with hci_conn_del_sysfs(), the kernel accesses a stale parent pointer. This leads to klist_put() dereferencing knode_klist(n)->put on an already removed node.

The failure path crashes the kernel on affected systems. Exploitation requires concurrent Bluetooth activity rather than remote network input, limiting the attack surface to local or physically proximate scenarios where Bluetooth operations can be induced.

Root Cause

The bug originated with commit 27aabf27fd01, which replaced device_find_child(..., __match_tty) with device_find_any_child() in hci_conn_del_sysfs(). The earlier change was intended to resolve a use-after-free where conn->dev outlived its parent hdev->dev because conn->dev only held a reference to hdev->dev while registered in sysfs. By broadening the child selection, the new logic introduced a window where device_move() reparents a child device to NULL while a concurrent device_del() operates on the same device, having snapshotted a non-NULL parent pointer.

Attack Vector

An attacker with local access and the ability to trigger Bluetooth connection teardown while a BNEP session is unregistering can race the two code paths. The resulting NULL pointer dereference in klist_put() crashes the kernel. Successful exploitation requires precise timing between hci_conn_del_sysfs() and unregister_netdev() on the dependent child device.

No verified public exploit code is available. The vulnerability is described in the upstream kernel commit messages referenced below.

Detection Methods for CVE-2026-97975

Indicators of Compromise

  • Kernel oops or panic messages referencing klist_put, klist_del, or device_del in the call stack during Bluetooth teardown operations
  • Repeated kernel crashes correlated with BNEP session termination or RFCOMM device unregistration
  • Unexpected system reboots on hosts actively using Bluetooth networking features

Detection Strategies

  • Monitor dmesg and /var/log/kern.log for NULL pointer dereference traces originating in hci_sysfs.c
  • Compare running kernel versions against distribution advisories referencing the fix commits 9b851b09b392, 9e9ece97b8e7, and eeabdb25c320
  • Audit systems for the presence of the vulnerable device_find_any_child() call pattern in hci_conn_del_sysfs()

Monitoring Recommendations

  • Collect kernel crash dumps for post-incident analysis to confirm whether klist_put() is implicated
  • Track Bluetooth subsystem telemetry on endpoints and IoT devices, especially those using BNEP tethering
  • Alert on repeated unplanned restarts of hosts that use RFCOMM TTY or Bluetooth PAN functionality

How to Mitigate CVE-2026-97975

Immediate Actions Required

  • Apply the stable kernel updates containing commits 9b851b09b392, 9e9ece97b8e7, or eeabdb25c320 from the upstream Linux kernel tree
  • Disable the Bluetooth stack on systems that do not require it until patches are deployed
  • Unload BNEP and related Bluetooth networking kernel modules on servers where they are unnecessary

Patch Information

The fix takes an explicit reference to the parent device with get_device(&hdev->dev) in hci_conn_init_sysfs() and drops it with put_device(parent) in bt_link_release() when the conn device is freed. This keeps hdev->dev valid for the entire lifecycle of conn->dev, resolving the underlying use-after-free. With the parent reference held correctly, the fix restores the __match_tty filter in hci_conn_del_sysfs(), so device_move() only operates on persistent RFCOMM TTY devices. See the upstream commits: commit 9b851b09b392, commit 9e9ece97b8e7, and commit eeabdb25c320.

Workarounds

  • Blacklist the bnep and bluetooth kernel modules on systems that do not require Bluetooth functionality
  • Restrict physical and local access to systems running vulnerable kernels until updates are applied
  • Avoid concurrent teardown of Bluetooth connections and BNEP network interfaces on unpatched hosts
bash
# Blacklist Bluetooth modules on systems that do not require Bluetooth
echo "blacklist bluetooth" | sudo tee /etc/modprobe.d/blacklist-bluetooth.conf
echo "blacklist bnep" | sudo tee -a /etc/modprobe.d/blacklist-bluetooth.conf
sudo update-initramfs -u

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

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.