<?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:21:04 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-99729 — mm/rmap: handle device-exclusive entries in folio_referenced_one()</title>
      <link>https://db.gcve.eu/vuln/cve-2026-99729</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/rmap: handle device-exclusive entries in folio_referenced_one()&lt;/p&gt;
&lt;p&gt;page_vma_mapped_walk() can return non-present device-exclusive entries,
but folio_referenced_one() passes them to PTE young-bit accessors that
require present PTEs.&lt;/p&gt;
&lt;p&gt;We must neither call clear_flush_young_ptes_notify() nor
folio_pte_batch() with non-present entries. For example, clearing the
young bit on non-present PTEs can corrupt the entry: on arm64
PTE_AF overlaps the swap type, so clearing it turns a device-exclusive
entry into an ordinary swap entry.&lt;/p&gt;
&lt;p&gt;folio_pte_batch() will VM_WARN_ON_FOLIO.&lt;/p&gt;
&lt;p&gt;Apply the same approach as the previous fixes to e.g., damon_ptep_mkold():
treat these entries as old from the CPU&amp;#39;s perspective and obtain their
young state through the MMU notifier.&lt;/p&gt;
&lt;p&gt;Skip PTE batching and MGLRU look-around for non-present entries, and
don&amp;#39;t modify non-present PTEs.&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/rmap: handle device-exclusive entries in folio_referenced_one()&lt;/p&gt;
&lt;p&gt;page_vma_mapped_walk() can return non-present device-exclusive entries,
but folio_referenced_one() passes them to PTE young-bit accessors that
require present PTEs.&lt;/p&gt;
&lt;p&gt;We must neither call clear_flush_young_ptes_notify() nor
folio_pte_batch() with non-present entries. For example, clearing the
young bit on non-present PTEs can corrupt the entry: on arm64
PTE_AF overlaps the swap type, so clearing it turns a device-exclusive
entry into an ordinary swap entry.&lt;/p&gt;
&lt;p&gt;folio_pte_batch() will VM_WARN_ON_FOLIO.&lt;/p&gt;
&lt;p&gt;Apply the same approach as the previous fixes to e.g., damon_ptep_mkold():
treat these entries as old from the CPU&amp;#39;s perspective and obtain their
young state through the MMU notifier.&lt;/p&gt;
&lt;p&gt;Skip PTE batching and MGLRU look-around for non-present entries, and
don&amp;#39;t modify non-present PTEs.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-99729</guid>
    </item>
  </channel>
</rss>
