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.
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:- Version 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and below 08ad7b94a31820eb3082851b924f76503fe66ebf is affected.
- Version 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and below c6789ceaf6e28e97d73434e12c7ae60432f86dbb is affected.
- Version 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and below bef1f610bc1f99b349368cb8d9025c2ff66d1fbe is affected.
- Version 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and below a518b9a9ef6ee3b18ecdf6ba5360c608aaf969e9 is affected.
- Version 2.6.12 is affected.
- Before 2.6.12 is unaffected.
- Version 6.12.118, <= 6.12.* is unaffected.
- Version 6.18.64, <= 6.18.* is unaffected.
- Version 7.3.5, <= 7.3.* is unaffected.
- Version 7.4-rc1, <= * is unaffected.
Exploit Probability
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.