CVE-2026-99654: Linux kernel · mm: fix unmap_mapping_range() beyond 4 GiB on 32-bit
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in cbf6c66a2ef46433092b41b87176755de32bf65b : update Linux kernel when convenient.
Data as of 20 Nov 2026, 06:04 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in cbf6c66a2ef46433092b41b87176755de32bf65b, 67e6d5468a7d693a00176713d44267e5360d63c3, 7a81bc23dade8082187be6d9cc36e4be4b7207e2 +7
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– |
Description
In the Linux kernel, the following vulnerability has been resolved: mm: fix unmap_mapping_range() beyond 4 GiB on 32-bit Commit 9eab0421fa94 ("mm: fix unmap_mapping_range high bits shift bug") made holebegin and holelen unsigned before they are shifted, by casting them to pgoff_t. That is an unsigned long: on a 32-bit kernel the cast cuts off the upper half of the two loff_t values, so a hole which begins at 4 GiB or beyond is taken for one in the first 4 GiB of the file. truncate_pagecache() passes the new size of the file and asks for private COWed pages to be unmapped as well. If a file of 6 GiB is truncated to 5 GiB, everything from 1 GiB on is unmapped, and what a process has written to a private mapping of the range between 1 GiB and 5 GiB is lost: it reads the contents of the file again. Where the range has an end, the wrong range is unmapped instead of the right one. The page cache copes with that, as it unmaps every folio that it removes. The callers which only have unmap_mapping_range() to get rid of user mappings do not, for example drm_vma_node_unmap(), whose fake offsets reach beyond 4 GiB on 32-bit, and revoke_iomem() with physical addresses of more than 32 bits. Cast to u64 instead. Nothing changes for 64-bit kernels. Fix generated by an LLM and sent by Josef Bacik in private.
References
- git.kernel.org/stable/c/cbf6c66a2ef46433092b41b87176755de32bf65b (opens in a new tab)
- git.kernel.org/stable/c/0cf8d3fdd869fe079e55f8e621e45397a819d93c (opens in a new tab)
- git.kernel.org/stable/c/67e6d5468a7d693a00176713d44267e5360d63c3 (opens in a new tab)
- git.kernel.org/stable/c/7a81bc23dade8082187be6d9cc36e4be4b7207e2 (opens in a new tab)