<?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-01T19:38:42.681943+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-74354</id>
    <title>CVE-2026-74354 — bpf: Take mmap_lock in zap_pages()</title>
    <updated>2026-10-01T19:38:42.697104+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>bpf: Take mmap_lock in zap_pages()</p>
<p>zap_vma_range() requires the owning mm's mmap_lock to be held.</p>
<p>Taking mmap_read_lock under arena-&gt;lock would AB-BA against
arena_vm_close() and arena_map_mmap(), both of which run with
mmap_write_lock held and then acquire arena-&gt;lock. Instead drop
arena-&gt;lock, mmget_not_zero() the vma's mm, take mmap_read_lock, and
re-resolve the vma via find_vma() since it may have been unmapped or
replaced while waiting.</p>
<p>Track processed vmls with a per-call generation in vml-&gt;zap_gen and
serialize zap_pages() callers with a new arena-&gt;zap_mutex so
concurrent callers on different uaddr ranges do not mark each other's
vmls processed before the zap is done.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-74354"/>
  </entry>
</feed>
