Linux kernel is ubiquitous; a kernel use-after-free can enable system compromise or widespread outages across enterprises.
CVE-2026-64216
Linux kernel netfs use-after-free enabling kernel compromise or DoS
Is CVE-2026-64216 being exploited?
Not confirmed. CVE-2026-64216 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.46% probability of exploitation in the next 30 days.
How severe is CVE-2026-64216?
CVE-2026-64216 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-64216?
Yes. A fix has been recorded for CVE-2026-64216. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-64216 affect?
CVE-2026-64216 affects Linux kernel (netfs subsystem), Distributions using affected kernel versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-64216?
Apply vendor kernel updates or backported fixes immediately
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Local attacker can trigger a netfs use-after-free, leading to kernel crash, privilege escalation, or arbitrary kernel code execution.
Immediate action required
- affected>= ee4cdf7ba857a894ad1650d6ab77669cbbfa329e and < d4ae8dba90b89e7bb4d1045d1cb26afbaf13ee5c
- affected>= ee4cdf7ba857a894ad1650d6ab77669cbbfa329e and < 6080fa3ecfbb4448a3b47368629534c09b6ec750
- affected>= ee4cdf7ba857a894ad1650d6ab77669cbbfa329e and < 3866d015f33aeedf81338dd99154703bef33faef
- affected>= ee4cdf7ba857a894ad1650d6ab77669cbbfa329e and < dbe556972100fabb8e5a1b3d2163831ff07b1e8e
- affected6.12
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.