Skip to main content
No exploitation reportedFix availableAwaiting NVD analysis

CVE-2026-99654

mm: fix unmap_mapping_range() beyond 4 GiB on 32-bit

No exploitation reported by the sources we read.

  • Published2026-11-20
  • Fixed in7.3.5 · 6.18.64 · 6.12.118 · 6.7 · 6.2 · 5.16

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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.

Timeline

dates in UTC
  1. 2026-11-2005:50CVE publishedCNA

Versions per branch

OSV
Linux kernel
BranchAffectedFixed in
7.3≥ 6.19.0, < 7.3.57.3.5
6.x≥ 6.13.0, < 6.18.646.18.64
6.x≥ 6.7.0, < 6.12.1186.12.118
6.x≥ 6.6.11, < 6.76.7
6.x≥ 6.1.72, < 6.26.2
5.x≥ 5.15.147, < 5.165.16
5.x≥ 5.10.208, < 5.115.11
5.x≥ 5.4.267, < 5.55.5
4.x≥ 4.19.305, < 4.204.20

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA2 products

As Linux, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • Linuxother versions: not affected

    https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

    Affected
    • ≥ 9eab0421fa94a3dde0d1f7e36ab3294fc306c99d, < cbf6c66a2ef46433092b41b87176755de32bf65bfixed in cbf6c66a2ef46433092b41b87176755de32bf65bgit
    • ≥ 9eab0421fa94a3dde0d1f7e36ab3294fc306c99d, < 0cf8d3fdd869fe079e55f8e621e45397a819d93cfixed in 0cf8d3fdd869fe079e55f8e621e45397a819d93cgit
    • ≥ 9eab0421fa94a3dde0d1f7e36ab3294fc306c99d, < 67e6d5468a7d693a00176713d44267e5360d63c3fixed in 67e6d5468a7d693a00176713d44267e5360d63c3git
    • ≥ 9eab0421fa94a3dde0d1f7e36ab3294fc306c99d, < 7a81bc23dade8082187be6d9cc36e4be4b7207e2fixed in 7a81bc23dade8082187be6d9cc36e4be4b7207e2git
    • = 2db1c46c3913b8bc92fed235a344de2671fe9d8dno fix statedgit
    • = 77359c4973056ba33a5627d5c04aea494eb76bc9no fix statedgit
    • = 73704c6b35c7682fd22f97992a68b0e8451c7a52no fix statedgit
    • = 91432aebce514cab49f63324c98b4eccb80532c5no fix statedgit

    8 more version lines in the CVE record.

  • Linuxother versions: affected

    https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

    Affected
    • = 6.7no fix stated

    Not affected < 6.7 · ≥ 6.12.118, ≤ 6.12.* · ≥ 6.18.64, ≤ 6.18.* · ≥ 7.3.5, ≤ 7.3.* · ≥ 7.4-rc2

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE terms of useCVE recordupdated 2026-11-20

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • linuxDebian:14all versions · no fixed version listed
  • linuxDebian:13all versions · fixed in 6.12.118-1
  • linuxDebian:12all versions · no fixed version listed
  • linux-ltsAlpaquita:streamfrom 6.18.62-r0 · fixed in 6.18.64-r0
  • linux-ltsAlpaquita:25from 6.12.115-r0 · no fixed version listed
  • linux-ltsAlpaquita:23from 6.1.191-r1 · no fixed version listed

Vendor advisories

  • CVE-2026-99654 Red Hat Product Security125 known affected

    kernel: kernel: Data loss via memory range truncation on 32-bit systems

    kernel.src as a component of Red Hat Enterprise Linux 10 · kernel as a component of Red Hat Enterprise Linux 6 · kernel-abi-whitelists as a component of Red Hat Enterprise Linux 6 · +122 more

Full record on NVD

Fix

  1. Update Linux kernel to 7.3.5 · 6.18.64 · 6.12.118 · 6.7 · 6.2 · 5.16 · 5.11 · 5.5
  2. No fix available, says the vendor Red Hat Product Security CVE-2026-99654 · 111 productsFix deferred
  3. No fix planned, says the vendor Red Hat Product Security CVE-2026-99654 · 14 productsOut of support scope

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Published
2026-11-20
Last modified
2026-11-22
NVD status
Received
GitHub advisory
GHSA-whx2-ppf3-pxvh

Frequently asked questions

What is CVE-2026-99654?

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.

Is CVE-2026-99654 actively exploited?

Active exploitation of CVE-2026-99654 has not been confirmed. Its EPSS score was 0.2% on 2026-11-21, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2026-99654?

CVE-2026-99654 has a CVSS v3 base score of 7.8 (High severity), with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.

Running Linux kernel? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website checks · 250 API requests/month

Sources for this record