CVE-2026-89615

HIGHCVSS 8.4/10EPSS 0.15%

Last modified

CVE-2026-89615 is a high-severity vulnerability rated 8.4/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: bound page_lcns[] index by the log record The copy_lcns loop and the redo shorten loop index page_lcns[] at j + i, where i runs up to the log record's lcns_follow. That count is checked only against the record's own length, not the target entry, so check_dp_table() (which validates the entry's lcns_follow) does not cover it: the copy_lcns entry may even be freshly allocated after that check, and find_dp() bounds j but not i. EPSS estimates a 0.15% chance of exploitation in the next 30 days.

Description

In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: bound page_lcns[] index by the log record The copy_lcns loop and the redo shorten loop index page_lcns[] at j + i, where i runs up to the log record's lcns_follow. That count is checked only against the record's own length, not the target entry, so check_dp_table() (which validates the entry's lcns_follow) does not cover it: the copy_lcns entry may even be freshly allocated after that check, and find_dp() bounds j but not i. A crafted record thus overflows page_lcns[] of an otherwise valid entry. Add dp_range_ok() and reject, before each loop, any record whose run does not fit the entry. These are the only two page_lcns[] accesses indexed by the record rather than the entry, so together with the entry validation every access is now bounded. [almaz.alexandrovich@paragon-software.com: original patch contained changes to the problem already handled, applied partly]

Metrics

EPSS Probability
0.15%

4.9th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= b46acd6a6a627d876898e1c84d3f84902264b445, < 31fdd11f75da9823500168cecb07aa45130915a3; >= b46acd6a6a627d876898e1c84d3f84902264b445, < bb742d1030864c0fe140666f639428ba4e90b2ca; >= b46acd6a6a627d876898e1c84d3f84902264b445, < 61ca8cbbf68f77f25b699ed4358bd232f94ed43b; >= b46acd6a6a627d876898e1c84d3f84902264b445, < f4c1bc6d7331f344ffcea93c2a37badcbe15baa6; >= b46acd6a6a627d876898e1c84d3f84902264b445, < 7ccb94901f38a062034b56b43c774050b113758f; >= b46acd6a6a627d876898e1c84d3f84902264b445, < 1135ebc225996b3ac1a295652b19a0a706737a6c; >= b46acd6a6a627d876898e1c84d3f84902264b445, < 6f7b9dbdc1b7520206abce0049bdd143eb536e75
LinuxLinux5.15

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-89615?
In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: bound page_lcns[] index by the log record The copy_lcns loop and the redo shorten loop index page_lcns[] at j + i, where i runs up to the log record's lcns_follow. That count is checked only against the record's own length, not the target entry, so check_dp_table() (which validates the entry's lcns_follow) does not cover it: the copy_lcns entry may even be freshly allocated after that check, and find_dp() bounds j but not i. A crafted record thus overflows page_lcns[] of an otherwise valid entry. Add dp_range_ok() and reject, before each loop, any record whose run does not fit the entry. These are the only two page_lcns[] accesses indexed by the record rather than the entry, so together with the entry validation every access is now bounded. [almaz.alexandrovich@paragon-software.com: original patch contained changes to the problem already handled, applied partly]
How severe is CVE-2026-89615?
CVE-2026-89615 has a CVSS score of 8.4/10 (HIGH severity). The EPSS model estimates a 0.15% probability of exploitation in the next 30 days.
How do I fix CVE-2026-89615?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-89615?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST