<?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:23 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-99669 — mm/huge_memory: fix truncate racing with PMD zapping</title>
      <link>https://db.gcve.eu/vuln/cve-2026-99669</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/huge_memory: fix truncate racing with PMD zapping&lt;/p&gt;
&lt;p&gt;zap_huge_pmd_folio() removes the rmap before calling folio_mark_dirty().
If this was the last mapping, truncation can skip unmapping the folio
and proceed without waiting for the PMD lock, racing with dirtying.&lt;/p&gt;
&lt;p&gt;ifs_set_range_dirty() can oops if MADV_DONTNEED races with
ftruncate() on XFS, when we get the folio set dirty after it was found
to not be mapped anymore.&lt;/p&gt;
&lt;p&gt;Move folio_mark_dirty() and folio_mark_accessed() before rmap removal,
matching the PTE zap path. This keeps the folio mapped while updating
its state, so truncation must wait for the page table lock.&lt;/p&gt;
&lt;p&gt;Fix generated by an LLM and sent by Chris Mason in private.&lt;/p&gt;
&lt;p&gt;[ david: simplify comment and description ]&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/huge_memory: fix truncate racing with PMD zapping&lt;/p&gt;
&lt;p&gt;zap_huge_pmd_folio() removes the rmap before calling folio_mark_dirty().
If this was the last mapping, truncation can skip unmapping the folio
and proceed without waiting for the PMD lock, racing with dirtying.&lt;/p&gt;
&lt;p&gt;ifs_set_range_dirty() can oops if MADV_DONTNEED races with
ftruncate() on XFS, when we get the folio set dirty after it was found
to not be mapped anymore.&lt;/p&gt;
&lt;p&gt;Move folio_mark_dirty() and folio_mark_accessed() before rmap removal,
matching the PTE zap path. This keeps the folio mapped while updating
its state, so truncation must wait for the page table lock.&lt;/p&gt;
&lt;p&gt;Fix generated by an LLM and sent by Chris Mason in private.&lt;/p&gt;
&lt;p&gt;[ david: simplify comment and description ]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-99669</guid>
    </item>
  </channel>
</rss>
