<?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>Fri, 02 Oct 2026 15:27:42 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-46066</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-46066</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-46066</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0831 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-0831</link>
      <description>certfr-2026-avi-0831</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0831</guid>
    </item>
    <item>
      <title>EUVD-2026-327108</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-327108</link>
      <description>EUVD-2026-327108</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-327108</guid>
    </item>
    <item>
      <title>fkie_cve-2026-46066</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-46066</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ceph: fix num_ops off-by-one when crypto allocation fails&lt;/p&gt;
&lt;p&gt;move_dirty_folio_in_page_array() may fail if the file is encrypted, the
dirty folio is not the first in the batch, and it fails to allocate a
bounce buffer to hold the ciphertext. When that happens,
ceph_process_folio_batch() simply redirties the folio and flushes the
current batch -- it can retry that folio in a future batch.&lt;/p&gt;
&lt;p&gt;However, if this failed folio is not contiguous with the last folio that
did make it into the batch, then ceph_process_folio_batch() has already
incremented `ceph_wbc-&amp;gt;num_ops`; because it doesn&amp;#39;t follow through and
add the discontiguous folio to the array, ceph_submit_write() -- which
expects that `ceph_wbc-&amp;gt;num_ops` accurately reflects the number of
contiguous ranges (and therefore the required number of &amp;#34;write extent&amp;#34;
ops) in the writeback -- will panic the kernel:&lt;/p&gt;
&lt;p&gt;BUG_ON(ceph_wbc-&amp;gt;op_idx + 1 != req-&amp;gt;r_num_ops);&lt;/p&gt;
&lt;p&gt;This issue can be reproduced on affected kernels by writing to
fscrypt-enabled CephFS file(s) with a 4KiB-written/4KiB-skipped/repeat
pattern (total filesize should not matter) and gradually increasing the
system&amp;#39;s memory pressure until a bounce buffer allocation fails.&lt;/p&gt;
&lt;p&gt;Fix this crash by decrementing `ceph_wbc-&amp;gt;num_ops` back to the correct
value when move_dirty_folio_in_page_array() fails, but the folio already
started counting a new (i.e. still-empty) extent.&lt;/p&gt;
&lt;p&gt;The defect corrected by this patch has existed…&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: fix num_ops off-by-one when crypto allocation fails&lt;/p&gt;
&lt;p&gt;move_dirty_folio_in_page_array() may fail if the file is encrypted, the
dirty folio is not the first in the batch, and it fails to allocate a
bounce buffer to hold the ciphertext. When that happens,
ceph_process_folio_batch() simply redirties the folio and flushes the
current batch -- it can retry that folio in a future batch.&lt;/p&gt;
&lt;p&gt;However, if this failed folio is not contiguous with the last folio that
did make it into the batch, then ceph_process_folio_batch() has already
incremented `ceph_wbc-&amp;gt;num_ops`; because it doesn&amp;#39;t follow through and
add the discontiguous folio to the array, ceph_submit_write() -- which
expects that `ceph_wbc-&amp;gt;num_ops` accurately reflects the number of
contiguous ranges (and therefore the required number of &amp;#34;write extent&amp;#34;
ops) in the writeback -- will panic the kernel:&lt;/p&gt;
&lt;p&gt;BUG_ON(ceph_wbc-&amp;gt;op_idx + 1 != req-&amp;gt;r_num_ops);&lt;/p&gt;
&lt;p&gt;This issue can be reproduced on affected kernels by writing to
fscrypt-enabled CephFS file(s) with a 4KiB-written/4KiB-skipped/repeat
pattern (total filesize should not matter) and gradually increasing the
system&amp;#39;s memory pressure until a bounce buffer allocation fails.&lt;/p&gt;
&lt;p&gt;Fix this crash by decrementing `ceph_wbc-&amp;gt;num_ops` back to the correct
value when move_dirty_folio_in_page_array() fails, but the folio already
started counting a new (i.e. still-empty) extent.&lt;/p&gt;
&lt;p&gt;The defect corrected by this patch has existed…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-46066</guid>
    </item>
    <item>
      <title>GHSA-2hfr-22wv-h4vj</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-2hfr-22wv-h4vj</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ceph: fix num_ops off-by-one when crypto allocation fails&lt;/p&gt;
&lt;p&gt;move_dirty_folio_in_page_array() may fail if the file is encrypted, the
dirty folio is not the first in the batch, and it fails to allocate a
bounce buffer to hold the ciphertext. When that happens,
ceph_process_folio_batch() simply redirties the folio and flushes the
current batch -- it can retry that folio in a future batch.&lt;/p&gt;
&lt;p&gt;However, if this failed folio is not contiguous with the last folio that
did make it into the batch, then ceph_process_folio_batch() has already
incremented `ceph_wbc-&amp;gt;num_ops`; because it doesn&amp;#39;t follow through and
add the discontiguous folio to the array, ceph_submit_write() -- which
expects that `ceph_wbc-&amp;gt;num_ops` accurately reflects the number of
contiguous ranges (and therefore the required number of &amp;#34;write extent&amp;#34;
ops) in the writeback -- will panic the kernel:&lt;/p&gt;
&lt;p&gt;BUG_ON(ceph_wbc-&amp;gt;op_idx + 1 != req-&amp;gt;r_num_ops);&lt;/p&gt;
&lt;p&gt;This issue can be reproduced on affected kernels by writing to
fscrypt-enabled CephFS file(s) with a 4KiB-written/4KiB-skipped/repeat
pattern (total filesize should not matter) and gradually increasing the
system&amp;#39;s memory pressure until a bounce buffer allocation fails.&lt;/p&gt;
&lt;p&gt;Fix this crash by decrementing `ceph_wbc-&amp;gt;num_ops` back to the correct
value when move_dirty_folio_in_page_array() fails, but the folio already
started counting a new (i.e. still-empty) extent.&lt;/p&gt;
&lt;p&gt;The defect corrected by this patch has existed…&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: fix num_ops off-by-one when crypto allocation fails&lt;/p&gt;
&lt;p&gt;move_dirty_folio_in_page_array() may fail if the file is encrypted, the
dirty folio is not the first in the batch, and it fails to allocate a
bounce buffer to hold the ciphertext. When that happens,
ceph_process_folio_batch() simply redirties the folio and flushes the
current batch -- it can retry that folio in a future batch.&lt;/p&gt;
&lt;p&gt;However, if this failed folio is not contiguous with the last folio that
did make it into the batch, then ceph_process_folio_batch() has already
incremented `ceph_wbc-&amp;gt;num_ops`; because it doesn&amp;#39;t follow through and
add the discontiguous folio to the array, ceph_submit_write() -- which
expects that `ceph_wbc-&amp;gt;num_ops` accurately reflects the number of
contiguous ranges (and therefore the required number of &amp;#34;write extent&amp;#34;
ops) in the writeback -- will panic the kernel:&lt;/p&gt;
&lt;p&gt;BUG_ON(ceph_wbc-&amp;gt;op_idx + 1 != req-&amp;gt;r_num_ops);&lt;/p&gt;
&lt;p&gt;This issue can be reproduced on affected kernels by writing to
fscrypt-enabled CephFS file(s) with a 4KiB-written/4KiB-skipped/repeat
pattern (total filesize should not matter) and gradually increasing the
system&amp;#39;s memory pressure until a bounce buffer allocation fails.&lt;/p&gt;
&lt;p&gt;Fix this crash by decrementing `ceph_wbc-&amp;gt;num_ops` back to the correct
value when move_dirty_folio_in_page_array() fails, but the folio already
started counting a new (i.e. still-empty) extent.&lt;/p&gt;
&lt;p&gt;The defect corrected by this patch has existed…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-2hfr-22wv-h4vj</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-46066 — ceph: fix num_ops off-by-one when crypto allocation fails</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-46066</link>
      <description>msrc_CVE-2026-46066</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-46066</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:10954-1 — kernel-devel-7.0.11-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:10954-1</link>
      <description>&lt;p&gt;kernel-devel-7.0.11-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel-devel-7.0.11-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2026:10954-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-46066</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-46066</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 154 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ceph: fix num_ops off-by-one when crypto allocation fails move_dirty_folio_in_page_array() may fail if the file is encrypted, the dirty folio is not the first in the batch, and it fails to allocate a bounce buffer to hold the ciphertext. When that happens, ceph_process_folio_batch() simply redirties the folio and flushes the current batch -- it can retry that folio in a future batch. However, if this failed folio is not contiguous with the last folio that did make it into the batch, then ceph_process_folio_batch() has already incremented `ceph_wbc-&amp;gt;num_ops`; because it doesn&amp;#39;t follow through and add the discontiguous folio to the array, ceph_submit_write() -- which expects that `ceph_wbc-&amp;gt;num_ops` accurately reflects the number of contiguous ranges (and therefore the required number of &amp;#34;write extent&amp;#34; ops) in the writeback -- will panic the kernel:     BUG_ON(ceph_wbc-&amp;gt;op_idx + 1 != req-&amp;gt;r_num_ops); This issue can be reproduced on affected kernels by writing to fscrypt-enabled CephFS file(s) with a 4KiB-written/4KiB-skipped/repeat pattern (total filesize should not matter) and gradually increasing the system&amp;#39;s memory pressure until a bounce buffer allocation fails. Fix this crash by decrementing `ceph_wbc-&amp;gt;num_ops` back to the correct value when move_dirty_folio_in_page_array() fails, but the folio already started counting a new (i.e. still-empty) extent. The defect corrected by this patch has existed since 2…&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 154 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ceph: fix num_ops off-by-one when crypto allocation fails move_dirty_folio_in_page_array() may fail if the file is encrypted, the dirty folio is not the first in the batch, and it fails to allocate a bounce buffer to hold the ciphertext. When that happens, ceph_process_folio_batch() simply redirties the folio and flushes the current batch -- it can retry that folio in a future batch. However, if this failed folio is not contiguous with the last folio that did make it into the batch, then ceph_process_folio_batch() has already incremented `ceph_wbc-&amp;gt;num_ops`; because it doesn&amp;#39;t follow through and add the discontiguous folio to the array, ceph_submit_write() -- which expects that `ceph_wbc-&amp;gt;num_ops` accurately reflects the number of contiguous ranges (and therefore the required number of &amp;#34;write extent&amp;#34; ops) in the writeback -- will panic the kernel:     BUG_ON(ceph_wbc-&amp;gt;op_idx + 1 != req-&amp;gt;r_num_ops); This issue can be reproduced on affected kernels by writing to fscrypt-enabled CephFS file(s) with a 4KiB-written/4KiB-skipped/repeat pattern (total filesize should not matter) and gradually increasing the system&amp;#39;s memory pressure until a bounce buffer allocation fails. Fix this crash by decrementing `ceph_wbc-&amp;gt;num_ops` back to the correct value when move_dirty_folio_in_page_array() fails, but the folio already started counting a new (i.e. still-empty) extent. The defect corrected by this patch has existed since 2…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-46066</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-1700 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1700</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere nicht näher spezifizierte 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 andere nicht näher spezifizierte Auswirkungen zu erzielen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1700</guid>
    </item>
  </channel>
</rss>
