<?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 04:48:52 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-35872 — mm/secretmem: fix GUP-fast succeeding on secretmem folios</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-35872</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/secretmem: fix GUP-fast succeeding on secretmem folios&lt;/p&gt;
&lt;p&gt;folio_is_secretmem() currently relies on secretmem folios being LRU
folios, to save some cycles.&lt;/p&gt;
&lt;p&gt;However, folios might reside in a folio batch without the LRU flag set, or
temporarily have their LRU flag cleared.  Consequently, the LRU flag is
unreliable for this purpose.&lt;/p&gt;
&lt;p&gt;In particular, this is the case when secretmem_fault() allocates a fresh
page and calls filemap_add_folio()-&amp;gt;folio_add_lru().  The folio might be
added to the per-cpu folio batch and won&amp;#39;t get the LRU flag set until the
batch was drained using e.g., lru_add_drain().&lt;/p&gt;
&lt;p&gt;Consequently, folio_is_secretmem() might not detect secretmem folios and
GUP-fast can succeed in grabbing a secretmem folio, crashing the kernel
when we would later try reading/writing to the folio, because the folio
has been unmapped from the directmap.&lt;/p&gt;
&lt;p&gt;Fix it by removing that unreliable check.&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/secretmem: fix GUP-fast succeeding on secretmem folios&lt;/p&gt;
&lt;p&gt;folio_is_secretmem() currently relies on secretmem folios being LRU
folios, to save some cycles.&lt;/p&gt;
&lt;p&gt;However, folios might reside in a folio batch without the LRU flag set, or
temporarily have their LRU flag cleared.  Consequently, the LRU flag is
unreliable for this purpose.&lt;/p&gt;
&lt;p&gt;In particular, this is the case when secretmem_fault() allocates a fresh
page and calls filemap_add_folio()-&amp;gt;folio_add_lru().  The folio might be
added to the per-cpu folio batch and won&amp;#39;t get the LRU flag set until the
batch was drained using e.g., lru_add_drain().&lt;/p&gt;
&lt;p&gt;Consequently, folio_is_secretmem() might not detect secretmem folios and
GUP-fast can succeed in grabbing a secretmem folio, crashing the kernel
when we would later try reading/writing to the folio, because the folio
has been unmapped from the directmap.&lt;/p&gt;
&lt;p&gt;Fix it by removing that unreliable check.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-35872</guid>
    </item>
  </channel>
</rss>
