<?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>Fri, 09 Oct 2026 23:39:47 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-98223 — mm: filemap: retain mapped dropbehind folios</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-98223</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: filemap: retain mapped dropbehind folios&lt;/p&gt;
&lt;p&gt;Fault-around can map ready dropbehind folios without going through the
normal page-cache lookup that clears dropbehind.  A mapping represents a
competing cached user, so retain the folio instead of forcibly unmapping
it when writeback completes.&lt;/p&gt;
&lt;p&gt;For a mapped folio, folio_unmap_invalidate() can call
unmap_mapping_folio(), which takes i_mmap_rwsem and may sleep.  Retaining
mapped folios avoids this path when folio_end_dropbehind() runs in
non-preemptible task context.&lt;/p&gt;
&lt;p&gt;Tal was able to trigger a sleeping-in-atomic warning due to this [1].&lt;/p&gt;
&lt;p&gt;Unmapped dropbehind folios continue through the existing invalidation path.&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: filemap: retain mapped dropbehind folios&lt;/p&gt;
&lt;p&gt;Fault-around can map ready dropbehind folios without going through the
normal page-cache lookup that clears dropbehind.  A mapping represents a
competing cached user, so retain the folio instead of forcibly unmapping
it when writeback completes.&lt;/p&gt;
&lt;p&gt;For a mapped folio, folio_unmap_invalidate() can call
unmap_mapping_folio(), which takes i_mmap_rwsem and may sleep.  Retaining
mapped folios avoids this path when folio_end_dropbehind() runs in
non-preemptible task context.&lt;/p&gt;
&lt;p&gt;Tal was able to trigger a sleeping-in-atomic warning due to this [1].&lt;/p&gt;
&lt;p&gt;Unmapped dropbehind folios continue through the existing invalidation path.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-98223</guid>
    </item>
  </channel>
</rss>
