Affects the Linux kernel netfs subsystem used broadly on servers and storage; can cause data corruption or DoS across many deployments.
CVE-2026-72366
Linux kernel netfs bug may bypass cache writes causing data loss or DoS
Is CVE-2026-72366 being exploited?
Not confirmed. CVE-2026-72366 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.64% probability of exploitation in the next 30 days.
How severe is CVE-2026-72366?
CVE-2026-72366 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-72366?
Yes. A fix has been recorded for CVE-2026-72366. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-72366 affect?
CVE-2026-72366 affects Linux kernel (netfs/fscache), Systems using network filesystems (NFS, CIFS, others). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-72366?
Apply vendor/kernel security updates and reboot affected systems immediately.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Netfs write ops can skip fscache_begin_write_operation, leading to cache bypass, potential data loss/corruption or kernel crashes (denial of service) via network file writes.
Immediate action required
- affected>= 7b589a9b45ae32aa9d7bece597490e141198d7a6 and < 8ab75e445c161c4cb504aa98e20ce1dd1ecd8e9a
- affected>= 7b589a9b45ae32aa9d7bece597490e141198d7a6 and < 1188a9846fadeacf9d1430b528e5217f749d665b
- affected>= 7b589a9b45ae32aa9d7bece597490e141198d7a6 and < dbd6f56d975b23241b7bbb11bb8f562af548a0aa
- affected6.11
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.