CVE-2026-99794 in Linuxinfo

Summary

by MITRE • 11/20/2026

In the Linux kernel, the following vulnerability has been resolved:

Bluetooth: L2CAP: Reject signalling responses in invalid states

A peer can send configuration messages while an incoming channel is in BT_CONNECT2, before the security or deferred accept gate has completed. A configuration response can then promote the channel to BT_CONNECTED. Configuration responses can also act on channels that are closing, and a late connection response can move a disconnecting channel back to BT_CONFIG.

Accept connection responses only while waiting in BT_CONNECT. Answer configuration requests in BT_CONNECT2, but defer our own request until BT_CONFIG so configuration cannot complete before the gate. Ignore configuration responses outside BT_CONFIG and BT_CONNECTED, and only complete configuration in BT_CONFIG.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Analysis

by VulDB Data Team • 11/20/2026

The Linux kernel Bluetooth subsystem contains a state management flaw within the Logical Link Control and Adaptation Protocol (L2CAP) layer that allows for improper channel state transitions during connection establishment and teardown phases. This vulnerability arises from an insufficient validation of incoming signaling messages against the current socket state, specifically affecting channels in the BT_CONNECT2 phase or those undergoing disconnection procedures. The core issue lies in the acceptance of configuration responses from a remote peer when the local endpoint is not yet fully established or is already in the process of closing. By accepting these out-of-sequence signals, an attacker can manipulate the internal state machine to force a channel into BT_CONNECTED status prematurely or revert a disconnecting channel back to BT_CONFIG, thereby bypassing critical security checks and connection integrity controls.

From a technical perspective, the L2CAP layer is responsible for managing logical connections between Bluetooth devices, handling multiplexing of higher-layer protocols over the baseband link. During normal operation, a new incoming connection progresses through several states: starting with BT_CONNECT upon receiving an ACL connection request, moving to BT_CONNECT2 after security authentication or deferred accept gates are initiated, and finally reaching BT_CONFIG where configuration parameters such as MTU and flush timeout are negotiated before transitioning to BT_CONNECTED for data transfer. The vulnerability exploits the window between entering BT_CONNECT2 and completing these gate checks. A malicious peer can send L2CAP Configuration Requests while the local stack is still processing security credentials or waiting for user-space authorization. If the local implementation incorrectly processes configuration responses during this interval, it may skip necessary validation steps. Furthermore, the flaw extends to channels in closing states; a late-arriving connection response from an attacker can trick the kernel into reactivating a channel that was previously marked for disconnection, leading to resource leaks or use-after-free conditions if memory associated with the old state is freed while still referenced by the newly activated context.

The operational impact of this vulnerability includes potential denial of service and security bypasses. By forcing channels into invalid states, an attacker can cause the Bluetooth stack to behave unpredictably, potentially crashing the kernel module responsible for L2CAP processing or causing system instability due to inconsistent state tracking. More critically, if the BT_CONNECT2 phase involves mandatory authentication or authorization checks that are effectively skipped by this race condition, it could allow unauthorized devices to establish connections without proper credentials. This undermines the security model of Bluetooth pairing and encryption, potentially exposing sensitive data exchanged over these links. Additionally, manipulating channels back from a closing state can lead to resource exhaustion as the system attempts to maintain resources for connections that should have been terminated, facilitating denial-of-service attacks against local services relying on stable Bluetooth connectivity.

This issue is categorized under CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') and aligns with MITRE ATT&CK technique T1059: Command and Scripting Interpreter if exploited to execute further malicious actions, or more directly with improper input validation flaws often associated with state machine violations. The root cause is a lack of strict adherence to the defined L2CAP finite state machine transitions within the kernel implementation. To mitigate this risk, system administrators should apply the latest available Linux kernel updates that include patches for Bluetooth L2CAP signaling handling. These updates enforce stricter checks by ensuring configuration responses are only accepted when the channel is explicitly in BT_CONFIG or BT_CONNECTED states and prevent connection responses from altering channels that are not actively waiting in BT_CONNECT. Users relying on high-security environments should also ensure their devices utilize updated firmware to minimize exposure vectors, although the primary fix resides at the kernel level where state transitions are strictly gated by security completion events rather than mere message receipt.

Responsible

Linux

Reservation

09/25/2026

Disclosure

11/20/2026

Moderation

accepted

CPE

ready

EPSS

0.00204

KEV

no

Activities

very low

Sources

Do you want to use VulDB in your project?

Use the official API to access entries easily!