<?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, 09 Oct 2026 20:19:55 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-64232 — block: recompute nr_integrity_segments in blk_insert_cloned_request</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-64232</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;block: recompute nr_integrity_segments in blk_insert_cloned_request&lt;/p&gt;
&lt;p&gt;blk_insert_cloned_request() already recomputes nr_phys_segments
against the bottom queue, because &amp;#34;the queue settings related to
segment counting may differ from the original queue.&amp;#34; The exact same
reasoning applies to integrity segments: a stacked driver&amp;#39;s underlying
queue can have tighter virt_boundary_mask, seg_boundary_mask, or
max_segment_size than the top queue, in which case
blk_rq_count_integrity_sg() against the bottom queue produces a
different count than the cached rq-&amp;gt;nr_integrity_segments inherited
from the source request by blk_rq_prep_clone().&lt;/p&gt;
&lt;p&gt;When the cached count is lower than the bottom queue&amp;#39;s actual count,
blk_rq_map_integrity_sg() trips&lt;/p&gt;
&lt;p&gt;BUG_ON(segments &amp;gt; rq-&amp;gt;nr_integrity_segments);&lt;/p&gt;
&lt;p&gt;on dispatch. The same families of stacked setups that motivated the
existing nr_phys_segments recompute -- dm-multipath fanning out to
nvme-rdma in particular -- can produce this.&lt;/p&gt;
&lt;p&gt;Mirror the nr_phys_segments handling: when the request carries
integrity, recompute nr_integrity_segments against the bottom queue
and reject the request if it exceeds the bottom queue&amp;#39;s
max_integrity_segments. blk_rq_count_integrity_sg() and
queue_max_integrity_segments() are both already available via
&amp;lt;linux/blk-integrity.h&amp;gt;, which blk-mq.c includes.&lt;/p&gt;
&lt;p&gt;This closes a latent gap in the stacking contract and brings the
integrity-segment accounting in line with t…&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;block: recompute nr_integrity_segments in blk_insert_cloned_request&lt;/p&gt;
&lt;p&gt;blk_insert_cloned_request() already recomputes nr_phys_segments
against the bottom queue, because &amp;#34;the queue settings related to
segment counting may differ from the original queue.&amp;#34; The exact same
reasoning applies to integrity segments: a stacked driver&amp;#39;s underlying
queue can have tighter virt_boundary_mask, seg_boundary_mask, or
max_segment_size than the top queue, in which case
blk_rq_count_integrity_sg() against the bottom queue produces a
different count than the cached rq-&amp;gt;nr_integrity_segments inherited
from the source request by blk_rq_prep_clone().&lt;/p&gt;
&lt;p&gt;When the cached count is lower than the bottom queue&amp;#39;s actual count,
blk_rq_map_integrity_sg() trips&lt;/p&gt;
&lt;p&gt;BUG_ON(segments &amp;gt; rq-&amp;gt;nr_integrity_segments);&lt;/p&gt;
&lt;p&gt;on dispatch. The same families of stacked setups that motivated the
existing nr_phys_segments recompute -- dm-multipath fanning out to
nvme-rdma in particular -- can produce this.&lt;/p&gt;
&lt;p&gt;Mirror the nr_phys_segments handling: when the request carries
integrity, recompute nr_integrity_segments against the bottom queue
and reject the request if it exceeds the bottom queue&amp;#39;s
max_integrity_segments. blk_rq_count_integrity_sg() and
queue_max_integrity_segments() are both already available via
&amp;lt;linux/blk-integrity.h&amp;gt;, which blk-mq.c includes.&lt;/p&gt;
&lt;p&gt;This closes a latent gap in the stacking contract and brings the
integrity-segment accounting in line with t…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-64232</guid>
    </item>
    <item>
      <title>USN-8618-1 — linux-aws, linux-raspi vulnerabilities</title>
      <link>https://cve.radiocsirt.org/vuln/usn-8618-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:26.04:LTS: linux-aws, Ubuntu:26.04:LTS: linux-raspi&lt;/p&gt;
&lt;p&gt;It was discovered that some AMD Zen 2 processors did not properly isolate
shared resources in the operation cache. A local attacker could possibly
use this issue to corrupt instructions executed at a higher privilege
level, resulting in privilege escalation. (CVE-2025-54518)&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:
  - x86 platform drivers;
  - Cryptographic API;
  - PSP security protocol;
  - ARM32 architecture;
  - ARM64 architecture;
  - MIPS architecture;
  - PowerPC architecture;
  - RISC-V architecture;
  - S390 architecture;
  - User-Mode Linux (UML);
  - x86 architecture;
  - Block layer subsystem;
  - Intel NPU Driver;
  - Compute Acceleration Framework;
  - ACPI drivers;
  - Auxiliary display drivers;
  - Drivers core;
  - DRBD Distributed Replicated Block Device drivers;
  - Rados block device (RBD) driver;
  - Ublk userspace block driver;
  - Compressed RAM block device driver;
  - Bluetooth drivers;
  - Bus devices;
  - Character device driver;
  - Clock framework and drivers;
  - CPU frequency scaling framework;
  - Hardware crypto device drivers;
  - Buffer Sharing and Synchronization framework;
  - DPLL subsystem;
  - EDAC drivers;
  - Arm Firmware Framework for ARMv8-A(FFA);
  - EFI core;
  - FWCTL subsystem;
  - GPIO subsystem;
  - GPU drivers;
  - HID subsystem;
  - Hardware monitoring drivers;
  - I2C subsystem;
  - I…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:26.04:LTS: linux-aws, Ubuntu:26.04:LTS: linux-raspi&lt;/p&gt;
&lt;p&gt;It was discovered that some AMD Zen 2 processors did not properly isolate
shared resources in the operation cache. A local attacker could possibly
use this issue to corrupt instructions executed at a higher privilege
level, resulting in privilege escalation. (CVE-2025-54518)&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:
  - x86 platform drivers;
  - Cryptographic API;
  - PSP security protocol;
  - ARM32 architecture;
  - ARM64 architecture;
  - MIPS architecture;
  - PowerPC architecture;
  - RISC-V architecture;
  - S390 architecture;
  - User-Mode Linux (UML);
  - x86 architecture;
  - Block layer subsystem;
  - Intel NPU Driver;
  - Compute Acceleration Framework;
  - ACPI drivers;
  - Auxiliary display drivers;
  - Drivers core;
  - DRBD Distributed Replicated Block Device drivers;
  - Rados block device (RBD) driver;
  - Ublk userspace block driver;
  - Compressed RAM block device driver;
  - Bluetooth drivers;
  - Bus devices;
  - Character device driver;
  - Clock framework and drivers;
  - CPU frequency scaling framework;
  - Hardware crypto device drivers;
  - Buffer Sharing and Synchronization framework;
  - DPLL subsystem;
  - EDAC drivers;
  - Arm Firmware Framework for ARMv8-A(FFA);
  - EFI core;
  - FWCTL subsystem;
  - GPIO subsystem;
  - GPU drivers;
  - HID subsystem;
  - Hardware monitoring drivers;
  - I2C subsystem;
  - I…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/usn-8618-1</guid>
    </item>
  </channel>
</rss>
