Affects Linux kernel nfsd (widely deployed OS/component); kernel-level bug can disrupt infrastructure and is newsworthy.
CVE-2026-89697
Linux NFS server kernel bug allows kernel corruption via malformed SETATTR
Is CVE-2026-89697 being exploited?
Not confirmed. CVE-2026-89697 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.69% probability of exploitation in the next 30 days.
How severe is CVE-2026-89697?
CVE-2026-89697 is rated Critical with a CVSS score of 9.1. 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-89697?
Yes. A fix has been recorded for CVE-2026-89697. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-89697 affect?
CVE-2026-89697 affects Linux kernel (nfsd module), NFS servers on Linux distributions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-89697?
Apply vendor kernel updates for nfsd and restart NFS services immediately
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote NFS client can trigger notify_change without mount write ref, risking kernel memory corruption leading to privilege escalation or DoS.
Immediate action required
- affected>= cc265089ce1b176dde963c74b53593446ee7f99a and < 3eec9d791968c177a4a8cda9af5c04f79dae09cb
- affected>= cc265089ce1b176dde963c74b53593446ee7f99a and < 9229d824b938f4fb0ea7a5dddade51735e6fe6f9
- affected>= cc265089ce1b176dde963c74b53593446ee7f99a and < 2150305134889fb2fc25228d35353bd2f6f29500
- affected>= cc265089ce1b176dde963c74b53593446ee7f99a and < d823bf9285cdf4514873b85ab5a888878dd4e8f4
- affected>= cc265089ce1b176dde963c74b53593446ee7f99a and < 15ca3b64a69caa6194bed8f98a20ed90a11c11dd
- affected>= cc265089ce1b176dde963c74b53593446ee7f99a and < 533964d420d385e11b08dd4c56c66ef5dcccaf08
- affected>= cc265089ce1b176dde963c74b53593446ee7f99a and < c4a409b86a92815181a8e9395c6bf1696ad19175
- affected>= cc265089ce1b176dde963c74b53593446ee7f99a and < 4e475be769aa9f7a2c1ce55a2b8592cfccacddcc
- affected1cb57d81cf20fe24b9e2e1daf57bfbdc24b77cd8
- affected>= 3.18.46 and < 3.19
- affected4.2
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.