Skip to main content
VulnerabilityPublished Updated

CVE-2026-64355: Linux kernel · bpf: Reject fragmented frames in devmap

Affects Linux kernelSource CVE Database V5

0

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

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
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: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
  • ≥ e624d4ed4aa8cc3c69d1359b0aaea539203ed266, < c5b4f5efcb55c1af3fe44ff712d31b7fb098a831
Fixed in
  • c5b4f5efcb55c1af3fe44ff712d31b7fb098a831
LinuxLinuxAffected
  • ≥ e624d4ed4aa8cc3c69d1359b0aaea539203ed266, < bccbab36ff228e0825eb85d9b0f9b8434cd0a399
Fixed in
  • bccbab36ff228e0825eb85d9b0f9b8434cd0a399
LinuxLinuxAffected
  • ≥ e624d4ed4aa8cc3c69d1359b0aaea539203ed266, < aa496720618f1a6054f1c870bf10b4f6c99bf656
Fixed in
  • aa496720618f1a6054f1c870bf10b4f6c99bf656
LinuxLinuxAffected
  • ≥ e624d4ed4aa8cc3c69d1359b0aaea539203ed266, < a9bb2d9c798cb62a4050a991c27b752770c33afe
Fixed in
  • a9bb2d9c798cb62a4050a991c27b752770c33afe
LinuxLinuxAffected
  • ≥ e624d4ed4aa8cc3c69d1359b0aaea539203ed266, < 51d07c12ca411e692c424ecdabf077f1e61a61be
Fixed in
  • 51d07c12ca411e692c424ecdabf077f1e61a61be
LinuxLinuxAffected
  • ≥ e624d4ed4aa8cc3c69d1359b0aaea539203ed266, < 47baddc856ae7e93a565dd9deeb797999b179466
Fixed in
  • 47baddc856ae7e93a565dd9deeb797999b179466

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

Community reviews

Loading reviews…