Skip to main content
CVE-2026-99239VulnerabilityPublished Updated

Microsoft · Bluetooth: L2CAP: refuse __l2cap_chan_add if chan already has conn

Affects MicrosoftSource GCVE Database

0
Compare
Authoritative record:CVE-2026-99239· High 7.8

Not known to be exploited · CVSS 7.8 High · fixed in fabaff1c59ff2cc89cb7e5bd0186a5e15f0c73b2 : patch Microsoft soon.

Data as of 20 Nov 2026, 08:34 UTC

CVSS 3.1 base score
7.8High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Linux)CVSS 3.17.8
EPSS
0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in fabaff1c59ff2cc89cb7e5bd0186a5e15f0c73b2, e618d928ec7f88cbeadfa3542adcac40f474e629, d3afd7803f9bc2a8c4270199497b60158b2fc647 +13
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • >=5.10.265 <5.10.273
  • >=5.15.216 <5.15.224
  • >=6.1.183 <6.1.191
  • >=6.6.145 <6.6.161
  • >=6.12.97 <6.12.115
  • >=6.18.39 <6.18.60
  • >=7.1.4 <7.2
Fixed in
  • fabaff1c59ff2cc89cb7e5bd0186a5e15f0c73b2
  • e618d928ec7f88cbeadfa3542adcac40f474e629
  • d3afd7803f9bc2a8c4270199497b60158b2fc647
  • 820579652b24ce277e0097cd65b42bd9b7b8bf07
  • 73820561d8cbfd3364a29b8fa77f1707f26029da
  • 86b55991d3cd690e73c5ef8d20b75ae4905b357a
  • 85cc289eb08afa975375f838187369e68b429ee0
  • 52fe88e4ef87311eee32b45c65603e7c69e75e7d
  • 10c705dd706aa93164ba41f2566f15206d6c178e
  • 7.2
  • 6.18.60
  • 6.12.115
  • 6.6.161
  • 6.1.191
  • 5.15.224
  • 5.10.273
LinuxLinuxAffected
  • =7.2
Fixed in–
Debiandebian/linuxpkg:deb/debian/linuxOther threatsAffected
  • >=5.10.265 <5.10.273
  • >=5.15.216 <5.15.224
  • >=6.1.183 <6.1.191
  • >=6.6.145 <6.6.161
  • >=6.12.97 <6.12.115
  • >=6.18.39 <6.18.60
  • >=7.1.4 <7.2
  • =7.2
Fixed in
  • 5.10.273
  • 5.15.224
  • 6.1.191
  • 6.6.161
  • 6.12.115
  • 6.18.60
  • 7.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

This vulnerability involves the Bluetooth L2CAP component where the function __l2cap_chan_add improperly handles cases when a channel already has a connection. The issue is identified in Microsoft product version 4.0. No CVSS score or detailed impact information is provided.

References

Community reviews

Loading reviews…