Skip to content
major vulnerability· requires attention

Kernel-level use-after-free in widely deployed Linux lockd (NLM/NFS). Can crash or allow kernel compromise on many servers/clients; public kernel patches exist. Enterprise-wide impact.

Systems

CVE-2026-89485

9.8
Critical
EPSS 0.70%Patch availableSep 13, 2026

Linux kernel lockd use-after-free can crash or enable kernel compromise via NFS

common questions

Is CVE-2026-89485 being exploited?

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

How severe is CVE-2026-89485?

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

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

What does CVE-2026-89485 affect?

CVE-2026-89485 affects Linux kernel (lockd/NLM), NFS servers and clients using lockd, Linux distributions with unpatched kernels. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-89485?

Install vendor kernel updates or apply upstream patch immediately

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

executive summary
technical analysis
affected
Linux kernel (lockd/NLM)NFS servers and clients using lockdLinux distributions with unpatched kernels
impact

Use-after-free in lockd (NLM) can be triggered via NFS or locally to cause kernel crash (DoS) or potentially escalate to kernel code execution.

action required

Immediate action required

affected versions
Linux Linux
  • affected>= 01df9c5e918ae5559f2d96da0143f8bfbb9e6171 and < c24bdb7df2f34bdc38ca8a73796f5acb40f1830c
  • affected>= 01df9c5e918ae5559f2d96da0143f8bfbb9e6171 and < 41f0a6d31615fcae261bf28a0aa50050dc93a401
  • affected>= 01df9c5e918ae5559f2d96da0143f8bfbb9e6171 and < e999a88133654c6dfc68487fb49da5f20dfa2d4f
  • affected>= 01df9c5e918ae5559f2d96da0143f8bfbb9e6171 and < 526c49cff3f72c3ec74752016380c7567040581b
  • affected2.6.18
vendor says fixed in< 2.6.18, >= 6.12.109 and <= 6.12.*, >= 6.18.50 and <= 6.18.*, >= 7.2.4 and <= 7.2.*, >= 7.3-rc1 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