FKIE_CVE-2026-99654
Vulnerability from fkie_nvd - Published: 2026-11-20 06:17 - Updated: 2026-11-20 06:17| Vendor | Product | Version |
|---|
{
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"mm/memory.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "cbf6c66a2ef46433092b41b87176755de32bf65b",
"status": "affected",
"version": "9eab0421fa94a3dde0d1f7e36ab3294fc306c99d",
"versionType": "git"
},
{
"lessThan": "0cf8d3fdd869fe079e55f8e621e45397a819d93c",
"status": "affected",
"version": "9eab0421fa94a3dde0d1f7e36ab3294fc306c99d",
"versionType": "git"
},
{
"lessThan": "67e6d5468a7d693a00176713d44267e5360d63c3",
"status": "affected",
"version": "9eab0421fa94a3dde0d1f7e36ab3294fc306c99d",
"versionType": "git"
},
{
"lessThan": "7a81bc23dade8082187be6d9cc36e4be4b7207e2",
"status": "affected",
"version": "9eab0421fa94a3dde0d1f7e36ab3294fc306c99d",
"versionType": "git"
},
{
"status": "affected",
"version": "2db1c46c3913b8bc92fed235a344de2671fe9d8d",
"versionType": "git"
},
{
"status": "affected",
"version": "77359c4973056ba33a5627d5c04aea494eb76bc9",
"versionType": "git"
},
{
"status": "affected",
"version": "73704c6b35c7682fd22f97992a68b0e8451c7a52",
"versionType": "git"
},
{
"status": "affected",
"version": "91432aebce514cab49f63324c98b4eccb80532c5",
"versionType": "git"
},
{
"status": "affected",
"version": "dafdeb7b91f1597983693a418c496b6702ea34b5",
"versionType": "git"
},
{
"status": "affected",
"version": "2247df454c7bb4b13939794fe6fae8510868d241",
"versionType": "git"
},
{
"lessThan": "4.20",
"status": "affected",
"version": "4.19.305",
"versionType": "semver"
},
{
"lessThan": "5.5",
"status": "affected",
"version": "5.4.267",
"versionType": "semver"
},
{
"lessThan": "5.11",
"status": "affected",
"version": "5.10.208",
"versionType": "semver"
},
{
"lessThan": "5.16",
"status": "affected",
"version": "5.15.147",
"versionType": "semver"
},
{
"lessThan": "6.2",
"status": "affected",
"version": "6.1.72",
"versionType": "semver"
},
{
"lessThan": "6.7",
"status": "affected",
"version": "6.6.11",
"versionType": "semver"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"mm/memory.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "6.7"
},
{
"lessThan": "6.7",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"version": "6.12.118",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.64",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.3.*",
"status": "unaffected",
"version": "7.3.5",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.4-rc2",
"versionType": "original_commit_for_fix"
}
]
}
],
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmm: fix unmap_mapping_range() beyond 4 GiB on 32-bit\n\nCommit 9eab0421fa94 (\"mm: fix unmap_mapping_range high bits shift bug\")\nmade holebegin and holelen unsigned before they are shifted, by casting\nthem to pgoff_t. That is an unsigned long: on a 32-bit kernel the cast\ncuts off the upper half of the two loff_t values, so a hole which begins\nat 4 GiB or beyond is taken for one in the first 4 GiB of the file.\n\ntruncate_pagecache() passes the new size of the file and asks for private\nCOWed pages to be unmapped as well. If a file of 6 GiB is truncated to\n5 GiB, everything from 1 GiB on is unmapped, and what a process has\nwritten to a private mapping of the range between 1 GiB and 5 GiB is\nlost: it reads the contents of the file again.\n\nWhere the range has an end, the wrong range is unmapped instead of the\nright one. The page cache copes with that, as it unmaps every folio that\nit removes. The callers which only have unmap_mapping_range() to get\nrid of user mappings do not, for example drm_vma_node_unmap(), whose fake\noffsets reach beyond 4 GiB on 32-bit, and revoke_iomem() with physical\naddresses of more than 32 bits.\n\nCast to u64 instead. Nothing changes for 64-bit kernels.\n\nFix generated by an LLM and sent by Josef Bacik in private."
}
],
"id": "CVE-2026-99654",
"lastModified": "2026-11-20T06:17:59.243",
"metrics": {},
"published": "2026-11-20T06:17:59.243",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/0cf8d3fdd869fe079e55f8e621e45397a819d93c"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/67e6d5468a7d693a00176713d44267e5360d63c3"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/7a81bc23dade8082187be6d9cc36e4be4b7207e2"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/cbf6c66a2ef46433092b41b87176755de32bf65b"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Received"
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.