# CVE-2026-99654: mm: fix unmap_mapping_range() beyond 4 GiB on 32-bit

Status: published. Published: 2026-11-20. Updated: 2026-11-22.

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.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Linux / Linux: ≥ 9eab0421fa94a3dde0d1f7e36ab3294fc306c99d; < cbf6c66a2ef46433092b41b87176755de32bf65b (affected, git); ≥ 9eab0421fa94a3dde0d1f7e36ab3294fc306c99d; < 0cf8d3fdd869fe079e55f8e621e45397a819d93c (affected, git); ≥ 9eab0421fa94a3dde0d1f7e36ab3294fc306c99d; < 67e6d5468a7d693a00176713d44267e5360d63c3 (affected, git); ≥ 9eab0421fa94a3dde0d1f7e36ab3294fc306c99d; < 7a81bc23dade8082187be6d9cc36e4be4b7207e2 (affected, git); 2db1c46c3913b8bc92fed235a344de2671fe9d8d (affected, git); 77359c4973056ba33a5627d5c04aea494eb76bc9 (affected, git); 73704c6b35c7682fd22f97992a68b0e8451c7a52 (affected, git); 91432aebce514cab49f63324c98b4eccb80532c5 (affected, git); dafdeb7b91f1597983693a418c496b6702ea34b5 (affected, git); 2247df454c7bb4b13939794fe6fae8510868d241 (affected, git); ≥ 4.19.305; < 4.20 (affected, semver); ≥ 5.4.267; < 5.5 (affected, semver); ≥ 5.10.208; < 5.11 (affected, semver); ≥ 5.15.147; < 5.16 (affected, semver); ≥ 6.1.72; < 6.2 (affected, semver); ≥ 6.6.11; < 6.7 (affected, semver). Source: CNA: Linux
- Linux / Linux: 6.7 (affected); ≥ 0; < 6.7 (unaffected, semver); ≥ 6.12.118; ≤ 6.12.* (unaffected, semver); ≥ 6.18.64; ≤ 6.18.* (unaffected, semver); ≥ 7.3.5; ≤ 7.3.* (unaffected, semver); ≥ 7.4-rc2; ≤ * (unaffected, original_commit_for_fix). Source: CNA: Linux

## Severity and prioritization

- CVSS 3.1: 7.8 (high); CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H; source: CNA: Linux

- CVSS 3.1: 7.8 (high); CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H; source: NVD: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

- CISA KEV: No listing in collected sources

- EPSS: 0.17% as of 2026-11-21; percentile 6.20%

- SSVC: Not available

- Weaknesses: Not reported

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://git.kernel.org/stable/c/cbf6c66a2ef46433092b41b87176755de32bf65b (CNA: Linux)

- https://git.kernel.org/stable/c/0cf8d3fdd869fe079e55f8e621e45397a819d93c (CNA: Linux)

- https://git.kernel.org/stable/c/67e6d5468a7d693a00176713d44267e5360d63c3 (CNA: Linux)

- https://git.kernel.org/stable/c/7a81bc23dade8082187be6d9cc36e4be4b7207e2 (CNA: Linux)

- https://git.kernel.org/stable/c/0cf8d3fdd869fe079e55f8e621e45397a819d93c (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

- https://git.kernel.org/stable/c/67e6d5468a7d693a00176713d44267e5360d63c3 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

- https://git.kernel.org/stable/c/7a81bc23dade8082187be6d9cc36e4be4b7207e2 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

- https://git.kernel.org/stable/c/cbf6c66a2ef46433092b41b87176755de32bf65b (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

## Provenance

- CNA: Linux: https://www.cve.org/CVERecord?id=CVE-2026-99654; retrieved 2026-11-22; source updated 2026-11-22

- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-99654; retrieved 2026-11-22; source updated 2026-11-22

- FIRST EPSS: https://api.first.org/data/v1/epss?cve=CVE-2026-99654; retrieved 2026-11-22; source updated Not reported

Revision: 8d96f482569e7107096cd032b0ad85561586f18ed5df7f1c3b90330a3bde29b1

Canonical: https://y2.dev/cve/CVE-2026-99654

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.