<?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, 16 Oct 2026 07:46:36 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-46066 — ceph: fix num_ops off-by-one when crypto allocation fails</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-46066</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 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;&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 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/cve-2026-46066</guid>
    </item>
    <item>
      <title>USN-8488-1 — linux, linux-aws, linux-gcp, linux-ibm, linux-oracle, linux-realtime vulnerabilities</title>
      <link>https://cve.radiocsirt.org/vuln/usn-8488-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:26.04:LTS: linux, Ubuntu:26.04:LTS: linux-aws, Ubuntu:26.04:LTS: linux-gcp, Ubuntu:26.04:LTS: linux-ibm, Ubuntu:26.04:LTS: linux-oracle, Ubuntu:26.04:LTS: linux-realtime&lt;/p&gt;
&lt;p&gt;It was discovered that some AMD processors did not properly clear data in
the floating point divider unit during speculative execution. A local
attacker could use this to expose sensitive information. (CVE-2025-54505)&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - ARM64 architecture;
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Rados block device (RBD) driver;
  - Compressed RAM block device driver;
  - Character device driver;
  - TPM device driver;
  - Hardware crypto device drivers;
  - EDAC drivers;
  - GPU drivers;
  - Greybus drivers;
  - HID subsystem;
  - Microsoft Hyper-V drivers;
  - Hardware monitoring drivers;
  - I2C subsystem;
  - IIO subsystem;
  - InfiniBand drivers;
  - Input Device core drivers;
  - LED subsystem;
  - Multiple devices driver;
  - Media drivers;
  - IBM Advanced System Management driver;
  - MTD block device drivers;
  - Network drivers;
  - Microsoft Azure Network Adapter (MANA) driver;
  - NTB driver;
  - NVME drivers;
  - Device tree and open firmware driver;
  - PCI subsystem;
  - Remote Processor subsystem;
  - SCSI subsystem;
  - SPI subsystem;
  - Realtek RTL8723BS SDIO drivers;
  - SM750 framebuffer staging driver;
  - Thermal drivers;
  - USB Gadget drivers;
  - USB over IP driver;
  - VFIO drivers;
  - Framebuffer layer;
  - 9P distributed file system;
  - AFS file…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:26.04:LTS: linux, Ubuntu:26.04:LTS: linux-aws, Ubuntu:26.04:LTS: linux-gcp, Ubuntu:26.04:LTS: linux-ibm, Ubuntu:26.04:LTS: linux-oracle, Ubuntu:26.04:LTS: linux-realtime&lt;/p&gt;
&lt;p&gt;It was discovered that some AMD processors did not properly clear data in
the floating point divider unit during speculative execution. A local
attacker could use this to expose sensitive information. (CVE-2025-54505)&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - ARM64 architecture;
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Rados block device (RBD) driver;
  - Compressed RAM block device driver;
  - Character device driver;
  - TPM device driver;
  - Hardware crypto device drivers;
  - EDAC drivers;
  - GPU drivers;
  - Greybus drivers;
  - HID subsystem;
  - Microsoft Hyper-V drivers;
  - Hardware monitoring drivers;
  - I2C subsystem;
  - IIO subsystem;
  - InfiniBand drivers;
  - Input Device core drivers;
  - LED subsystem;
  - Multiple devices driver;
  - Media drivers;
  - IBM Advanced System Management driver;
  - MTD block device drivers;
  - Network drivers;
  - Microsoft Azure Network Adapter (MANA) driver;
  - NTB driver;
  - NVME drivers;
  - Device tree and open firmware driver;
  - PCI subsystem;
  - Remote Processor subsystem;
  - SCSI subsystem;
  - SPI subsystem;
  - Realtek RTL8723BS SDIO drivers;
  - SM750 framebuffer staging driver;
  - Thermal drivers;
  - USB Gadget drivers;
  - USB over IP driver;
  - VFIO drivers;
  - Framebuffer layer;
  - 9P distributed file system;
  - AFS file…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/usn-8488-1</guid>
    </item>
  </channel>
</rss>
