Skip to content
major vulnerability· requires attention

Affects the Linux kernel (ubiquitous OS kernel); local kernel LPE can impact many servers, desktops, and appliances — newsworthy and organization-wide risk.

Systems

CVE-2026-89610

9.8
Critical
EPSS 0.55%Patch availableSep 13, 2026

Local Linux kernel LPE via malformed NTFS mapping pairs

common questions

Is CVE-2026-89610 being exploited?

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

How severe is CVE-2026-89610?

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

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

What does CVE-2026-89610 affect?

CVE-2026-89610 affects Linux kernel (NTFS driver), Linux desktops, Linux servers, Embedded/IoT devices running Linux that mount NTFS. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-89610?

Apply the kernel update immediately and avoid mounting untrusted NTFS volumes.

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

executive summary
technical analysis
affected
Linux kernel (NTFS driver)Linux desktopsLinux serversEmbedded/IoT devices running Linux that mount NTFS
impact

Local privilege escalation to root via kernel memory corruption when mounting or processing a crafted NTFS image.

action required

Immediate action required

affected versions
Linux Linux
  • affected>= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 6e844d4b82434a781b80d02145fd1b17cf90e3c3
  • affected>= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < fea9e4488f384c0ef1c0e3d96b565127c1b98447
  • affected< 7.2.4
vendor says fixed in>= 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