CVE-2026-99707: Linux kernel · mm/khugepaged: flush deferred unmaps before dropping a failed folio
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in d9d621ad49a969587d32c98aee1d83e679b9d361 : patch Linux kernel soon.
Data as of 20 Nov 2026, 06:36 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 d9d621ad49a969587d32c98aee1d83e679b9d361, cf1902ab0203f8767a3582143049d1bea5422096, 854e5ff8b3ce2a776586cabebaeae645c992345b +1
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 d9d621ad49a969587d32c98aee1d83e679b9d361, cf1902ab0203f8767a3582143049d1bea5422096, 854e5ff8b3ce2a776586cabebaeae645c992345b or 8c4adb787f77318df3b478f928f271e26d557208.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix is available and has been applied in the Linux kernel versions identified by commits d9d621ad49a969587d32c98aee1d83e679b9d361, cf1902ab0203f8767a3582143049d1bea5422096, 854e5ff8b3ce2a776586cabebaeae645c992345b, and 8c4adb787f77318df3b478f928f271e26d557208. Users and administrators should update to a kernel version including these fixes to mitigate the vulnerability.
Description
A vulnerability in the Linux kernel's memory management subsystem (mm/khugepaged) involves improper flushing of deferred unmaps before dropping a failed folio. This flaw can lead to a CPU retaining a user translation to a freed folio, potentially causing stale memory references. The issue arises when collapse_file() fails certain checks after unmapping, allowing another collapse to replace and free the folio while its page-table entries are gone, preventing proper TLB flushes. This has been reproduced with unprivileged MADV_COLLAPSE on a memfd. The vulnerability is fixed by ensuring flush occurs while the lookup reference and folio lock are still held.
References
- git.kernel.org/stable/c/d9d621ad49a969587d32c98aee1d83e679b9d361 (opens in a new tab)
- git.kernel.org/stable/c/cf1902ab0203f8767a3582143049d1bea5422096 (opens in a new tab)
- git.kernel.org/stable/c/8c4adb787f77318df3b478f928f271e26d557208 (opens in a new tab)
- git.kernel.org/stable/c/854e5ff8b3ce2a776586cabebaeae645c992345b (opens in a new tab)