Widespread Linux kernel vulnerability in sunrpc/RPC used by many servers; can cause kernel compromise or widespread service disruption and requires org-wide remediation.
CVE-2026-72220
Linux kernel sunrpc double-free/UAF allowing kernel compromise or crash.
Is CVE-2026-72220 being exploited?
Not confirmed. CVE-2026-72220 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.59% probability of exploitation in the next 30 days.
How severe is CVE-2026-72220?
CVE-2026-72220 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-72220?
Yes. A fix has been recorded for CVE-2026-72220. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-72220 affect?
CVE-2026-72220 affects Linux kernel (sunrpc/RPC/NFS server). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-72220?
Apply vendor kernel updates immediately; restrict/block RPC/NFS access until patched.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Memory corruption via crafted RPC requests leading to kernel crash, local/full privilege escalation, or potential remote code execution.
Immediate action required
- affected>= d9adbb6e10bf7d4223d3d521ede1b2052903bc5e and < 66014ab165cb01bfef5836939412a8ef98d5d5ff
- affected>= d9adbb6e10bf7d4223d3d521ede1b2052903bc5e and < 31ba490c02d476a5e4f90b8845932ac9db8aa71b
- affected>= d9adbb6e10bf7d4223d3d521ede1b2052903bc5e and < 18d216788bef06332ff8901670ecf1ed8f6eb614
- affected6.18
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.