CVE-2026-99462
Severity unknownNo known exploitationFix availablemm/truncate: look up the end-edge straddler by index
Record last updated
CVSS score
No score published yet
EPSS, chance of exploitation in 30 days
Higher than 6% of scored CVEs. A prediction, not evidence.
CISA remediation deadline
Not in the KEV catalog
Description
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.
Patching and mitigation
- Patch status
- Fix available (source: CVE record (Linux))
- Fix documented (source date)
- Mitigation
- None documented
- Vendor guidance
- No vendor link on record
Affected products
| Vendor | Product | Affected versions | Fixed in | Per |
|---|---|---|---|---|
| Linux | Linux | from 7460b470a131f985a70302a322617121efdd7caa before 863ecacdae9ebac39e25a3e90e6cec3e86bc856a | 863ecacdae9ebac39e25a3e90e6cec3e86bc856a | CVE Program |
| Linux | Linux | from 7460b470a131f985a70302a322617121efdd7caa before f47dee903b9f0f1e4e7181e8a398a7678cabf0a5 | f47dee903b9f0f1e4e7181e8a398a7678cabf0a5 | CVE Program |
| Linux | Linux | from 7460b470a131f985a70302a322617121efdd7caa before 0fab93d241cfb6f3aae29530a9a214157bb64087 | 0fab93d241cfb6f3aae29530a9a214157bb64087 | CVE Program |
| Linux | Linux | 6.15 | Not documented | CVE Program |
| Linux | Linux (unaffected) | from 6.18.63 up to and including 6.18.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | from 7.3.2 up to and including 7.3.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | 7.4-rc1 | Not documented | CVE Program |
| Linux | Linux (unaffected) | all versions before 6.15 | Not documented | CVE Program |
Timeline
Disclosure
CVE record published by Linux
Source: CVE Program (opens in a new tab)
Patch
Fix documented by CVE record (Linux)