GHSA-MPJF-V662-XM2M
Vulnerability from github – Published: 2026-10-06 09:31 – Updated: 2026-10-06 09:31In the Linux kernel, the following vulnerability has been resolved:
mm/vma: correctly unaccount on mmap_prepare() failure
__mmap_setup() accounts memory for relevant mappings via:
security_vm_enough_memory_mm() -> __vm_enough_memory() -> vm_acct_memory()
If __mmap_setup() fails, this indicates that this accounting did not take place, and thus it's appropriate for __mmap_region() to jump to abort_munmap.
However if call_mmap_prepare() fails, it also jumps there and any accounted memory is not correctly unaccounted.
Fix this by handling each error separately.
{
"affected": [],
"aliases": [
"CVE-2026-98224"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-10-06T09:18:09Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nmm/vma: correctly unaccount on mmap_prepare() failure\n\n__mmap_setup() accounts memory for relevant mappings via:\n\nsecurity_vm_enough_memory_mm()\n -\u003e __vm_enough_memory()\n -\u003e vm_acct_memory()\n\nIf __mmap_setup() fails, this indicates that this accounting did not take\nplace, and thus it\u0027s appropriate for __mmap_region() to jump to\nabort_munmap.\n\nHowever if call_mmap_prepare() fails, it also jumps there and any accounted\nmemory is not correctly unaccounted.\n\nFix this by handling each error separately.",
"id": "GHSA-mpjf-v662-xm2m",
"modified": "2026-10-06T09:31:31Z",
"published": "2026-10-06T09:31:31Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-98224"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/6cc27d82196385fe06853319f74312a7d8019726"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/8fdc521d438fbf0d22c13d51d55d5dd82d7202b2"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/fb5400bff669c8bad3d4ec09287d9b461e89e5f1"
}
],
"schema_version": "1.4.0",
"severity": []
}
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
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.