<?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>Mon, 28 Sep 2026 20:20:38 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-39878 — ceph: fix crash after fscrypt_encrypt_pagecache_blocks() error</title>
      <link>https://db.gcve.eu/vuln/cve-2025-39878</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;ceph: fix crash after fscrypt_encrypt_pagecache_blocks() error&lt;/p&gt;
&lt;p&gt;The function move_dirty_folio_in_page_array() was created by commit
ce80b76dd327 (&amp;#34;ceph: introduce ceph_process_folio_batch() method&amp;#34;) by
moving code from ceph_writepages_start() to this function.&lt;/p&gt;
&lt;p&gt;This new function is supposed to return an error code which is checked
by the caller (now ceph_process_folio_batch()), and on error, the
caller invokes redirty_page_for_writepage() and then breaks from the
loop.&lt;/p&gt;
&lt;p&gt;However, the refactoring commit has gone wrong, and it by accident, it
always returns 0 (= success) because it first NULLs the pointer and
then returns PTR_ERR(NULL) which is always 0.  This means errors are
silently ignored, leaving NULL entries in the page array, which may
later crash the kernel.&lt;/p&gt;
&lt;p&gt;The simple solution is to call PTR_ERR() before clearing the pointer.&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;ceph: fix crash after fscrypt_encrypt_pagecache_blocks() error&lt;/p&gt;
&lt;p&gt;The function move_dirty_folio_in_page_array() was created by commit
ce80b76dd327 (&amp;#34;ceph: introduce ceph_process_folio_batch() method&amp;#34;) by
moving code from ceph_writepages_start() to this function.&lt;/p&gt;
&lt;p&gt;This new function is supposed to return an error code which is checked
by the caller (now ceph_process_folio_batch()), and on error, the
caller invokes redirty_page_for_writepage() and then breaks from the
loop.&lt;/p&gt;
&lt;p&gt;However, the refactoring commit has gone wrong, and it by accident, it
always returns 0 (= success) because it first NULLs the pointer and
then returns PTR_ERR(NULL) which is always 0.  This means errors are
silently ignored, leaving NULL entries in the page array, which may
later crash the kernel.&lt;/p&gt;
&lt;p&gt;The simple solution is to call PTR_ERR() before clearing the pointer.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2025-39878</guid>
    </item>
  </channel>
</rss>
