<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-01T11:03:18.687694+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2026-53373</id>
    <title>CVE-2026-53373 — mm/vma: do not try to unmap a VMA if mmap_prepare() invoked from mmap()</title>
    <updated>2026-10-01T11:03:20.012652+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>mm/vma: do not try to unmap a VMA if mmap_prepare() invoked from mmap()</p>
<p>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).</p>
<p>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.</p>
<p>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.</p>
<p>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.</p>
<p>It's also unncessary - the mmap() handler will clean up the VMA on error.</p>
<p>So to fix this issue, this patch propagates whether or not an mmap action
is being completed via the compatibility layer or directly.</p>
<p>If the former, then we do not attempt VMA cleanup, if the latter, then we
do.</p>
<p>This patch also updates the userland VMA tests to reflect the change.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-53373"/>
  </entry>
</feed>
