Security-gate bypass via invalid L2CAP state transitions
Published Nov 20, 2026 · Updated Nov 20, 2026
State-validation errors in Linux Bluetooth L2CAP allow physically proximate attackers to bypass connection security gates. Signaling handlers in net/bluetooth/l2cap_core.c accept configuration responses during BT_CONNECT2, advancing channels to BT_CONNECTED before security or deferred acceptance completes, and accept late responses on closing channels. Exploitation requires Bluetooth peer reachability and an affected channel state; the documented consequence is premature connection establishment or incorrect channel-state transitions, not demonstrated code execution.
Summary
What happened
State-validation errors in Linux Bluetooth L2CAP allow physically proximate attackers to bypass connection security gates. Signaling handlers in net/bluetooth/l2cap_core.c accept configuration responses during BT_CONNECT2, advancing channels to BT_CONNECTED before security or deferred acceptance completes, and accept late responses on closing channels. Exploitation requires Bluetooth peer reachability and an affected channel state; the documented consequence is premature connection establishment or incorrect channel-state transitions, not demonstrated code execution.
The record
- CVE
- CVE-2026-99794
- Published
- Nov 20, 2026
- Updated
- Nov 20, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 20, 2026CVE publishedPublication date reported by the CVE source.
- Nov 20, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <1485880c4c91d69533e08769d033f0868c85a539
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6320736af7dcb90da6ee9fd651ecc11c564d45b7
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <9a63e20fcedef1cb9fd6dc771ee364ca83a36bf2
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <c6f3af8470e4f97553a49c48d9336bdd1f927cb0
- Affected versionversion=2.6.12
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Contact us