Skip to content
major vulnerability· requires attention

Linux kernel is core infrastructure; an ntfs3 kernel-level overflow can enable widespread RCE/privilege escalation across many systems and distributions.

Systems

CVE-2026-89615

8.4
High
EPSS 0.15%Patch availableSep 13, 2026

ntfs3 kernel bug allows kernel memory corruption, escalation or DoS

common questions

Is CVE-2026-89615 being exploited?

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

How severe is CVE-2026-89615?

CVE-2026-89615 is rated High with a CVSS score of 8.4. 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-89615?

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

What does CVE-2026-89615 affect?

CVE-2026-89615 affects Linux kernel (ntfs3 filesystem driver), Linux distributions with affected kernel versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-89615?

Apply kernel updates containing the ntfs3 fix; avoid mounting untrusted NTFS media until patched.

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

executive summary
technical analysis
affected
Linux kernel (ntfs3 filesystem driver)Linux distributions with affected kernel versions
impact

Out-of-bounds write in ntfs3 via crafted NTFS log record -> kernel memory corruption enabling RCE, local privilege escalation, or DoS when processing/mounting volumes.

action required

Immediate action required

affected versions
Linux Linux
  • affected>= b46acd6a6a627d876898e1c84d3f84902264b445 and < f4c1bc6d7331f344ffcea93c2a37badcbe15baa6
  • affected>= b46acd6a6a627d876898e1c84d3f84902264b445 and < 7ccb94901f38a062034b56b43c774050b113758f
  • affected>= b46acd6a6a627d876898e1c84d3f84902264b445 and < 1135ebc225996b3ac1a295652b19a0a706737a6c
  • affected>= b46acd6a6a627d876898e1c84d3f84902264b445 and < 6f7b9dbdc1b7520206abce0049bdd143eb536e75
  • affected5.15
vendor says fixed in< 5.15, >= 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