GHSA-VFRX-CQ74-4PR7
Vulnerability from github – Published: 2026-07-19 12:30 – Updated: 2026-07-20 15:31In the Linux kernel, the following vulnerability has been resolved:
mm/vma: do not try to unmap a VMA if mmap_prepare() invoked from mmap()
The mmap_prepare hook functionality includes the ability to invoke mmap_prepare() from the mmap() hook of existing 'stacked' drivers, that is ones which are capable of calling the mmap hooks of other drivers/file systems (e.g. overlayfs, shm).
As part of the mmap_prepare action functionality, we deal with errors by unmapping the VMA should one arise. This works in the usual mmap_prepare case, as we invoke this action at the last moment, when the VMA is established in the maple tree.
However, the mmap() hook passes a not-fully-established VMA pointer to the caller (which is the motivation behind the mmap_prepare() work), which is detached.
So attempting to unmap a VMA in this state will be problematic, with the most obvious symptom being a warning in vma_mark_detached(), because the VMA is already detached.
It's also unncessary - the mmap() handler will clean up the VMA on error.
So to fix this issue, this patch propagates whether or not an mmap action is being completed via the compatibility layer or directly.
If the former, then we do not attempt VMA cleanup, if the latter, then we do.
This patch also updates the userland VMA tests to reflect the change.
{
"affected": [],
"aliases": [
"CVE-2026-53373"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-07-19T11:16:38Z",
"severity": "HIGH"
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nmm/vma: do not try to unmap a VMA if mmap_prepare() invoked from mmap()\n\nThe mmap_prepare hook functionality includes the ability to invoke\nmmap_prepare() from the mmap() hook of existing \u0027stacked\u0027 drivers, that is\nones which are capable of calling the mmap hooks of other drivers/file\nsystems (e.g. overlayfs, shm).\n\nAs part of the mmap_prepare action functionality, we deal with errors by\nunmapping the VMA should one arise. This works in the usual mmap_prepare\ncase, as we invoke this action at the last moment, when the VMA is\nestablished in the maple tree.\n\nHowever, the mmap() hook passes a not-fully-established VMA pointer to the\ncaller (which is the motivation behind the mmap_prepare() work), which is\ndetached.\n\nSo attempting to unmap a VMA in this state will be problematic, with the\nmost obvious symptom being a warning in vma_mark_detached(), because the\nVMA is already detached.\n\nIt\u0027s also unncessary - the mmap() handler will clean up the VMA on error.\n\nSo to fix this issue, this patch propagates whether or not an mmap action\nis being completed via the compatibility layer or directly.\n\nIf the former, then we do not attempt VMA cleanup, if the latter, then we\ndo.\n\nThis patch also updates the userland VMA tests to reflect the change.",
"id": "GHSA-vfrx-cq74-4pr7",
"modified": "2026-07-20T15:31:43Z",
"published": "2026-07-19T12:30:21Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-53373"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/5394bcb746503f2ae4b206212416dccea78e3773"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/619eab23e1ce7c97e54bfc5a417306d94b3f6f13"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
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.