Skip to content
major vulnerability· requires attention

Linux kernel flaw can crash or allow kernel compromise across widely deployed OSes and infrastructure; high-impact for most organizations.

Systems

CVE-2026-72463

9.8
Critical
EPSS 0.38%Patch availableAug 17, 2026

Kernel xfrm use-after-free in async resumption allows kernel crash or compromise.

common questions

Is CVE-2026-72463 being exploited?

Not confirmed. CVE-2026-72463 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.38% probability of exploitation in the next 30 days.

How severe is CVE-2026-72463?

CVE-2026-72463 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-72463?

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

What does CVE-2026-72463 affect?

CVE-2026-72463 affects Linux kernel (xfrm/IPsec subsystem), Virtual Tunnel Interface (VTI) devices, Linux distributions using affected kernels. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-72463?

Apply vendor kernel updates and reboot affected hosts; restrict IPsec/VTI exposure until patched.

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

executive summary
technical analysis
affected
Linux kernel (xfrm/IPsec subsystem)Virtual Tunnel Interface (VTI) devicesLinux distributions using affected kernels
impact

Crafted network packets can trigger a use-after-free of tunnel devices, causing kernel crash (DoS) or possible kernel code execution/privilege escalation.

action required

Immediate action required

affected versions
Linux Linux
  • affected>= 1c428b03840094410c5fb6a5db30640486bbbfcb and < 63a30015199912bd5055bead8001b1ae68a67cdb
  • affected>= 1c428b03840094410c5fb6a5db30640486bbbfcb and < 8045c0df98d4f14c54e5cb875f1c9c0ce89fe4ff
  • affected4236c30b437b80f673b9e08c8fae38b8d471ac9e
  • affected0f451b43c88bf2b9c038b414be580efee42e031b
  • affected5002beda5cac69d522dc54da0d5d463ed9c963d2
  • affected>= 6.12.94 and < 6.13
  • affected>= 6.18.23 and < 6.19
  • affected>= 6.19.13 and < 6.20
  • affected7.0
vendor says fixed in< 7.0, >= 7.1.5 and <= 7.1.*, >= 7.2 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