<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Mon, 05 Oct 2026 11:28:03 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-42233 — filemap: replace pte_offset_map() with pte_offset_map_nolock()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-42233</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;filemap: replace pte_offset_map() with pte_offset_map_nolock()&lt;/p&gt;
&lt;p&gt;The vmf-&amp;gt;ptl in filemap_fault_recheck_pte_none() is still set from
handle_pte_fault().  But at the same time, we did a pte_unmap(vmf-&amp;gt;pte). 
After a pte_unmap(vmf-&amp;gt;pte) unmap and rcu_read_unlock(), the page table
may be racily changed and vmf-&amp;gt;ptl maybe fails to protect the actual page
table.  Fix this by replacing pte_offset_map() with
pte_offset_map_nolock().&lt;/p&gt;
&lt;p&gt;As David said, the PTL pointer might be stale so if we continue to use
it infilemap_fault_recheck_pte_none(), it might trigger UAF.  Also, if
the PTL fails, the issue fixed by commit 58f327f2ce80 (&amp;#34;filemap: avoid
unnecessary major faults in filemap_fault()&amp;#34;) might reappear.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;filemap: replace pte_offset_map() with pte_offset_map_nolock()&lt;/p&gt;
&lt;p&gt;The vmf-&amp;gt;ptl in filemap_fault_recheck_pte_none() is still set from
handle_pte_fault().  But at the same time, we did a pte_unmap(vmf-&amp;gt;pte). 
After a pte_unmap(vmf-&amp;gt;pte) unmap and rcu_read_unlock(), the page table
may be racily changed and vmf-&amp;gt;ptl maybe fails to protect the actual page
table.  Fix this by replacing pte_offset_map() with
pte_offset_map_nolock().&lt;/p&gt;
&lt;p&gt;As David said, the PTL pointer might be stale so if we continue to use
it infilemap_fault_recheck_pte_none(), it might trigger UAF.  Also, if
the PTL fails, the issue fixed by commit 58f327f2ce80 (&amp;#34;filemap: avoid
unnecessary major faults in filemap_fault()&amp;#34;) might reappear.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-42233</guid>
    </item>
  </channel>
</rss>
