Skip to content
major vulnerability· requires attention

Linux kernel flaw in netfs can allow kernel compromise across many distributions; widespread impact on servers and endpoints.

Systems

CVE-2026-64068

9.8
Critical
EPSS 0.34%Patch availableJul 21, 2026

Linux kernel netfs race leads to kernel memory corruption and potential root compromise.

common questions

Is CVE-2026-64068 being exploited?

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

How severe is CVE-2026-64068?

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

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

What does CVE-2026-64068 affect?

CVE-2026-64068 affects Linux kernel (netfs subsystem), All Linux distributions using vulnerable kernels, Servers, desktops, embedded devices running affected kernels. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-64068?

Apply vendor kernel updates or backported patches and reboot affected hosts immediately.

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

executive summary
technical analysis
affected
Linux kernel (netfs subsystem)All Linux distributions using vulnerable kernelsServers, desktops, embedded devices running affected kernels
impact

Kernel memory corruption via netfs subrequest race, enabling denial of service, local privilege escalation, or remote code execution.

action required

Immediate action required

affected versions
Linux Linux
  • affected>= 288ace2f57c9d06dd2e42bd80d03747d879a4068 and < d5c9d19b0ff2f7153532ac238a5e96fed2df315c
  • affected>= 288ace2f57c9d06dd2e42bd80d03747d879a4068 and < 393f3f0d7353a94b1e0bc4ca89c683fe983e5fd2
  • affected>= 288ace2f57c9d06dd2e42bd80d03747d879a4068 and < cce18c263e9623872327ba3c956012f73c1179cc
  • affected6.10
vendor says fixed in< 6.10, >= 6.18.50 and <= 6.18.*, >= 7.0.11 and <= 7.0.*, >= 7.1 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