CVE-2026-99642: Linux kernel · mm/gup: check folio->mapping under folio lock in memfd_pin_folios()
Source GCVE Database
Not known to be exploited · fixed in 71555ae8c7572fd99158013ca2e29187c5d2508d : patch Linux kernel soon.
Data as of 20 Nov 2026, 07:34 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 71555ae8c7572fd99158013ca2e29187c5d2508d, 4480eb27975b91a28bc058a2ca16f466ebd9d7cd, 240bc9b873d3522672db13ea93ec73b7f0461912 +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 71555ae8c7572fd99158013ca2e29187c5d2508d, 4480eb27975b91a28bc058a2ca16f466ebd9d7cd, 240bc9b873d3522672db13ea93ec73b7f0461912 or 6ac69b444b85d0e511d9bc15f586ebeed49322fa.
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– |
Description
In the Linux kernel, the following vulnerability has been resolved: mm/gup: check folio->mapping under folio lock in memfd_pin_folios() memfd_pin_folios() pins folios from the page cache without taking the folio lock. khugepaged or MADV_COLLAPSE can therefore replace a folio after checking its refcount while memfd_pin_folios() still pins the old folio. The caller then receives a folio which is no longer part of the memfd. For udmabuf and iommufd, this can cause data corruption: DMA accesses the detached folio rather than the live memfd contents. DMA reads can return stale data, while DMA writes update the detached copy and are lost from the live memfd. The detached folio remains pinned, so these accesses do not constitute a use-after-free or target another application's memory. For memfd live update, the stale contents can reappear in the memfd after handover. Lock the folio and recheck folio->mapping before pinning it, like other page cache users do. If the folio was removed, retry the folio lookup from the index that was removed.
References
- nvd.nist.gov/vuln/detail/CVE-2026-99642 (opens in a new tab)
- git.kernel.org/stable/c/240bc9b873d3522672db13ea93ec73b7f0461912 (opens in a new tab)
- git.kernel.org/stable/c/4480eb27975b91a28bc058a2ca16f466ebd9d7cd (opens in a new tab)
- git.kernel.org/stable/c/6ac69b444b85d0e511d9bc15f586ebeed49322fa (opens in a new tab)
- git.kernel.org/stable/c/71555ae8c7572fd99158013ca2e29187c5d2508d (opens in a new tab)