CVE-2026-99793: Bluetooth: L2CAP: Only accept connection responses to outstanding requests

Published Nov 20, 2026
·
Updated

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

7 affected componentsFixes available
linux/kernel>=2.6.12<6.12.118
6.12.118
linux/kernel>=6.13.0<6.18.64
6.18.64
linux/kernel>=6.19.0<7.3.5
7.3.5
debian/linux*
debian/linux*
debian/linux*
debian/linux<=6.1.176-1, <=6.1.192-2, <=6.12.107-1, <=6.12.117-1, <=7.3.4-1
7.3.5-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.12.118
  2. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.18.64
  3. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 7.3.5
  4. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 7.3.5-1

Event History

Nov 20, 2026
CVE Published
via MITRE·05:51 AM
Data Sourced
via MITRE·05:51 AM
Description
Data Sourced
via OSV·05:51 AM
DescriptionAffected Software
Data Sourced
via NVD·06:18 AM
Description

Frequently Asked Questions

1

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.

2

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.

3

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.

4

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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203