CVE-2026-99239
Description
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: refuse __l2cap_chan_add if chan already has conn l2cap_chan may be linked to l2cap_conn at most once. This is assumed in several places, eg l2cap_chan_del cleanup. There is a TOCTOU race where the invariant is violated: [Task 1] [Task 2] l2cap_chan_connect l2cap_sock_bind l2cap_chan_lock lock_sock l2cap_state_change if (sk->sk_state != BT_OPEN) chan->state = BT_CONNECT l2cap_sock_state_change_cb chan->state = BT_BOUND sk->sk_state = BT_BOUND lock_sock <------------------ release_sock sk->sk_state = BT_CONNECT l2cap_sock_connect() does not check sk->sk_state, so since chan->state is now BT_BOUND, subsequent connect() ends up with second __l2cap_chan_add. Explicitly document and check the invariant in __l2cap_chan_add with WARN_ON_ONCE. The only callsite where it could be hit is l2cap_chan_connect, so add pre-check there to avoid relying on chan->state. chan->state read/write is not properly guarded currently so there can be other TOCTOUC problems. Add l2cap_lock_chan in l2cap_sock_bind() to guard chan->state write.
Timeline
- 2026-11-02Published by the CNA16:06 UTC
Affected products
Products listed as vulnerable. Upgrade to the version under "Fixed in", or a later one.
| Product | Vulnerable versions | Fixed in |
|---|---|---|
| linux linux | from 5.10.265 before 5.10.273fixed in 5.10.273from 5.15.216 before 5.15.224fixed in 5.15.224from 6.1.183 before 6.1.191fixed in 6.1.191from 6.12.97 before 6.12.115fixed in 6.12.115from 6.18.39 before 6.18.60fixed in 6.18.60(+2 more) | 5.10.2735.15.2246.1.1916.12.1156.18.60 |
| linux linux_kernel | from 5.10.265 before 5.10.273fixed in 5.10.273from 5.15.216 before 5.15.224fixed in 5.15.224from 6.1.183 before 6.1.191fixed in 6.1.191from 6.12.97 before 6.12.115fixed in 6.12.115from 6.18.39 before 6.18.60fixed in 6.18.60(+5 more) | 5.10.2735.15.2246.1.1916.12.1156.18.60 |
References
- https://git.kernel.org/stable/c/10c705dd706aa93164ba41f2566f15206d6c178e
- https://git.kernel.org/stable/c/52fe88e4ef87311eee32b45c65603e7c69e75e7d
- https://git.kernel.org/stable/c/73820561d8cbfd3364a29b8fa77f1707f26029da
- https://git.kernel.org/stable/c/820579652b24ce277e0097cd65b42bd9b7b8bf07
- https://git.kernel.org/stable/c/85cc289eb08afa975375f838187369e68b429ee0
- https://git.kernel.org/stable/c/86b55991d3cd690e73c5ef8d20b75ae4905b357a
- https://git.kernel.org/stable/c/d3afd7803f9bc2a8c4270199497b60158b2fc647
- https://git.kernel.org/stable/c/e618d928ec7f88cbeadfa3542adcac40f474e629
- https://git.kernel.org/stable/c/fabaff1c59ff2cc89cb7e5bd0186a5e15f0c73b2
Get more CVE data from the API.
curl 'https://api.contrastcyber.com/cve_lookup/CVE-2026-99239'curl 'https://api.contrastcyber.com/cve_risk_score/CVE-2026-99239'curl 'https://api.contrastcyber.com/cve_exploit/CVE-2026-99239'curl 'https://api.contrastcyber.com/cve_products/CVE-2026-99239'
Sources
- Vulnerability data from the National Vulnerability Database (NIST) and the CVE Program. CVE records: Copyright © 1999-2026, The MITRE Corporation, used under the CVE Program Terms of Use. CVE® is a registered trademark of The MITRE Corporation.
- CWE definitions: Copyright © 2006-2026, The MITRE Corporation, used under the CWE Terms of Use. CWE is a trademark of The MITRE Corporation.
- OWASP Top 10 categories by the OWASP Foundation (CC BY 3.0).
- EPSS scores by FIRST.org EPSS, used with attribution.
- KEV catalog and SSVC decisions by CISA.
- Advisory data from the GitHub Advisory Database through OSV.dev (CC BY 4.0).
- Exploit metadata from the Exploit Database (GPL-2.0-only, metadata only).
- Nuclei template names from nuclei-templates (MIT).