<?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-09-29T01:59:57.013511+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-97533</id>
    <title>CVE-2026-97533 — x86/mm/pat: Acquire init_mm read lock on attribute changes to avoid UAF</title>
    <updated>2026-09-29T01:59:57.017391+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>x86/mm/pat: Acquire init_mm read lock on attribute changes to avoid UAF</p>
<p>A previous commit protected against races between ptdump and CPA collapse,
however one still exists between attribute changes and collapse as reported
by Denis V. Lunev (linked).</p>
<p>When an attribute change arises, a lockless page table walker obtains a PTE
entry, which is later written to via set_pte_atomic():</p>
<p>...
  -&gt; change_page_attr_set_clr()
  -&gt; __change_page_attr_set_clr()
  -&gt; __change_page_attr()
	-&gt; _lookup_address_cpa()
	-&gt; lookup_address_in_pgd_attr()
	-&gt; [ lockless page table walker ]
  -&gt; set_pte_atomic()</p>
<p>There is nothing preventing a concurrent CPA collapse which can free the
PTE that was retrieved here, resulting in a use-after-free.</p>
<p>With the mmap write lock taken on init_mm over CPA collapse, resolve this
race by acquiring an mmap read lock on init_mm over
__change_page_attr_set_clr().</p>
<p>This locks across the whole operation over which the walk and the PTE
entry write occurs, solving the race.</p>
<p>It is safe to do this here, as no spinlocks are held upon entry to
__change_page_attr_set_clr().</p>
<p>However, the lock must not be held over an allocation, as allocation can
trigger reclaim and shrinkers may call into CPA recursively, making
deadlocks possible (init_mm -&gt; ... -&gt; fs_reclaim -&gt; init_mm).</p>
<p>A page table is allocated when a huge page needs to be split:</p>
<p>-&gt; change_page_attr_set_clr()
  -&gt; __change_page_attr_set_clr()…</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-97533"/>
  </entry>
</feed>
