CVE-2026-64355: Linux kernel · bpf: Reject fragmented frames in devmap
Affects Linux kernelSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical · fixed in c5b4f5efcb55c1af3fe44ff712d31b7fb098a831 : patch Linux kernel as a priority.
Data as of 26 Oct 2026, 13:07 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 43% 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 c5b4f5efcb55c1af3fe44ff712d31b7fb098a831, bccbab36ff228e0825eb85d9b0f9b8434cd0a399, aa496720618f1a6054f1c870bf10b4f6c99bf656 +4
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 25 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: bpf: Reject fragmented frames in devmap Devmap broadcast redirects clone the packet for all but the last destination. For native XDP, that clone path copies only the linear xdp_frame data, while fragmented frames keep skb_shared_info in tailroom outside the linear area. Cloning such a frame leaves XDP_FLAGS_HAS_FRAGS set but without valid frag metadata, and the later free path can interpret uninitialized tail data as skb_shared_info, leading to an out-of-bounds access during frame return. Reject fragmented native XDP frames in dev_map_enqueue_clone(). Add the same restriction to the generic XDP clone path in dev_map_redirect_clone(). Generic XDP represents fragmented packets as nonlinear skbs, and rejecting them here keeps clone-based broadcast support aligned between native and generic XDP.
References
- git.kernel.org/stable/c/47baddc856ae7e93a565dd9deeb797999b179466 (opens in a new tab)
- git.kernel.org/stable/c/07a4c11ee8ef4abcb39d922e9e410ae269671cdf (opens in a new tab)
- git.kernel.org/stable/c/bccbab36ff228e0825eb85d9b0f9b8434cd0a399 (opens in a new tab)
- git.kernel.org/stable/c/c5b4f5efcb55c1af3fe44ff712d31b7fb098a831 (opens in a new tab)
- git.kernel.org/stable/c/a9bb2d9c798cb62a4050a991c27b752770c33afe (opens in a new tab)
- git.kernel.org/stable/c/51d07c12ca411e692c424ecdabf077f1e61a61be (opens in a new tab)
- git.kernel.org/stable/c/aa496720618f1a6054f1c870bf10b4f6c99bf656 (opens in a new tab)