CVE-2026-53373
Last modified
CVE-2026-53373 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. In 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. EPSS estimates a 0.11% chance of exploitation in the next 30 days.
Description
In 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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= ac0a3fc9c07df79dc8a4ce9d274df00afc7bf12d, < 5394bcb746503f2ae4b206212416dccea78e3773; >= ac0a3fc9c07df79dc8a4ce9d274df00afc7bf12d, < 619eab23e1ce7c97e54bfc5a417306d94b3f6f13 |
| Linux | Linux | 6.19 |
References
Timeline
- Published
- Last Modified
- Status
- Awaiting Analysis
Frequently Asked Questions
What is CVE-2026-53373?
How severe is CVE-2026-53373?
How do I fix CVE-2026-53373?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-53368In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-53369In the Linux kernel, the following vulnerability has been re…8.4
- CVE-2026-5337During the analysis, it was identified that authenticated at…6.5
- CVE-2026-53370In the Linux kernel, the following vulnerability has been re…
- CVE-2026-53371In the Linux kernel, the following vulnerability has been re…
- CVE-2026-53372In the Linux kernel, the following vulnerability has been re…
- CVE-2026-53374In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-53375In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-53376In the Linux kernel, the following vulnerability has been re…
- CVE-2026-53377In the Linux kernel, the following vulnerability has been re…
- CVE-2026-53378In the Linux kernel, the following vulnerability has been re…
- CVE-2026-53379In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-53373?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
