CVE-2026-99654
What it is
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.
At a glance
- Fix
- No patch or advisory is linked yet. Look at mitigations or restrict exposure.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: not scored yet.
- Severity: not scored yet.
- Fix: none linked yet, which raises it.
Details
- Published
- Last modified
- Record status
- Received
Affected
- Linux < cbf6c66a2ef46433092b41b87176755de32bf65b
- Linux < 0cf8d3fdd869fe079e55f8e621e45397a819d93c
- Linux < 67e6d5468a7d693a00176713d44267e5360d63c3
- Linux < 7a81bc23dade8082187be6d9cc36e4be4b7207e2
- Linux 2db1c46c3913b8bc92fed235a344de2671fe9d8d
- Linux 77359c4973056ba33a5627d5c04aea494eb76bc9
- Linux 73704c6b35c7682fd22f97992a68b0e8451c7a52
- Linux 91432aebce514cab49f63324c98b4eccb80532c5
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-99654.md and follow it. Check whether this project is affected by CVE-2026-99654. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.