Answer in brief
CVE-2026-89612 records a Critical severity (CVSS 9.8) vulnerability in ntfs: reject invalid MFT LCNs from boot sector. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 9.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=11ccc9107dc460de28af90fac1f42404d9802735 <8f8420b68a6f05ca2b03779d8208814ec539b9e5 || >=11ccc9107dc460de28af90fac1f42404d9802735 <cc9d09fef78410bcd37ac05168cbd5f6dd75d3d2 | 8f8420b68a6f05ca2b03779d8208814ec539b9e5, cc9d09fef78410bcd37ac05168cbd5f6dd75d3d2 |
| Linux/Linuxgeneric | 7.1 | Not reported |
Published upstream
Sep 11, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 11, 2026
In the Linux kernel, the following vulnerability has been resolved: ntfs: reject invalid MFT LCNs from boot sector The NTFS boot sector stores the MFT and MFTMirr locations as unsigned 64-bit LCNs, but parse_ntfs_boot_sector() decoded them into an s64. A crafted high-bit value could therefore become negative and pass the existing upper-bound check. The invalid value then propagated into the MFT zone allocator and could result in an out-of-bounds access to lcn_empty_bits_per_page.
Quoted source text, attributed separately from HOL analysis.