<?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>Thu, 01 Oct 2026 00:26:58 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-42293 — arm64: mm: Fix lockless walks with static and dynamic page-table folding</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-42293</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;arm64: mm: Fix lockless walks with static and dynamic page-table folding&lt;/p&gt;
&lt;p&gt;Lina reports random oopsen originating from the fast GUP code when
16K pages are used with 4-level page-tables, the fourth level being
folded at runtime due to lack of LPA2.&lt;/p&gt;
&lt;p&gt;In this configuration, the generic implementation of
p4d_offset_lockless() will return a &amp;#39;p4d_t *&amp;#39; corresponding to the
&amp;#39;pgd_t&amp;#39; allocated on the stack of the caller, gup_fast_pgd_range().
This is normally fine, but when the fourth level of page-table is folded
at runtime, pud_offset_lockless() will offset from the address of the
&amp;#39;p4d_t&amp;#39; to calculate the address of the PUD in the same page-table page.
This results in a stray stack read when the &amp;#39;p4d_t&amp;#39; has been allocated
on the stack and can send the walker into the weeds.&lt;/p&gt;
&lt;p&gt;Fix the problem by providing our own definition of p4d_offset_lockless()
when CONFIG_PGTABLE_LEVELS &amp;lt;= 4 which returns the real page-table
pointer rather than the address of the local stack variable.&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;arm64: mm: Fix lockless walks with static and dynamic page-table folding&lt;/p&gt;
&lt;p&gt;Lina reports random oopsen originating from the fast GUP code when
16K pages are used with 4-level page-tables, the fourth level being
folded at runtime due to lack of LPA2.&lt;/p&gt;
&lt;p&gt;In this configuration, the generic implementation of
p4d_offset_lockless() will return a &amp;#39;p4d_t *&amp;#39; corresponding to the
&amp;#39;pgd_t&amp;#39; allocated on the stack of the caller, gup_fast_pgd_range().
This is normally fine, but when the fourth level of page-table is folded
at runtime, pud_offset_lockless() will offset from the address of the
&amp;#39;p4d_t&amp;#39; to calculate the address of the PUD in the same page-table page.
This results in a stray stack read when the &amp;#39;p4d_t&amp;#39; has been allocated
on the stack and can send the walker into the weeds.&lt;/p&gt;
&lt;p&gt;Fix the problem by providing our own definition of p4d_offset_lockless()
when CONFIG_PGTABLE_LEVELS &amp;lt;= 4 which returns the real page-table
pointer rather than the address of the local stack variable.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-42293</guid>
    </item>
  </channel>
</rss>
