CVE-2026-99740: Linux kernel · mm/shmem: stop retrying folios that cannot be split
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in dfedff4a9f0abcd985dcdfbd721dcd9374d6ff12 : patch Linux kernel soon.
Data as of 20 Nov 2026, 06:33 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 dfedff4a9f0abcd985dcdfbd721dcd9374d6ff12, b3239a5a37bba078d83cfb864d47a0cc122f17cd, a842a1f947da8a7020e72f885ffbf2ce6a93685f +3
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 to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix is available and has been applied in Linux kernel versions 6.2, 6.7, and associated commits. Users and administrators should update to these or later kernel versions to remediate this issue. No additional mitigation steps are indicated.
Description
A vulnerability in the Linux kernel's memory management subsystem (shmem) causes an infinite retry loop when handling large folios that cannot be split during file truncation. This occurs after shmem_undo_range() processes boundary folios, leading to a retained dirty folio that causes repeated scanning and looping while holding inode and directory locks. This can block directory operations during concurrent unlink() calls. The issue has been fixed in Linux kernel versions 6.2, 6.7, and related commits.
References
- git.kernel.org/stable/c/dfedff4a9f0abcd985dcdfbd721dcd9374d6ff12 (opens in a new tab)
- git.kernel.org/stable/c/1360e0f9a188cfede01d0df81119d925bbfff165 (opens in a new tab)
- git.kernel.org/stable/c/b3239a5a37bba078d83cfb864d47a0cc122f17cd (opens in a new tab)
- git.kernel.org/stable/c/a842a1f947da8a7020e72f885ffbf2ce6a93685f (opens in a new tab)