mm/mmu_gather: fix flushing ranges with 4 GiB or larger
Summary
| CVE | CVE-2026-99659 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-11-20 06:17:59 UTC |
| Updated | 2026-11-22 11:17:04 UTC |
| Description | In the Linux kernel, the following vulnerability has been resolved: mm/mmu_gather: fix flushing ranges with 4 GiB or larger __tlb_adjust_range() takes the size of the range which has to be flushed as an unsigned int. Its callers, tlb_flush_{pte,pmd,pud,p4d}_range(), get and pass an unsigned long. Consequently, a range that is 4 GiB or larger gets truncated, possibly to 0. On arm64 with hugetlb, a 64k kernel can have 16 GiB hugetlb folios mapped contiguously at the PMD level and flush them when unmapping, and a 16k kernel can flush 64 GiB PUDs through tlb_unshare_pmd_ptdesc(). So at least these two scenarios are affected. Fix it by flushing the proper range instead of the truncated one by properly using "unsigned long" for range_size. Fix generated by an LLM and sent by Josef Bacik in private. [ david: use two-tab indent, simplify description ] |
Risk And Classification
Primary CVSS: v3.1 7 HIGH from 416baaa9-dc9f-4396-8d5f-8c081fb06d67
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS: 0.001680000 probability, percentile 0.062380000 (date 2026-11-21)
| Version | Source | Type | Score | Severity | Vector |
|---|---|---|---|---|---|
| 3.1 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | Secondary | 7 | HIGH | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H |
| 3.1 | CNA | DECLARED | 7 | HIGH | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H |
CVSS v3.1 Breakdown
Attack Vector
LocalAttack Complexity
HighPrivileges Required
LowUser Interaction
NoneScope
UnchangedConfidentiality
HighIntegrity
HighAvailability
HighCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected b528e4b6405b9fd656a6a308a7e2aa6afa50e77d da895690b531ba3905c69bd2ed1c447dafa7b4ce git | Not specified |
| CNA | Linux | Linux | affected b528e4b6405b9fd656a6a308a7e2aa6afa50e77d 2e12a0d8fa2ea4af9a74f414063359d965784919 git | Not specified |
| CNA | Linux | Linux | affected b528e4b6405b9fd656a6a308a7e2aa6afa50e77d 3647c49f164004458b5e767deed033bc13a25a2d git | Not specified |
| CNA | Linux | Linux | affected b528e4b6405b9fd656a6a308a7e2aa6afa50e77d 64ae7959a1df8af8eec504e31df2ec9670424a4e git | Not specified |
| CNA | Linux | Linux | affected 4.10 | Not specified |
| CNA | Linux | Linux | unaffected 4.10 semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12.118 6.12.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.18.64 6.18.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.3.5 7.3.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.4-rc2 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/64ae7959a1df8af8eec504e31df2ec9670424a4e | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/2e12a0d8fa2ea4af9a74f414063359d965784919 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/da895690b531ba3905c69bd2ed1c447dafa7b4ce | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/3647c49f164004458b5e767deed033bc13a25a2d | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.