<?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>Wed, 30 Sep 2026 14:19:22 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-57942 — netfs: Fix ceph copy to cache on write-begin</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-57942</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;netfs: Fix ceph copy to cache on write-begin&lt;/p&gt;
&lt;p&gt;At the end of netfs_unlock_read_folio() in which folios are marked
appropriately for copying to the cache (either with by being marked dirty
and having their private data set or by having PG_private_2 set) and then
unlocked, the folio_queue struct has the entry pointing to the folio
cleared.  This presents a problem for netfs_pgpriv2_write_to_the_cache(),
which is used to write folios marked with PG_private_2 to the cache as it
expects to be able to trawl the folio_queue list thereafter to find the
relevant folios, leading to a hang.&lt;/p&gt;
&lt;p&gt;Fix this by not clearing the folio_queue entry if we&amp;#39;re going to do the
deprecated copy-to-cache.  The clearance will be done instead as the folios
are written to the cache.&lt;/p&gt;
&lt;p&gt;This can be reproduced by starting cachefiles, mounting a ceph filesystem
with &amp;#34;-o fsc&amp;#34; and writing to it.&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;netfs: Fix ceph copy to cache on write-begin&lt;/p&gt;
&lt;p&gt;At the end of netfs_unlock_read_folio() in which folios are marked
appropriately for copying to the cache (either with by being marked dirty
and having their private data set or by having PG_private_2 set) and then
unlocked, the folio_queue struct has the entry pointing to the folio
cleared.  This presents a problem for netfs_pgpriv2_write_to_the_cache(),
which is used to write folios marked with PG_private_2 to the cache as it
expects to be able to trawl the folio_queue list thereafter to find the
relevant folios, leading to a hang.&lt;/p&gt;
&lt;p&gt;Fix this by not clearing the folio_queue entry if we&amp;#39;re going to do the
deprecated copy-to-cache.  The clearance will be done instead as the folios
are written to the cache.&lt;/p&gt;
&lt;p&gt;This can be reproduced by starting cachefiles, mounting a ceph filesystem
with &amp;#34;-o fsc&amp;#34; and writing to it.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-57942</guid>
    </item>
  </channel>
</rss>
