<?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>Sun, 04 Oct 2026 17:51:33 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-37818 — LoongArch: Return NULL from huge_pte_offset() for invalid PMD</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-37818</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;LoongArch: Return NULL from huge_pte_offset() for invalid PMD&lt;/p&gt;
&lt;p&gt;LoongArch&amp;#39;s huge_pte_offset() currently returns a pointer to a PMD slot
even if the underlying entry points to invalid_pte_table (indicating no
mapping). Callers like smaps_hugetlb_range() fetch this invalid entry
value (the address of invalid_pte_table) via this pointer.&lt;/p&gt;
&lt;p&gt;The generic is_swap_pte() check then incorrectly identifies this address
as a swap entry on LoongArch, because it satisfies the &amp;#34;!pte_present()
&amp;amp;&amp;amp; !pte_none()&amp;#34; conditions. This misinterpretation, combined with a
coincidental match by is_migration_entry() on the address bits, leads to
kernel crashes in pfn_swap_entry_to_page().&lt;/p&gt;
&lt;p&gt;Fix this at the architecture level by modifying huge_pte_offset() to
check the PMD entry&amp;#39;s content using pmd_none() before returning. If the
entry is invalid (i.e., it points to invalid_pte_table), return NULL
instead of the pointer to the slot.&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;LoongArch: Return NULL from huge_pte_offset() for invalid PMD&lt;/p&gt;
&lt;p&gt;LoongArch&amp;#39;s huge_pte_offset() currently returns a pointer to a PMD slot
even if the underlying entry points to invalid_pte_table (indicating no
mapping). Callers like smaps_hugetlb_range() fetch this invalid entry
value (the address of invalid_pte_table) via this pointer.&lt;/p&gt;
&lt;p&gt;The generic is_swap_pte() check then incorrectly identifies this address
as a swap entry on LoongArch, because it satisfies the &amp;#34;!pte_present()
&amp;amp;&amp;amp; !pte_none()&amp;#34; conditions. This misinterpretation, combined with a
coincidental match by is_migration_entry() on the address bits, leads to
kernel crashes in pfn_swap_entry_to_page().&lt;/p&gt;
&lt;p&gt;Fix this at the architecture level by modifying huge_pte_offset() to
check the PMD entry&amp;#39;s content using pmd_none() before returning. If the
entry is invalid (i.e., it points to invalid_pte_table), return NULL
instead of the pointer to the slot.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-37818</guid>
    </item>
  </channel>
</rss>
