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

CVE-2026-98455: Linux Kernel RFCOMM Use-After-Free Vulnerability

CVE-2026-98455 is a use-after-free vulnerability in the Linux kernel RFCOMM component that causes NULL pointer dereference. This article covers technical details, affected versions, impact analysis, and mitigation strategies.

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

CVE-2026-98455 is a NULL pointer dereference vulnerability in the Linux kernel's Bluetooth RFCOMM subsystem. The flaw resides in the RFCOMM_CONNINFOgetsockopt handler, which fails to validate that a Data Link Connection (DLC) session is still active before dereferencing it. A remote Bluetooth peer can send a Disconnect (DISC) frame after a socket with BT_DEFER_SETUP is accepted, clearing dlc->session while dlc->defer_setup remains set. A subsequent getsockopt(SOL_RFCOMM, RFCOMM_CONNINFO) call then dereferences the NULL session pointer, triggering a general protection fault and kernel panic.

Critical Impact

A remote Bluetooth BR/EDR peer in range can trigger a kernel NULL pointer dereference, leading to denial of service on affected Linux systems.

Affected Products

  • Linux kernel (upstream) with Bluetooth RFCOMM support enabled
  • Distributions shipping vulnerable net/bluetooth/rfcomm/sock.c code paths
  • Systems using BT_DEFER_SETUP on RFCOMM listening sockets

Discovery Timeline

  • 2026-10-18 - CVE-2026-98455 published to NVD
  • 2026-10-19 - Last updated in NVD database

Technical Details for CVE-2026-98455

Vulnerability Analysis

The vulnerability is a kernel-space NULL pointer dereference [CWE-476] in the Bluetooth RFCOMM protocol handler. The rfcomm_sock_getsockopt_old() function, inlined into rfcomm_sock_getsockopt(), accepts sockets that are not in the BT_CONNECTED state as long as rfcomm_pi(sk)->dlc->defer_setup is set. The handler then unconditionally follows dlc->session->sock->sk without verifying the session is still valid.

The kernel crash manifests as a general protection fault at offset 0x10, which corresponds to the sock field within struct rfcomm_session. KASAN classifies this as a null-ptr-deref in the range [0x0000000000000010-0x0000000000000017].

Root Cause

The root cause is incomplete state tracking during remote DLC teardown. When rfcomm_recv_disc() processes a Disconnect frame, it forces d->state = BT_CLOSED and calls __rfcomm_dlc_close(). The RFCOMM_DEFER_SETUP early return in __rfcomm_dlc_close() only matches states BT_CONNECT, BT_CONFIG, BT_OPEN, and BT_CONNECT2. With state already BT_CLOSED, execution falls through to rfcomm_dlc_unlink(), which sets d->session = NULL while d->defer_setup remains 1. The getsockopt handler's conditional therefore skips the -ENOTCONN return path and dereferences a NULL session pointer. A related issue in rfcomm_dlc_accept() was previously fixed by commit 43a556b2fd43.

Attack Vector

Exploitation requires an attacker-controlled Bluetooth BR/EDR peer within radio range of the target. The attacker establishes an ACL link, opens L2CAP on the RFCOMM Protocol/Service Multiplexer (PSM), starts an RFCOMM session, and sends a Set Asynchronous Balanced Mode (SABM) frame for a channel bound with BT_DEFER_SETUP. After the local application accepts the socket, the peer transmits a DISC frame for that DLC Identifier (DLCI). Any subsequent getsockopt(SOL_RFCOMM, RFCOMM_CONNINFO) call on the accepted socket triggers the crash. No race condition is required once the DISC frame has been processed.

For technical details, see the upstream patch at Kernel Commit 005b23d.

Detection Methods for CVE-2026-98455

Indicators of Compromise

  • Kernel oops messages referencing rfcomm_sock_getsockopt+0x529/0x780 in dmesg or system logs
  • KASAN reports with null-ptr-deref in the range [0x10-0x17] originating from the RFCOMM subsystem
  • Unexpected system reboots or kernel panics on hosts with active Bluetooth adapters in environments with untrusted BR/EDR peers

Detection Strategies

  • Monitor kernel ring buffer output for general protection fault entries associated with rfcomm_sock_getsockopt
  • Audit userspace applications that call getsockopt(SOL_RFCOMM, RFCOMM_CONNINFO) on sockets configured with BT_DEFER_SETUP
  • Correlate Bluetooth HCI logs showing SABM followed by DISC on deferred-setup channels with host instability events

Monitoring Recommendations

  • Collect dmesg and /var/log/kern.log output centrally and alert on RFCOMM-related oops signatures
  • Enable Bluetooth HCI snoop logging on sensitive endpoints to capture suspicious L2CAP/RFCOMM session patterns
  • Track kernel package versions across the fleet to confirm patch coverage on all Bluetooth-capable hosts

How to Mitigate CVE-2026-98455

Immediate Actions Required

  • Apply the upstream Linux kernel patch series referenced in the stable tree commits as soon as distribution updates are available
  • Disable the Bluetooth stack on systems that do not require it using systemctl disable --now bluetooth and unload the rfcomm module
  • Restrict Bluetooth discoverability and pairing on hosts that must remain Bluetooth-enabled

Patch Information

The fix restricts the deferred-setup exception in rfcomm_sock_getsockopt() to the BT_CONNECT2 state and validates that dlc->session is non-NULL before dereferencing it. Patches have been merged across stable branches via the following commits: 005b23d, 1c4f7e1, 46f8ffd, 4bf5ca4, 84ae3cf, 8f5b30c, c3aee3f, and c7362f6.

Workarounds

  • Blacklist the rfcomm kernel module where RFCOMM services are not required
  • Avoid using BT_DEFER_SETUP on RFCOMM listening sockets until the kernel is patched
  • Operate Bluetooth-enabled devices only in physically controlled environments where untrusted peers cannot establish BR/EDR connections
bash
# Disable and unload the RFCOMM module to eliminate the attack surface
sudo systemctl stop bluetooth
sudo modprobe -r rfcomm
echo 'blacklist rfcomm' | sudo tee /etc/modprobe.d/blacklist-rfcomm.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.