<?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://cve.radiocsirt.org</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>Sat, 03 Oct 2026 07:11:26 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-13899</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-13899</link>
      <description>bdu:2025-13899</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-13899</guid>
    </item>
    <item>
      <title>BELL-CVE-2025-39879</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2025-39879</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2025-39879</guid>
    </item>
    <item>
      <title>EUVD-2026-314802</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-314802</link>
      <description>EUVD-2026-314802</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-314802</guid>
    </item>
    <item>
      <title>fkie_cve-2025-39879</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-39879</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ceph: always call ceph_shift_unused_folios_left()&lt;/p&gt;
&lt;p&gt;The function ceph_process_folio_batch() sets folio_batch entries to
NULL, which is an illegal state.  Before folio_batch_release() crashes
due to this API violation, the function ceph_shift_unused_folios_left()
is supposed to remove those NULLs from the array.&lt;/p&gt;
&lt;p&gt;However, since commit ce80b76dd327 (&amp;#34;ceph: introduce
ceph_process_folio_batch() method&amp;#34;), this shifting doesn&amp;#39;t happen
anymore because the &amp;#34;for&amp;#34; loop got moved to ceph_process_folio_batch(),
and now the `i` variable that remains in ceph_writepages_start()
doesn&amp;#39;t get incremented anymore, making the shifting effectively
unreachable much of the time.&lt;/p&gt;
&lt;p&gt;Later, commit 1551ec61dc55 (&amp;#34;ceph: introduce ceph_submit_write()
method&amp;#34;) added more preconditions for doing the shift, replacing the
`i` check (with something that is still just as broken):&lt;/p&gt;
&lt;p&gt;- if ceph_process_folio_batch() fails, shifting never happens&lt;/p&gt;
&lt;p&gt;- if ceph_move_dirty_page_in_page_array() was never called (because
  ceph_process_folio_batch() has returned early for some of various
  reasons), shifting never happens&lt;/p&gt;
&lt;p&gt;- if `processed_in_fbatch` is zero (because ceph_process_folio_batch()
  has returned early for some of the reasons mentioned above or
  because ceph_move_dirty_page_in_page_array() has failed), shifting
  never happens&lt;/p&gt;
&lt;p&gt;Since those two commits, any problem in ceph_process_folio_batch()
could crash the kernel, e.g. this way:&lt;/p&gt;
&lt;p&gt;BUG: kern…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ceph: always call ceph_shift_unused_folios_left()&lt;/p&gt;
&lt;p&gt;The function ceph_process_folio_batch() sets folio_batch entries to
NULL, which is an illegal state.  Before folio_batch_release() crashes
due to this API violation, the function ceph_shift_unused_folios_left()
is supposed to remove those NULLs from the array.&lt;/p&gt;
&lt;p&gt;However, since commit ce80b76dd327 (&amp;#34;ceph: introduce
ceph_process_folio_batch() method&amp;#34;), this shifting doesn&amp;#39;t happen
anymore because the &amp;#34;for&amp;#34; loop got moved to ceph_process_folio_batch(),
and now the `i` variable that remains in ceph_writepages_start()
doesn&amp;#39;t get incremented anymore, making the shifting effectively
unreachable much of the time.&lt;/p&gt;
&lt;p&gt;Later, commit 1551ec61dc55 (&amp;#34;ceph: introduce ceph_submit_write()
method&amp;#34;) added more preconditions for doing the shift, replacing the
`i` check (with something that is still just as broken):&lt;/p&gt;
&lt;p&gt;- if ceph_process_folio_batch() fails, shifting never happens&lt;/p&gt;
&lt;p&gt;- if ceph_move_dirty_page_in_page_array() was never called (because
  ceph_process_folio_batch() has returned early for some of various
  reasons), shifting never happens&lt;/p&gt;
&lt;p&gt;- if `processed_in_fbatch` is zero (because ceph_process_folio_batch()
  has returned early for some of the reasons mentioned above or
  because ceph_move_dirty_page_in_page_array() has failed), shifting
  never happens&lt;/p&gt;
&lt;p&gt;Since those two commits, any problem in ceph_process_folio_batch()
could crash the kernel, e.g. this way:&lt;/p&gt;
&lt;p&gt;BUG: kern…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-39879</guid>
    </item>
    <item>
      <title>GHSA-hq23-ggcp-mx5x</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-hq23-ggcp-mx5x</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ceph: always call ceph_shift_unused_folios_left()&lt;/p&gt;
&lt;p&gt;The function ceph_process_folio_batch() sets folio_batch entries to
NULL, which is an illegal state.  Before folio_batch_release() crashes
due to this API violation, the function ceph_shift_unused_folios_left()
is supposed to remove those NULLs from the array.&lt;/p&gt;
&lt;p&gt;However, since commit ce80b76dd327 (&amp;#34;ceph: introduce
ceph_process_folio_batch() method&amp;#34;), this shifting doesn&amp;#39;t happen
anymore because the &amp;#34;for&amp;#34; loop got moved to ceph_process_folio_batch(),
and now the `i` variable that remains in ceph_writepages_start()
doesn&amp;#39;t get incremented anymore, making the shifting effectively
unreachable much of the time.&lt;/p&gt;
&lt;p&gt;Later, commit 1551ec61dc55 (&amp;#34;ceph: introduce ceph_submit_write()
method&amp;#34;) added more preconditions for doing the shift, replacing the
`i` check (with something that is still just as broken):&lt;/p&gt;
&lt;p&gt;- if ceph_process_folio_batch() fails, shifting never happens&lt;/p&gt;
&lt;p&gt;- if ceph_move_dirty_page_in_page_array() was never called (because
  ceph_process_folio_batch() has returned early for some of various
  reasons), shifting never happens&lt;/p&gt;
&lt;p&gt;- if `processed_in_fbatch` is zero (because ceph_process_folio_batch()
  has returned early for some of the reasons mentioned above or
  because ceph_move_dirty_page_in_page_array() has failed), shifting
  never happens&lt;/p&gt;
&lt;p&gt;Since those two commits, any problem in ceph_process_folio_batch()
could crash the kernel, e.g. this way:&lt;/p&gt;
&lt;p&gt;BUG: kern…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ceph: always call ceph_shift_unused_folios_left()&lt;/p&gt;
&lt;p&gt;The function ceph_process_folio_batch() sets folio_batch entries to
NULL, which is an illegal state.  Before folio_batch_release() crashes
due to this API violation, the function ceph_shift_unused_folios_left()
is supposed to remove those NULLs from the array.&lt;/p&gt;
&lt;p&gt;However, since commit ce80b76dd327 (&amp;#34;ceph: introduce
ceph_process_folio_batch() method&amp;#34;), this shifting doesn&amp;#39;t happen
anymore because the &amp;#34;for&amp;#34; loop got moved to ceph_process_folio_batch(),
and now the `i` variable that remains in ceph_writepages_start()
doesn&amp;#39;t get incremented anymore, making the shifting effectively
unreachable much of the time.&lt;/p&gt;
&lt;p&gt;Later, commit 1551ec61dc55 (&amp;#34;ceph: introduce ceph_submit_write()
method&amp;#34;) added more preconditions for doing the shift, replacing the
`i` check (with something that is still just as broken):&lt;/p&gt;
&lt;p&gt;- if ceph_process_folio_batch() fails, shifting never happens&lt;/p&gt;
&lt;p&gt;- if ceph_move_dirty_page_in_page_array() was never called (because
  ceph_process_folio_batch() has returned early for some of various
  reasons), shifting never happens&lt;/p&gt;
&lt;p&gt;- if `processed_in_fbatch` is zero (because ceph_process_folio_batch()
  has returned early for some of the reasons mentioned above or
  because ceph_move_dirty_page_in_page_array() has failed), shifting
  never happens&lt;/p&gt;
&lt;p&gt;Since those two commits, any problem in ceph_process_folio_batch()
could crash the kernel, e.g. this way:&lt;/p&gt;
&lt;p&gt;BUG: kern…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-hq23-ggcp-mx5x</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-39879</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-39879</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 79 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ceph: always call ceph_shift_unused_folios_left() The function ceph_process_folio_batch() sets folio_batch entries to NULL, which is an illegal state.  Before folio_batch_release() crashes due to this API violation, the function ceph_shift_unused_folios_left() is supposed to remove those NULLs from the array. However, since commit ce80b76dd327 (&amp;#34;ceph: introduce ceph_process_folio_batch() method&amp;#34;), this shifting doesn&amp;#39;t happen anymore because the &amp;#34;for&amp;#34; loop got moved to ceph_process_folio_batch(), and now the `i` variable that remains in ceph_writepages_start() doesn&amp;#39;t get incremented anymore, making the shifting effectively unreachable much of the time. Later, commit 1551ec61dc55 (&amp;#34;ceph: introduce ceph_submit_write() method&amp;#34;) added more preconditions for doing the shift, replacing the `i` check (with something that is still just as broken): - if ceph_process_folio_batch() fails, shifting never happens - if ceph_move_dirty_page_in_page_array() was never called (because   ceph_process_folio_batch() has returned early for some of various   reasons), shifting never happens - if `processed_in_fbatch` is zero (because ceph_process_folio_batch()   has returned early for some of the reasons mentioned above or   because ceph_move_dirty_page_in_page_array() has failed), shifting   never happens Since those two commits, any problem in ceph_process_folio_batch() could crash the kernel, e.g. this way:  BUG: kernel NULL p…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 79 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ceph: always call ceph_shift_unused_folios_left() The function ceph_process_folio_batch() sets folio_batch entries to NULL, which is an illegal state.  Before folio_batch_release() crashes due to this API violation, the function ceph_shift_unused_folios_left() is supposed to remove those NULLs from the array. However, since commit ce80b76dd327 (&amp;#34;ceph: introduce ceph_process_folio_batch() method&amp;#34;), this shifting doesn&amp;#39;t happen anymore because the &amp;#34;for&amp;#34; loop got moved to ceph_process_folio_batch(), and now the `i` variable that remains in ceph_writepages_start() doesn&amp;#39;t get incremented anymore, making the shifting effectively unreachable much of the time. Later, commit 1551ec61dc55 (&amp;#34;ceph: introduce ceph_submit_write() method&amp;#34;) added more preconditions for doing the shift, replacing the `i` check (with something that is still just as broken): - if ceph_process_folio_batch() fails, shifting never happens - if ceph_move_dirty_page_in_page_array() was never called (because   ceph_process_folio_batch() has returned early for some of various   reasons), shifting never happens - if `processed_in_fbatch` is zero (because ceph_process_folio_batch()   has returned early for some of the reasons mentioned above or   because ceph_move_dirty_page_in_page_array() has failed), shifting   never happens Since those two commits, any problem in ceph_process_folio_batch() could crash the kernel, e.g. this way:  BUG: kernel NULL p…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-39879</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-2107 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2107</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht näher beschriebene Auswirkungen zu erzielen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht näher beschriebene Auswirkungen zu erzielen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2107</guid>
    </item>
  </channel>
</rss>
