CVE-2026-99462

published 19 Nov 2026 · updated 20 Nov 2026

mm/truncate: look up the end-edge straddler by index

5.0MediumEPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 0fab93d241cfb6f3aae29530a9a214157bb64087, Kernel 863ecacdae9ebac39e25a3e90e6cec3e86bc856a, Kernel f47dee903b9f0f1e4e7181e8a398a7678cabf0a5 and 2 more.

In the Linux kernel, the following vulnerability has been resolved: mm/truncate: look up the end-edge straddler by index In truncate_inode_partial_folio(), after the first split at the start edge, folio_split() unlocks and drops the refcount of the after-split sub-folios. The sub-folio straddling the end of the truncation range is therefore unlocked and only transiently ref'd in the page cache while the code still derives it from a page pointer inside the original folio. Between the first split finishing and page_folio() resolving split_at2, that tail page can be reclaimed, freed and reallocated as a new large folio in the same mapping at a different file offset. folio2 then points at a folio that does not cover the end boundary, yet folio2->mapping == folio->mapping still holds, so the stale pointer passes the mapping check and folio_split_or_unmap() splits a folio at a wrong position (or, with a transient refcount, a use-after-free window opens between try_get and the split). __folio_split()'s own folio != page_folio(split_at) check cannot catch this either since split_at2 has been reallocated as part of the new folio, so page_folio(split_at2) resolves back to folio2. Look the straddler up by its page index instead. __filemap_get_folio() returns the folio currently covering the boundary, ref'd and locked, with the mapping validated under the lock, so the split target is always the real folio at the end edge.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=6.15, >=7460b470a131f985a70302a322617121efdd7caa <0fab93d241cfb6f3aae29530a9a214157bb64087, >=7460b470a131f985a70302a322617121efdd7caa <863ecacdae9ebac39e25a3e90e6cec3e86bc856a, >=7460b470a131f985a70302a322617121efdd7caa <f47dee903b9f0f1e4e7181e8a398a7678cabf0a50fab93d241cfb6f3aae29530a9a214157bb64087, 863ecacdae9ebac39e25a3e90e6cec3e86bc856a, f47dee903b9f0f1e4e7181e8a398a7678cabf0a5
linux-kernel: Kernel>=6.15.0 <6.18.63, >=6.19.0 <7.3.26.18.63, 7.3.2

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-99462 severity on Zeptric[![CVE-2026-99462](https://zeptric.io/badge/cve/CVE-2026-99462.svg)](https://zeptric.io/cve/CVE-2026-99462)