<?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://db.gcve.eu</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>Fri, 20 Nov 2026 21:22:37 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-99664 — mm/gup: recheck the PUD under PTL in follow_pud_mask()</title>
      <link>https://db.gcve.eu/vuln/cve-2026-99664</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/gup: recheck the PUD under PTL in follow_pud_mask()&lt;/p&gt;
&lt;p&gt;follow_pud_mask() reads the PUD without a lock. If it is a leaf, it takes
the lock and calls follow_huge_pud(), which reads the entry again, but
only tests whether it is present.&lt;/p&gt;
&lt;p&gt;A leaf can be zapped concurrently and a page fault can fill the empty
entry with a page table.&lt;/p&gt;
&lt;p&gt;This currently only applies when device-dax makes use of PUD entries,
and the fault after e.g., MADV_DONTNEED would find THPs to be disabled.&lt;/p&gt;
&lt;p&gt;That requires a sequence like&lt;/p&gt;
&lt;p&gt;1) Fault in the PUD
2) Disable THP
3) Have GUP race against concurrent MADV_DONTNEED + refault&lt;/p&gt;
&lt;p&gt;Which is rather unlikely to happen in practice, which is why we never
received a report about such a problem.&lt;/p&gt;
&lt;p&gt;Before commit 1b1676180246 (&amp;#34;mm/gup: handle huge pud for
follow_pud_mask()&amp;#34;), we performed that check in follow_devmap_pud() by
testing for pud_devmap().&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s fix it by just structuring follow_pud_mask() similar to
follow_pmd_mask(), minus protnone stuff that does not apply and minus
FOLL_SPLIT_PMD handling. That makes it much easier to spot any such
inconsistencies.&lt;/p&gt;
&lt;p&gt;Perform the pud_bad() check early in follow_pmd_mask() and just forward
the PUD value. We can drop the pud_present() check in follow_huge_pud(),
just like we have in follow_huge_pmd().&lt;/p&gt;
&lt;p&gt;Even though we are performing more changes than strictly necessary, the
fix should be easy to backport.&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/gup: recheck the PUD under PTL in follow_pud_mask()&lt;/p&gt;
&lt;p&gt;follow_pud_mask() reads the PUD without a lock. If it is a leaf, it takes
the lock and calls follow_huge_pud(), which reads the entry again, but
only tests whether it is present.&lt;/p&gt;
&lt;p&gt;A leaf can be zapped concurrently and a page fault can fill the empty
entry with a page table.&lt;/p&gt;
&lt;p&gt;This currently only applies when device-dax makes use of PUD entries,
and the fault after e.g., MADV_DONTNEED would find THPs to be disabled.&lt;/p&gt;
&lt;p&gt;That requires a sequence like&lt;/p&gt;
&lt;p&gt;1) Fault in the PUD
2) Disable THP
3) Have GUP race against concurrent MADV_DONTNEED + refault&lt;/p&gt;
&lt;p&gt;Which is rather unlikely to happen in practice, which is why we never
received a report about such a problem.&lt;/p&gt;
&lt;p&gt;Before commit 1b1676180246 (&amp;#34;mm/gup: handle huge pud for
follow_pud_mask()&amp;#34;), we performed that check in follow_devmap_pud() by
testing for pud_devmap().&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s fix it by just structuring follow_pud_mask() similar to
follow_pmd_mask(), minus protnone stuff that does not apply and minus
FOLL_SPLIT_PMD handling. That makes it much easier to spot any such
inconsistencies.&lt;/p&gt;
&lt;p&gt;Perform the pud_bad() check early in follow_pmd_mask() and just forward
the PUD value. We can drop the pud_present() check in follow_huge_pud(),
just like we have in follow_huge_pmd().&lt;/p&gt;
&lt;p&gt;Even though we are performing more changes than strictly necessary, the
fix should be easy to backport.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-99664</guid>
    </item>
  </channel>
</rss>
