CVE-2026-99239

Bluetooth: L2CAP: refuse __l2cap_chan_add if chan already has conn

  • High 7.8

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.

Key facts

Published
2 Nov 2026
Last changed
3 Nov 2026
Assigned by
Linux
EPSS
0.126% likely to be exploited in the next 30 days, higher than 2.328% of CVEs (scores for 16 Nov 2026)

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 7.8CVSS 3.1, Highfrom the CNA (Linux)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • 8f90405a4a6f1f1880dc07996b47bf57c712bd8a up to but excluding 85cc289eb08afa975375f838187369e68b429ee0 (affected)
  • 32d783cafb46ff3ca58e6f9fd62c9c5f35eaf26b up to but excluding 820579652b24ce277e0097cd65b42bd9b7b8bf07 (affected)
  • 8922c7940bae9ce4b1736dddb6362370793835c2 up to but excluding e618d928ec7f88cbeadfa3542adcac40f474e629 (affected)
  • 91047a4396a8b1857a6f712a90cf33ec0012b189 up to but excluding fabaff1c59ff2cc89cb7e5bd0186a5e15f0c73b2 (affected)
  • 0b0e2bf39cf99e458d991b9df253727e036a7d7d up to but excluding 52fe88e4ef87311eee32b45c65603e7c69e75e7d (affected)
  • d3b739db5dc6f688a60d56da872fabaf65246032 up to but excluding 10c705dd706aa93164ba41f2566f15206d6c178e (affected)
  • b66774b48dd98f07254951f74ea6f513efe7ff8b up to but excluding 73820561d8cbfd3364a29b8fa77f1707f26029da (affected)
  • b66774b48dd98f07254951f74ea6f513efe7ff8b up to but excluding d3afd7803f9bc2a8c4270199497b60158b2fc647 (affected)
  • b66774b48dd98f07254951f74ea6f513efe7ff8b up to but excluding 86b55991d3cd690e73c5ef8d20b75ae4905b357a (affected)
  • 50c38d9f42a529691e4e67ea9cedf4f0bfc8d277 (affected)
  • 5.10.265 up to but excluding 5.10.273 (affected)
  • 5.15.216 up to but excluding 5.15.224 (affected)
  • 6.1.183 up to but excluding 6.1.191 (affected)
  • 6.6.145 up to but excluding 6.6.161 (affected)
  • 6.12.97 up to but excluding 6.12.115 (affected)
  • 6.18.39 up to but excluding 6.18.60 (affected)
  • 7.1.4 up to but excluding 7.2 (affected)
LinuxLinux
  • Default status: affected
  • 7.2 (affected)
  • 0 up to but excluding 7.2 (unaffected)
  • 5.10.273 up to and including 5.10.* (unaffected)
  • 5.15.224 up to and including 5.15.* (unaffected)
  • 6.1.191 up to and including 6.1.* (unaffected)
  • 6.6.161 up to and including 6.6.* (unaffected)
  • 6.12.115 up to and including 6.12.* (unaffected)
  • 6.18.60 up to and including 6.18.* (unaffected)
  • 7.2.14 up to and including 7.2.* (unaffected)
  • 7.3.1 up to and including 7.3.* (unaffected)
  • 7.4-rc1 up to and including * (unaffected)

Timeline

  1. 2 Nov 2026 Published

References