<?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:00 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-99732 — mm/filemap: read mapping-&gt;a_ops-&gt;free_folio under i_lock</title>
      <link>https://db.gcve.eu/vuln/cve-2026-99732</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: read mapping-&amp;gt;a_ops-&amp;gt;free_folio under i_lock&lt;/p&gt;
&lt;p&gt;memory_failure() -&amp;gt; ... -&amp;gt; filemap_remove_folio() can read mapping-&amp;gt;a_ops
after the inode has been freed. Once the folio is deleted from the
pagecache it no longer pins the mapping, so after i_lock is dropped
e.g., a concurrent final iput() can evict and free the inode before
filemap_free_folio() looks up mapping-&amp;gt;a_ops-&amp;gt;free_folio.&lt;/p&gt;
&lt;p&gt;Most callers hold a reference on the inode, but not all.&lt;/p&gt;
&lt;p&gt;Documentation/filesystems/vfs.rst explicitly states that -&amp;gt;free_folio()
must not assume the original address_space mapping still exists.&lt;/p&gt;
&lt;p&gt;Fix it by loading -&amp;gt;free_folio while i_lock is still held, similar to
what folio_unmap_invalidate() does.&lt;/p&gt;
&lt;p&gt;Inline filemap_free_folio() into its remaining caller such that
delete_from_page_cache_batch() also just loads the callback before
dropping the i_lock.&lt;/p&gt;
&lt;p&gt;The bug was found by code inspection and has not been reproduced.&lt;/p&gt;
&lt;p&gt;Fix generated by an LLM and sent by Josef Bacik in private.&lt;/p&gt;
&lt;p&gt;[ david: get rid of filemap_free_folio() entirely; improve patch 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/filemap: read mapping-&amp;gt;a_ops-&amp;gt;free_folio under i_lock&lt;/p&gt;
&lt;p&gt;memory_failure() -&amp;gt; ... -&amp;gt; filemap_remove_folio() can read mapping-&amp;gt;a_ops
after the inode has been freed. Once the folio is deleted from the
pagecache it no longer pins the mapping, so after i_lock is dropped
e.g., a concurrent final iput() can evict and free the inode before
filemap_free_folio() looks up mapping-&amp;gt;a_ops-&amp;gt;free_folio.&lt;/p&gt;
&lt;p&gt;Most callers hold a reference on the inode, but not all.&lt;/p&gt;
&lt;p&gt;Documentation/filesystems/vfs.rst explicitly states that -&amp;gt;free_folio()
must not assume the original address_space mapping still exists.&lt;/p&gt;
&lt;p&gt;Fix it by loading -&amp;gt;free_folio while i_lock is still held, similar to
what folio_unmap_invalidate() does.&lt;/p&gt;
&lt;p&gt;Inline filemap_free_folio() into its remaining caller such that
delete_from_page_cache_batch() also just loads the callback before
dropping the i_lock.&lt;/p&gt;
&lt;p&gt;The bug was found by code inspection and has not been reproduced.&lt;/p&gt;
&lt;p&gt;Fix generated by an LLM and sent by Josef Bacik in private.&lt;/p&gt;
&lt;p&gt;[ david: get rid of filemap_free_folio() entirely; improve patch description ]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-99732</guid>
    </item>
  </channel>
</rss>
