Answer in brief
CVE-2026-98140 records a Unknown severity vulnerability in ntfs: fix kmap_local leak in write_mft_record_nolock() error paths. 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.
A CVSS score is not reported in the current record. 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 | >=115380f9a2f9675c7924563cbba70d40cae8fb81 <5d7f7bf8fba8cf563b42b44aa4ab3d9928ac480c || >=115380f9a2f9675c7924563cbba70d40cae8fb81 <cf06dcd572845723821b54a608fc2da995c3c8e2 | 5d7f7bf8fba8cf563b42b44aa4ab3d9928ac480c, cf06dcd572845723821b54a608fc2da995c3c8e2 |
| Linux/Linuxgeneric | 7.1 | Not reported |
Published upstream
Sep 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 25, 2026
In the Linux kernel, the following vulnerability has been resolved: ntfs: fix kmap_local leak in write_mft_record_nolock() error paths write_mft_record_nolock() maps the MFT record folio with kmap_local_folio(), but the pre_write_mst_fixup() and bio_add_folio() failure paths jump to the error label without unmapping it. kmap_local mappings are stack-ordered per task, so leaking one corrupts the nesting for any outer mapping. Unmap the folio on those error paths too.
Quoted source text, attributed separately from HOL analysis.