CVE-2026-64000: Linux kernel · Out-of-bounds Read
Affects Linux kernelSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical · fixed in fbd0662f9c9a66e8cc3df3099cca8ed6d3837cc7 : patch Linux kernel as a priority.
Data as of 26 Oct 2026, 17:30 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 41% 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 can reliably automate steps 1–4 of the kill chain
- Technical impact
- Total control over the software or total information disclosure
CISA SSVC assessment, 2026-10-16.
- Patch
- Available – fixed in fbd0662f9c9a66e8cc3df3099cca8ed6d3837cc7, f229426072fc865654a60978bb7fda790a051ff3, a4b64f3e9c7b8259f7dd251a0313420ba7c01852 +3
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 19 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
Description
In the Linux kernel, the following vulnerability has been resolved: net: hsr: fix potential OOB access in supervision frame handling Ensure the entire TLV header is linearized before access by adding sizeof(struct hsr_sup_tlv) to the pskb_may_pull() calls. Without this, a truncated frame could cause an out-of-bounds access.
References
- git.kernel.org/stable/c/09a37dca090c55ffb1a33f52d8667f1c2367ef48 (opens in a new tab)
- git.kernel.org/stable/c/a4b64f3e9c7b8259f7dd251a0313420ba7c01852 (opens in a new tab)
- git.kernel.org/stable/c/71c986c0ba45b7dc574fae27c83e7b6671556f37 (opens in a new tab)
- git.kernel.org/stable/c/fbd0662f9c9a66e8cc3df3099cca8ed6d3837cc7 (opens in a new tab)
- git.kernel.org/stable/c/78607a6854a22a2502f68092202e75a39af4865d (opens in a new tab)
- git.kernel.org/stable/c/f229426072fc865654a60978bb7fda790a051ff3 (opens in a new tab)