<?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>Sun, 18 Oct 2026 03:41:29 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-43338 — btrfs: reserve enough transaction items for qgroup ioctls</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-43338</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;btrfs: reserve enough transaction items for qgroup ioctls&lt;/p&gt;
&lt;p&gt;Currently our qgroup ioctls don&amp;#39;t reserve any space, they just do a
transaction join, which does not reserve any space, neither for the quota
tree updates nor for the delayed refs generated when updating the quota
tree. The quota root uses the global block reserve, which is fine most of
the time since we don&amp;#39;t expect a lot of updates to the quota root, or to
be too close to -ENOSPC such that other critical metadata updates need to
resort to the global reserve.&lt;/p&gt;
&lt;p&gt;However this is not optimal, as not reserving proper space may result in a
transaction abort due to not reserving space for delayed refs and then
abusing the use of the global block reserve.&lt;/p&gt;
&lt;p&gt;For example, the following reproducer (which is unlikely to model any
real world use case, but just to illustrate the problem), triggers such a
transaction abort due to -ENOSPC when running delayed refs:&lt;/p&gt;
&lt;p&gt;$ cat test.sh
  #!/bin/bash&lt;/p&gt;
&lt;p&gt;DEV=/dev/nullb0
  MNT=/mnt/nullb0&lt;/p&gt;
&lt;p&gt;umount $DEV &amp;amp;&amp;gt; /dev/null
  # Limit device to 1G so that it&amp;#39;s much faster to reproduce the issue.
  mkfs.btrfs -f -b 1G $DEV
  mount -o commit=600 $DEV $MNT&lt;/p&gt;
&lt;p&gt;fallocate -l 800M $MNT/filler
  btrfs quota enable $MNT&lt;/p&gt;
&lt;p&gt;for ((i = 1; i &amp;lt;= 400000; i++)); do
      btrfs qgroup create 1/$i $MNT
  done&lt;/p&gt;
&lt;p&gt;umount $MNT&lt;/p&gt;
&lt;p&gt;When running this, we can see in dmesg/syslog that a transaction abort
happened:&lt;/p&gt;
&lt;p&gt;[436.490] BTRFS error (device nullb0): fa…&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;btrfs: reserve enough transaction items for qgroup ioctls&lt;/p&gt;
&lt;p&gt;Currently our qgroup ioctls don&amp;#39;t reserve any space, they just do a
transaction join, which does not reserve any space, neither for the quota
tree updates nor for the delayed refs generated when updating the quota
tree. The quota root uses the global block reserve, which is fine most of
the time since we don&amp;#39;t expect a lot of updates to the quota root, or to
be too close to -ENOSPC such that other critical metadata updates need to
resort to the global reserve.&lt;/p&gt;
&lt;p&gt;However this is not optimal, as not reserving proper space may result in a
transaction abort due to not reserving space for delayed refs and then
abusing the use of the global block reserve.&lt;/p&gt;
&lt;p&gt;For example, the following reproducer (which is unlikely to model any
real world use case, but just to illustrate the problem), triggers such a
transaction abort due to -ENOSPC when running delayed refs:&lt;/p&gt;
&lt;p&gt;$ cat test.sh
  #!/bin/bash&lt;/p&gt;
&lt;p&gt;DEV=/dev/nullb0
  MNT=/mnt/nullb0&lt;/p&gt;
&lt;p&gt;umount $DEV &amp;amp;&amp;gt; /dev/null
  # Limit device to 1G so that it&amp;#39;s much faster to reproduce the issue.
  mkfs.btrfs -f -b 1G $DEV
  mount -o commit=600 $DEV $MNT&lt;/p&gt;
&lt;p&gt;fallocate -l 800M $MNT/filler
  btrfs quota enable $MNT&lt;/p&gt;
&lt;p&gt;for ((i = 1; i &amp;lt;= 400000; i++)); do
      btrfs qgroup create 1/$i $MNT
  done&lt;/p&gt;
&lt;p&gt;umount $MNT&lt;/p&gt;
&lt;p&gt;When running this, we can see in dmesg/syslog that a transaction abort
happened:&lt;/p&gt;
&lt;p&gt;[436.490] BTRFS error (device nullb0): fa…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-43338</guid>
    </item>
    <item>
      <title>USN-8567-1 — linux, linux-gcp, linux-gcp-6.8, linux-gke, linux-gkeop, linux-realtime, linux-realtime-6.8 vulnerabilities</title>
      <link>https://cve.radiocsirt.org/vuln/usn-8567-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:22.04:LTS: linux-gcp-6.8, Ubuntu:Pro:Realtime:22.04:LTS: linux-realtime-6.8, Ubuntu:24.04:LTS: linux, Ubuntu:24.04:LTS: linux-gcp, Ubuntu:24.04:LTS: linux-gke, Ubuntu:24.04:LTS: linux-gkeop, Ubuntu:Pro:Realtime:24.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;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;It was discovered that some AMD Zen 5 processors supporting RDSEED
instruction did not properly handle entropy, potentially resulting in the
consumption of insufficiently random values. A local attacker could
possibly use this issue to influence the values returned by the RDSEED
instruction causing loss of confidentiality and integrity. (CVE-2025-62626)&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;
  - RISC-V architecture;
  - S390 architecture;
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Compute Acceleration Framework;
  - ACPI drivers;
  - Serial ATA and Parallel ATA drivers;
  - Drivers core;
  - Power management core;
  - DRBD Distributed Replicated Block Device drivers;
  - Rados block device (RBD) driver;
  - Compressed RAM block device driver;
  - Bluetooth drivers;
  - Bus devices;
  - Charact…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:22.04:LTS: linux-gcp-6.8, Ubuntu:Pro:Realtime:22.04:LTS: linux-realtime-6.8, Ubuntu:24.04:LTS: linux, Ubuntu:24.04:LTS: linux-gcp, Ubuntu:24.04:LTS: linux-gke, Ubuntu:24.04:LTS: linux-gkeop, Ubuntu:Pro:Realtime:24.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;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;It was discovered that some AMD Zen 5 processors supporting RDSEED
instruction did not properly handle entropy, potentially resulting in the
consumption of insufficiently random values. A local attacker could
possibly use this issue to influence the values returned by the RDSEED
instruction causing loss of confidentiality and integrity. (CVE-2025-62626)&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;
  - RISC-V architecture;
  - S390 architecture;
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Compute Acceleration Framework;
  - ACPI drivers;
  - Serial ATA and Parallel ATA drivers;
  - Drivers core;
  - Power management core;
  - DRBD Distributed Replicated Block Device drivers;
  - Rados block device (RBD) driver;
  - Compressed RAM block device driver;
  - Bluetooth drivers;
  - Bus devices;
  - Charact…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/usn-8567-1</guid>
    </item>
  </channel>
</rss>
