PT-2026-152534

CVE-2026-99654

·

Published

2026-11-20

·

Updated

2026-11-20

Description by

Score
N/A
Not available

No severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.

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.
Vendors
Affected products
Related identifiers
Found an issue in the description? Have something to add? Feel free to write us 👾