Linux Kernel Bluetooth L2CAP Improper Connection Response Handling
CVE-2026-99793 Published on November 20, 2026

Bluetooth: L2CAP: Only accept connection responses to outstanding requests
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Only accept connection responses to outstanding requests An outgoing channel waits in BT_CONNECT until security and the feature mask exchange complete, and only then sends its connection request. A peer can answer it before that with a connection response matching our source CID. The channel then moves to BT_CONFIG, completes configuration and becomes connected before security has completed. If security then fails, l2cap_security_cfm() leaves the connected channel alone, so it stays up on a link that did not reach the required security level. A connection response with a zero source CID is matched by identifier. Another channel can hold the same identifier for a response it still has to send, so the lookup can pick the wrong channel. Only accept a connection response while our request is outstanding, and only look at such channels when matching by identifier.

NVD


Products Associated with CVE-2026-99793

Want to know whenever a new CVE is published for Linux Kernel? stack.watch will email you.

Affected Versions

Linux: Linux:

Exploit Probability

EPSS
0.17%
Percentile
6.69%

EPSS (Exploit Prediction Scoring System) scores estimate the probability that a vulnerability will be exploited in the wild within the next 30 days. The percentile shows you how this score compares to all other vulnerabilities.