CVE-2026-99462: Linux kernel · mm/truncate: look up the end-edge straddler by index
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in f47dee903b9f0f1e4e7181e8a398a7678cabf0a5 : patch Linux kernel soon.
Data as of 19 Nov 2026, 15:49 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in f47dee903b9f0f1e4e7181e8a398a7678cabf0a5, 863ecacdae9ebac39e25a3e90e6cec3e86bc856a, 0fab93d241cfb6f3aae29530a9a214157bb64087
Exploitation evidence
Disclosed: evidence found.
CVE published 19 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.
What to do
Upgrade Linux kernel to f47dee903b9f0f1e4e7181e8a398a7678cabf0a5, 863ecacdae9ebac39e25a3e90e6cec3e86bc856a or 0fab93d241cfb6f3aae29530a9a214157bb64087.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
This vulnerability has been fixed in the Linux kernel. The fix involves using __filemap_get_folio() to look up the folio by page index, ensuring the folio is valid and locked during truncation. Users should update to the fixed kernel versions identified by the commits f47dee903b9f0f1e4e7181e8a398a7678cabf0a5, 863ecacdae9ebac39e25a3e90e6cec3e86bc856a, and 0fab93d241cfb6f3aae29530a9a214157bb64087 or later.
Description
A vulnerability in the Linux kernel's memory management subsystem (specifically in the truncate_inode_partial_folio function) allows incorrect handling of folios during truncation. This can cause a stale pointer to be used when splitting folios, potentially leading to use-after-free conditions. The issue is fixed by changing the lookup method to use the page index, ensuring the correct folio is referenced and locked during the operation.