Linux kernel vulnerability in netfs affects broadly deployed OS kernel; can crash or escalate privileges across many servers and endpoints.
CVE-2026-64069
Linux netfs read cancellation bug causes kernel memory corruption.
Is CVE-2026-64069 being exploited?
Not confirmed. CVE-2026-64069 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.44% probability of exploitation in the next 30 days.
How severe is CVE-2026-64069?
CVE-2026-64069 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-64069?
Yes. A fix has been recorded for CVE-2026-64069. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-64069 affect?
CVE-2026-64069 affects Linux kernel (netfs subsystem), Network filesystem clients (e.g., NFS and other netfs-backed mounts). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-64069?
Apply vendor/mainline kernel patches and reboot affected hosts immediately.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Kernel memory corruption from failed netfs read subrequests; can cause kernel panic, denial of service, or local/remote privilege escalation.
Immediate action required
- affected>= e2d46f2ec332533816417b60933954173f602121 and < 5366199be46fb53de62861721d34ba816e7e440e
- affected>= e2d46f2ec332533816417b60933954173f602121 and < f73372a4c6900d117f8e903fe10b62692f95e6c4
- affected>= e2d46f2ec332533816417b60933954173f602121 and < 6f0f7ac1915abc0d202f0eb4b003a6548a5ba60d
- affected6.14
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.