PatchSiren cyber security CVE debrief
CVE-2026-64355 Linux CVE debrief
A vulnerability in the Linux kernel's bpf (Berkeley Packet Filter) implementation can lead to an out-of-bounds access during frame return when handling fragmented native XDP frames in devmap. This issue arises because cloning a fragmented frame leaves XDP_FLAGS_HAS_FRAGS set but without valid frag metadata. The vulnerability has been resolved by rejecting fragmented native XDP frames in dev_map_enqueue_clone() and adding the same restriction to the generic XDP clone path in dev_map_redirect_clone().
- Vendor
- Linux
- Product
- Unknown
- CVSS
- CRITICAL 9.8
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-07-25
- Original CVE updated
- 2026-10-19
- Advisory published
- 2026-07-25
- Advisory updated
- 2026-10-19
Who should care
Defenders responsible for Linux kernel security, Linux system administrators, and security teams should assess exposure and prioritize patching to prevent potential out-of-bounds access during frame return.
Why it matters
The Linux kernel's bpf implementation has a vulnerability that can lead to an out-of-bounds access during frame return when handling fragmented native XDP frames in devmap. Defenders should prioritize verifying their Linux kernel versions and applying patches to prevent potential out-of-bounds access during frame return.
- Verify Linux kernel versions to prevent potential out-of-bounds access during frame return
- Update affected Linux systems to ensure they are running a patched version
- Monitor Linux kernel updates and apply patches as needed to prevent exploitation
Technical summary
The Linux kernel's bpf implementation has a vulnerability that can lead to an out-of-bounds access during frame return when handling fragmented native XDP frames in devmap. The issue arises because cloning a fragmented frame leaves XDP_FLAGS_HAS_FRAGS set but without valid frag metadata. The vulnerability has been resolved by rejecting fragmented native XDP frames in dev_map_enqueue_clone() and adding the same restriction to the generic XDP clone path in dev_map_redirect_clone().
Defensive priority
Defenders should prioritize verifying their Linux kernel versions and applying patches to prevent potential out-of-bounds access during frame return.
Recommended defensive actions
- Verify Linux kernel versions and apply patches to prevent potential out-of-bounds access during frame return
- Review and update affected Linux systems to ensure they are running a patched version
- Monitor Linux kernel updates and apply patches as needed
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented.
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
- Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
Evidence notes
The CVE record and source item provide details on the vulnerability, its impact, and the resolution. However, the corpus does not establish specific versions that are affected or fixed, requiring verification from the supplied official sources.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-64355 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-64355
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-64355 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-64355
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
bpf: Reject fragmented frames in devmap
Unverified legacy reference
URL: https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/64xxx/CVE-2026-64355.json
cve_program_cvelist_v5
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/47baddc856ae7e93a565dd9deeb797999b179466
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/07a4c11ee8ef4abcb39d922e9e410ae269671cdf
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/bccbab36ff228e0825eb85d9b0f9b8434cd0a399
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/c5b4f5efcb55c1af3fe44ff712d31b7fb098a831
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/a9bb2d9c798cb62a4050a991c27b752770c33afe
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/51d07c12ca411e692c424ecdabf077f1e61a61be
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/aa496720618f1a6054f1c870bf10b4f6c99bf656
Supplemental source
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.