CVE-2026-99733: Linux kernel · mm/truncate: look again if a folio left the mapping
Affects Linux kernelSource CVE Database V5
Not known to be exploited : upgrade to f17044fee422605d19e07c4c9f5dc2be7abd7086 or 9cf632e139737314afa889ca18122bc3fddb9120 soon.
Data as of 20 Nov 2026, 06:34 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 f17044fee422605d19e07c4c9f5dc2be7abd7086, 9cf632e139737314afa889ca18122bc3fddb9120
Exploitation evidence
Disclosed: evidence found.
CVE published 20 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 19 Nov 2026.
What to do
Upgrade Linux kernel to f17044fee422605d19e07c4c9f5dc2be7abd7086 or 9cf632e139737314afa889ca18122bc3fddb9120.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix has been implemented and is available in the Linux kernel versions identified by commits f17044fee422605d19e07c4c9f5dc2be7abd7086 and 9cf632e139737314afa889ca18122bc3fddb9120. Users and administrators should apply these updates to ensure the vulnerability is resolved. No additional mitigation steps are indicated beyond applying the official fix.
Description
A vulnerability in the Linux kernel's memory management subsystem (mm/truncate) allows a stale folio with old data to remain in the page cache after a write operation completes. This occurs because invalidate_inode_pages2_range() may skip a folio that no longer belongs to the mapping, assuming it was removed, but the folio could have been replaced by a new one at the same index. The issue particularly affects collapse_file() and truncate_inode_pages_range() functions, potentially causing stale data to persist in the page cache.