Skip to main content
VulnerabilityPublished Updated

CVE-2026-98107: Linux kernel · Bluetooth: L2CAP: fix out-of-bounds write in l2cap_ecred_connect

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · fixed in fabc5e04f123225daf980d03f2c5a05e7f0f0a7f : patch Linux kernel soon.

Data as of 26 Oct 2026, 20:21 UTC

Severity
High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

EPSS
0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in fabc5e04f123225daf980d03f2c5a05e7f0f0a7f, df8c3af6132640da4788e96a02d653e642059803, ce0927eb3ee2939fab5ce3f9334bfd2fafb38481 +2

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ da49b602f7f75ccc91386e1274b3ef71676cd092, < fabc5e04f123225daf980d03f2c5a05e7f0f0a7f
Fixed in
  • fabc5e04f123225daf980d03f2c5a05e7f0f0a7f
LinuxLinuxAffected
  • ≥ da49b602f7f75ccc91386e1274b3ef71676cd092, < df8c3af6132640da4788e96a02d653e642059803
Fixed in
  • df8c3af6132640da4788e96a02d653e642059803
LinuxLinuxAffected
  • ≥ da49b602f7f75ccc91386e1274b3ef71676cd092, < ce0927eb3ee2939fab5ce3f9334bfd2fafb38481
Fixed in
  • ce0927eb3ee2939fab5ce3f9334bfd2fafb38481
LinuxLinuxAffected
  • ≥ da49b602f7f75ccc91386e1274b3ef71676cd092, < 56c2b5831d39dc84aad2573dc3e197af1a872a05
Fixed in
  • 56c2b5831d39dc84aad2573dc3e197af1a872a05
LinuxLinuxAffected
  • ≥ da49b602f7f75ccc91386e1274b3ef71676cd092, < 6da5c0331fc3ef0c7b8df8269523fc3b2cce1e65
Fixed in
  • 6da5c0331fc3ef0c7b8df8269523fc3b2cce1e65
LinuxLinuxAffected
  • =5.7
Fixed in–

AI-suggested

A fix is available and has been applied in the Linux kernel. Users and administrators should update to a fixed kernel version that includes the patches identified by commits fabc5e04f123225daf980d03f2c5a05e7f0f0a7f, df8c3af6132640da4788e96a02d653e642059803, ce0927eb3ee2939fab5ce3f9334bfd2fafb38481, 56c2b5831d39dc84aad2573dc3e197af1a872a05, and 6da5c0331fc3ef0c7b8df8269523fc3b2cce1e65. No additional mitigations are indicated by the vendor advisory.

Description

A vulnerability in the Linux kernel Bluetooth L2CAP implementation (version 5.7) allows an out-of-bounds write in the l2cap_ecred_connect function. This occurs due to improper counting of pending ECRED channels, leading to one __le16 value being written outside the bounds of the scid array and sending an invalid ECRED_CONN_REQ. The issue is fixed by adjusting the counting logic to include non-deferred pending channels and moving the counting under a critical section to prevent exceeding the limit.

References

Community reviews

Loading reviews…