Skip to content
major vulnerability· requires attention

Kernel-level memory-corruption in widely deployed Linux kernels (XDP/AF_XDP) can crash or enable escalation across many environments; impacts core infrastructure.

Systems

CVE-2026-81002

9.8
Critical
EPSS 0.52%Patch availableSep 13, 2026

Linux kernel XDP/AF_XDP zero-copy bug causes kernel memory corruption and panic.

common questions

Is CVE-2026-81002 being exploited?

Not confirmed. CVE-2026-81002 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.52% probability of exploitation in the next 30 days.

How severe is CVE-2026-81002?

CVE-2026-81002 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-81002?

Yes. A fix has been recorded for CVE-2026-81002. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-81002 affect?

CVE-2026-81002 affects Linux kernel (XDP/AF_XDP, cpumap), Systems using AF_XDP zero-copy or cpumap redirection. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-81002?

Apply kernel patches/backports immediately and reboot affected hosts

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Linux kernel (XDP/AF_XDP, cpumap)Systems using AF_XDP zero-copy or cpumap redirection
impact

Out-of-bounds write via AF_XDP zero-copy cpumap redirection: kernel panic, memory corruption and potential local privilege escalation or RCE.

action required

Immediate action required

affected versions
Linux Linux
  • affected>= b0d1beeff2a97a0cf1965ea8f1d13b8973f22582 and < 444216dacdbebd3e52d5e704facafbb230da09e9
  • affected>= b0d1beeff2a97a0cf1965ea8f1d13b8973f22582 and < 15d1f3c0dbe7a740f779337deb39f23cd8d002c8
  • affected>= b0d1beeff2a97a0cf1965ea8f1d13b8973f22582 and < 68d7cc5512238693670fc19c7a615df631e10edf
  • affected>= b0d1beeff2a97a0cf1965ea8f1d13b8973f22582 and < 71283aaa6c65b3cec84caf1dc78560985737641f
  • affected4.20
vendor says fixed in< 4.20, >= 6.12.109 and <= 6.12.*, >= 6.18.50 and <= 6.18.*, >= 7.2.4 and <= 7.2.*, >= 7.3-rc1 and <= *

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free