CVE-2026-53373

mm/vma: do not try to unmap a VMA if mmap_prepare() invoked from mmap()

Published Jul 19, 2026 CVSS 3.1 · 7.8 High EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

The flaw occurs when the Linux kernel attempts to unmap a virtual memory area that has already been detached during an mmap operation, causing a warning in vma_mark_detached(). The unmap logic is incorrect but does not provide a direct code‑execution or denial of service path; it merely results in an unnecessary warning and potential instability in the memory management subsystem.

Affected Systems

All Linux kernel releases that include the mm/vma subsystem are potentially affected. The advisory does not list specific kernel release numbers, so affected versions are unknown. Distribution maintainers should verify whether their kernel contains the patch that corrects the unmap logic before determining impact.

Risk and Exploitability

The CVSS score of 7.8 indicates high severity. The EPSS score of < 1% shows a very low likelihood of exploitation. The vulnerability is not in CISA’s KEV catalog. An attacker would need local or privileged access that can trigger the faulty mmap path, such as through a driver that invokes mmap_prepare().

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the kernel to a version that includes the patch for CVE-2026-53373.
  • If a patched kernel is not yet available, monitor kernel logs for "vma_mark_detached" warnings and plan for scheduled maintenance to mitigate potential instability.
  • Disable or update stacked drivers (e.g., overlayfs, shm) that invoke mmap_prepare() from their mmap hooks, preventing them from executing when the fault may be triggered.
  • Maintain a regular patch cadence and verify kernel integrity to ensure memory management functions remain secure.

Generated by OpenCVE AI on August 12, 2026 at 09:33 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Ubuntu USN Ubuntu USN USN-8593-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8603-1 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-8618-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8663-1 Linux kernel (NVIDIA) vulnerabilities
Ubuntu USN Ubuntu USN USN-8664-1 Linux kernel (NVIDIA BaseOS) vulnerabilities
Ubuntu USN Ubuntu USN USN-8728-1 Linux kernel (GCP) vulnerabilities
Ubuntu USN Ubuntu USN USN-8728-2 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-8728-3 Linux kernel (Oracle) vulnerabilities
History
Type Values Removed Values Added
Metrics cvssV3_1

{'score': 7.8, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}

Type Values Removed Values Added
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.
Title mm/vma: do not try to unmap a VMA if mmap_prepare() invoked from mmap()
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
Aug 5, 2026, 12:35 PM
Reserved
Jun 9, 2026, 7:44 AM
Status
Analyzed
Published
Jul 19, 2026, 11:16 AM
Modified
Jul 29, 2026, 4:55 PM
Severity
Moderate
Public date
Jul 19, 2026, 12:00 AM