<?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>Thu, 15 Oct 2026 11:41:58 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-26792 — btrfs: fix double free of anonymous device after snapshot creation failure</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2024-26792</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: fix double free of anonymous device after snapshot creation failure&lt;/p&gt;
&lt;p&gt;When creating a snapshot we may do a double free of an anonymous device
in case there&amp;#39;s an error committing the transaction. The second free may
result in freeing an anonymous device number that was allocated by some
other subsystem in the kernel or another btrfs filesystem.&lt;/p&gt;
&lt;p&gt;The steps that lead to this:&lt;/p&gt;
&lt;p&gt;1) At ioctl.c:create_snapshot() we allocate an anonymous device number
   and assign it to pending_snapshot-&amp;gt;anon_dev;&lt;/p&gt;
&lt;p&gt;2) Then we call btrfs_commit_transaction() and end up at
   transaction.c:create_pending_snapshot();&lt;/p&gt;
&lt;p&gt;3) There we call btrfs_get_new_fs_root() and pass it the anonymous device
   number stored in pending_snapshot-&amp;gt;anon_dev;&lt;/p&gt;
&lt;p&gt;4) btrfs_get_new_fs_root() frees that anonymous device number because
   btrfs_lookup_fs_root() returned a root - someone else did a lookup
   of the new root already, which could some task doing backref walking;&lt;/p&gt;
&lt;p&gt;5) After that some error happens in the transaction commit path, and at
   ioctl.c:create_snapshot() we jump to the &amp;#39;fail&amp;#39; label, and after
   that we free again the same anonymous device number, which in the
   meanwhile may have been reallocated somewhere else, because
   pending_snapshot-&amp;gt;anon_dev still has the same value as in step 1.&lt;/p&gt;
&lt;p&gt;Recently syzbot ran into this and reported the following trace:&lt;/p&gt;
&lt;p&gt;------------[ cut here ]------------
  ida_free called for id=51 which is not a…&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: fix double free of anonymous device after snapshot creation failure&lt;/p&gt;
&lt;p&gt;When creating a snapshot we may do a double free of an anonymous device
in case there&amp;#39;s an error committing the transaction. The second free may
result in freeing an anonymous device number that was allocated by some
other subsystem in the kernel or another btrfs filesystem.&lt;/p&gt;
&lt;p&gt;The steps that lead to this:&lt;/p&gt;
&lt;p&gt;1) At ioctl.c:create_snapshot() we allocate an anonymous device number
   and assign it to pending_snapshot-&amp;gt;anon_dev;&lt;/p&gt;
&lt;p&gt;2) Then we call btrfs_commit_transaction() and end up at
   transaction.c:create_pending_snapshot();&lt;/p&gt;
&lt;p&gt;3) There we call btrfs_get_new_fs_root() and pass it the anonymous device
   number stored in pending_snapshot-&amp;gt;anon_dev;&lt;/p&gt;
&lt;p&gt;4) btrfs_get_new_fs_root() frees that anonymous device number because
   btrfs_lookup_fs_root() returned a root - someone else did a lookup
   of the new root already, which could some task doing backref walking;&lt;/p&gt;
&lt;p&gt;5) After that some error happens in the transaction commit path, and at
   ioctl.c:create_snapshot() we jump to the &amp;#39;fail&amp;#39; label, and after
   that we free again the same anonymous device number, which in the
   meanwhile may have been reallocated somewhere else, because
   pending_snapshot-&amp;gt;anon_dev still has the same value as in step 1.&lt;/p&gt;
&lt;p&gt;Recently syzbot ran into this and reported the following trace:&lt;/p&gt;
&lt;p&gt;------------[ cut here ]------------
  ida_free called for id=51 which is not a…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2024-26792</guid>
    </item>
    <item>
      <title>USN-6820-1 — linux, linux-gcp, linux-gcp-5.15, linux-lowlatency, linux-lowlatency-hwe-5.15, linux-xilinx-zynqmp vulnerabilities</title>
      <link>https://cve.radiocsirt.org/vuln/usn-6820-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:20.04:LTS: linux-gcp-5.15, Ubuntu:20.04:LTS: linux-lowlatency-hwe-5.15, Ubuntu:22.04:LTS: linux, Ubuntu:22.04:LTS: linux-gcp, Ubuntu:22.04:LTS: linux-lowlatency, Ubuntu:22.04:LTS: linux-xilinx-zynqmp&lt;/p&gt;
&lt;p&gt;It was discovered that the ATA over Ethernet (AoE) driver in the Linux
kernel contained a race condition, leading to a use-after-free
vulnerability. An attacker could use this to cause a denial of service or
possibly execute arbitrary code. (CVE-2023-6270)&lt;/p&gt;
&lt;p&gt;It was discovered that the Atheros 802.11ac wireless driver did not
properly validate certain data structures, leading to a NULL pointer
dereference. An attacker could possibly use this to cause a denial of
service. (CVE-2023-7042)&lt;/p&gt;
&lt;p&gt;It was discovered that the HugeTLB file system component of the Linux
Kernel contained a NULL pointer dereference vulnerability. A privileged
attacker could possibly use this to to cause a denial of service.
(CVE-2024-0841)&lt;/p&gt;
&lt;p&gt;It was discovered that the Intel Data Streaming and Intel Analytics
Accelerator drivers in the Linux kernel allowed direct access to the
devices for unprivileged users and virtual machines. A local attacker could
use this to cause a denial of service. (CVE-2024-21823)&lt;/p&gt;
&lt;p&gt;Yuxuan Hu discovered that the Bluetooth RFCOMM protocol driver in the Linux
Kernel contained a race condition, leading to a NULL pointer dereference.
An attacker could possibly use this to cause a denial of service (system
crash). (CVE-2024-22099)&lt;/p&gt;
&lt;p&gt;It was discovered that the MediaTek SoC Gigabit Ethernet driver in the
Linux kernel contained a race condition when stopping the device. A local
attacker could possibly use this to cause a denial of service (device
unavailability). (CVE-2024-27432)&lt;/p&gt;
&lt;p&gt;Several securi…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:20.04:LTS: linux-gcp-5.15, Ubuntu:20.04:LTS: linux-lowlatency-hwe-5.15, Ubuntu:22.04:LTS: linux, Ubuntu:22.04:LTS: linux-gcp, Ubuntu:22.04:LTS: linux-lowlatency, Ubuntu:22.04:LTS: linux-xilinx-zynqmp&lt;/p&gt;
&lt;p&gt;It was discovered that the ATA over Ethernet (AoE) driver in the Linux
kernel contained a race condition, leading to a use-after-free
vulnerability. An attacker could use this to cause a denial of service or
possibly execute arbitrary code. (CVE-2023-6270)&lt;/p&gt;
&lt;p&gt;It was discovered that the Atheros 802.11ac wireless driver did not
properly validate certain data structures, leading to a NULL pointer
dereference. An attacker could possibly use this to cause a denial of
service. (CVE-2023-7042)&lt;/p&gt;
&lt;p&gt;It was discovered that the HugeTLB file system component of the Linux
Kernel contained a NULL pointer dereference vulnerability. A privileged
attacker could possibly use this to to cause a denial of service.
(CVE-2024-0841)&lt;/p&gt;
&lt;p&gt;It was discovered that the Intel Data Streaming and Intel Analytics
Accelerator drivers in the Linux kernel allowed direct access to the
devices for unprivileged users and virtual machines. A local attacker could
use this to cause a denial of service. (CVE-2024-21823)&lt;/p&gt;
&lt;p&gt;Yuxuan Hu discovered that the Bluetooth RFCOMM protocol driver in the Linux
Kernel contained a race condition, leading to a NULL pointer dereference.
An attacker could possibly use this to cause a denial of service (system
crash). (CVE-2024-22099)&lt;/p&gt;
&lt;p&gt;It was discovered that the MediaTek SoC Gigabit Ethernet driver in the
Linux kernel contained a race condition when stopping the device. A local
attacker could possibly use this to cause a denial of service (device
unavailability). (CVE-2024-27432)&lt;/p&gt;
&lt;p&gt;Several securi…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/usn-6820-1</guid>
    </item>
  </channel>
</rss>
