<?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-09T21:17:12.380711+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-98224</id>
    <title>CVE-2026-98224 — mm/vma: correctly unaccount on mmap_prepare() failure</title>
    <updated>2026-10-09T21:17:13.286072+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: correctly unaccount on mmap_prepare() failure</p>
<p>__mmap_setup() accounts memory for relevant mappings via:</p>
<p>security_vm_enough_memory_mm()
  -&gt; __vm_enough_memory()
    -&gt; vm_acct_memory()</p>
<p>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.</p>
<p>However if call_mmap_prepare() fails, it also jumps there and any accounted
memory is not correctly unaccounted.</p>
<p>Fix this by handling each error separately.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-98224"/>
  </entry>
</feed>
