<?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>Wed, 30 Sep 2026 13:31:18 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-40948 — mm/page_table_check: fix crash on ZONE_DEVICE</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-40948</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;mm/page_table_check: fix crash on ZONE_DEVICE&lt;/p&gt;
&lt;p&gt;Not all pages may apply to pgtable check.  One example is ZONE_DEVICE
pages: they map PFNs directly, and they don&amp;#39;t allocate page_ext at all
even if there&amp;#39;s struct page around.  One may reference
devm_memremap_pages().&lt;/p&gt;
&lt;p&gt;When both ZONE_DEVICE and page-table-check enabled, then try to map some
dax memories, one can trigger kernel bug constantly now when the kernel
was trying to inject some pfn maps on the dax device:&lt;/p&gt;
&lt;p&gt;kernel BUG at mm/page_table_check.c:55!&lt;/p&gt;
&lt;p&gt;While it&amp;#39;s pretty legal to use set_pxx_at() for ZONE_DEVICE pages for page
fault resolutions, skip all the checks if page_ext doesn&amp;#39;t even exist in
pgtable checker, which applies to ZONE_DEVICE but maybe more.&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;mm/page_table_check: fix crash on ZONE_DEVICE&lt;/p&gt;
&lt;p&gt;Not all pages may apply to pgtable check.  One example is ZONE_DEVICE
pages: they map PFNs directly, and they don&amp;#39;t allocate page_ext at all
even if there&amp;#39;s struct page around.  One may reference
devm_memremap_pages().&lt;/p&gt;
&lt;p&gt;When both ZONE_DEVICE and page-table-check enabled, then try to map some
dax memories, one can trigger kernel bug constantly now when the kernel
was trying to inject some pfn maps on the dax device:&lt;/p&gt;
&lt;p&gt;kernel BUG at mm/page_table_check.c:55!&lt;/p&gt;
&lt;p&gt;While it&amp;#39;s pretty legal to use set_pxx_at() for ZONE_DEVICE pages for page
fault resolutions, skip all the checks if page_ext doesn&amp;#39;t even exist in
pgtable checker, which applies to ZONE_DEVICE but maybe more.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-40948</guid>
    </item>
  </channel>
</rss>
