CVE-2026-99793: 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 BTCONNECT 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 BTCONFIG, completes configuration and becomes connected before security has completed. If security then fails, l2capsecuritycfm() 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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.12.118 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.18.64 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.3.5 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 7.3.5-1
Event History
Frequently Asked Questions
Who is exposed to this issue?
Systems using the Linux kernel Bluetooth L2CAP implementation are exposed when an outgoing L2CAP channel is being established and is awaiting security completion and feature-mask exchange. A Bluetooth peer that can send crafted L2CAP connection responses is needed to trigger the flawed state transition.
What security impact can exploitation have?
A peer can cause an outgoing channel to complete configuration and become connected before the required security level has been reached. If the later security check fails, the channel can remain connected despite the link not reaching the required security level.
Are channels affected before they send a connection request?
Yes. The vulnerable behavior occurs when a peer sends a connection response before the outgoing channel has sent its own connection request. The fix accepts connection responses only when the corresponding request is outstanding.
What does the fix change for zero source-CID responses?
For connection responses with a zero source CID, channel matching by identifier is restricted to channels with an outstanding connection request. This prevents selecting another channel that happens to hold the same identifier for a response it still needs to send.