Skip to main content
Menu
CVEs

Linux kernel unmap_mapping_range data loss above 4 GiB on 32-bit

CVE-2026-99654Published November 20, 2026, updated

Exploited
No known exploitation
Fix
Fixed in 4.20, 5.5, 5.11, 5.16, 6.2, and 1 more
Who is exposed
Not reported

Summary

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.

What to do

Upgrade to a fixed version: 4.20, 5.5, 5.11, 5.16, 6.2, or one of 1 more.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-99654 (mm: fix unmap_mapping_range() beyond 4 GiB on 32-bit), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-99654 (entry last updated 2026-11-20):
Affected:
- Linux Linux: from 4.19.305, fixed in 4.20; from 5.4.267, fixed in 5.5; from 5.10.208, fixed in 5.11; from 5.15.147, fixed in 5.16; from 6.1.72, fixed in 6.2; from 6.6.11, fixed in 6.7
- Linux Linux: versions 6.7
Fixed versions: 4.20, 5.5, 5.11, 5.16, 6.2, 6.7.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-99654 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-99654 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://git.kernel.org/stable/c/cbf6c66a2ef46433092b41b87176755de32bf65b
- https://git.kernel.org/stable/c/0cf8d3fdd869fe079e55f8e621e45397a819d93c
- https://git.kernel.org/stable/c/67e6d5468a7d693a00176713d44267e5360d63c3
- https://git.kernel.org/stable/c/7a81bc23dade8082187be6d9cc36e4be4b7207e2
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-99654
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-99654"}.

Affected versions

cve.now Index

20Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure?/25Unknown. No advisory context yet
  • Reach20/20Affects Linux kernel (software on nearly every server, desktop or phone)
  • Severity?/10Unknown. No CVSS score or vendor rating
  • No patch0/5No signal

What would change the score

  • Would score about 75 if added to CISA KEV
  • Would score about 70 if CISA's SSVC rates exploitation active
  • Would score about 42 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 6

Questions about CVE-2026-99654

Is CVE-2026-99654 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-99654?

Linux: from 4.19.305 before 4.20; from 5.4.267 before 5.5; from 5.10.208 before 5.11; from 5.15.147 before 5.16; from 6.1.72 before 6.2; from 6.6.11 before 6.7. Linux: version 6.7.

Source: cve.now feed data

How do I fix CVE-2026-99654?

Upgrade to a fixed version: 4.20, 5.5, 5.11, 5.16, 6.2, or one of 1 more.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.