Skip to main content
VulnerabilityPublished Updated

CVE-2026-64403: Linux kernel · Out-of-bounds Read

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · CVSS 7.1 High · fixed in f70d4aa88068096f35d73e3a05eff33c0a16b9cd : patch Linux kernel soon.

Data as of 26 Oct 2026, 13:07 UTC

CVSS 3.1 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 18% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-10-16.

Patch
Available – fixed in f70d4aa88068096f35d73e3a05eff33c0a16b9cd, cca81b4bc672604a84f6d224a55cc77ec7dee619, 687617555cedfb74c9e3cb85d759b908dcb17856 +12
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Jul 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
  • >=3.16.66 <3.17
  • >=3.18.138 <3.19
  • >=4.4.178 <4.5
  • >=4.9.167 <4.10
  • >=4.14.110 <4.15
  • >=4.19.33 <4.20
  • >=5.0.6 <5.1
Fixed in
  • f70d4aa88068096f35d73e3a05eff33c0a16b9cd
  • cca81b4bc672604a84f6d224a55cc77ec7dee619
  • 687617555cedfb74c9e3cb85d759b908dcb17856
  • 996d3da39899aceb8f4910911a3f19a45a7d9d1b
  • 98d93c226bdfaa79bbdd86981921d7f106374225
  • 73abbaf91aa33da87c008fb62c148ade561bb606
  • 7d871e969b941ce25653f7716203a0ea4d07ad4b
  • 6b47bdaacfd0045687880177e0987055d8f4765a
  • 5.1
  • 4.20
  • 4.15
  • 4.10
  • 4.5
  • 3.19
  • 3.17
LinuxLinuxAffected
  • =5.1
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: validate option length before reading conf opt value l2cap_get_conf_opt() derives the option length from the attacker-controlled opt->len field and immediately dereferences opt->val (as u8, get_unaligned_le16() or get_unaligned_le32(), or a raw pointer for the default case) before any caller has confirmed that opt->len bytes are present in the buffer. The callers (l2cap_parse_conf_req(), l2cap_parse_conf_rsp() and l2cap_conf_rfc_get()) only detect a malformed option afterwards, once the running length has gone negative, by which point the out-of-bounds read has already executed. An existing post-hoc length check keeps the garbage value from being consumed, so this is not a data leak in the current control flow. It is still a validate-after-use ordering bug: up to 4 bytes are read past the end of the buffer before it is known to contain them, and it is fragile to future changes in the callers. Fix it at the source. Pass the end of the buffer into l2cap_get_conf_opt() and refuse to touch opt->val unless the full option (header + value) fits. Each caller computes an end pointer once before the loop and checks the return value directly instead of inferring the error from a negative length.

References

Community reviews

Loading reviews…