https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 13:00:11 +0000 https://cve.radiocsirt.org/vuln/bdu:2026-15238 bdu:2026-15238 https://cve.radiocsirt.org/vuln/bdu:2026-15238 https://cve.radiocsirt.org/vuln/bell-cve-2023-53618 <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:stream: linux-lts</p> <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:stream: linux-lts</p> https://cve.radiocsirt.org/vuln/bell-cve-2023-53618 https://cve.radiocsirt.org/vuln/certfr-2025-avi-1009 certfr-2025-avi-1009 https://cve.radiocsirt.org/vuln/certfr-2025-avi-1009 https://cve.radiocsirt.org/vuln/euvd-2026-320498 EUVD-2026-320498 https://cve.radiocsirt.org/vuln/euvd-2026-320498 https://cve.radiocsirt.org/vuln/fkie_cve-2023-53618 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>btrfs: reject invalid reloc tree root keys with stack dump</p> <p>[BUG] Syzbot reported a crash that an ASSERT() got triggered inside prepare_to_merge().</p> <p>That ASSERT() makes sure the reloc tree is properly pointed back by its subvolume tree.</p> <p>[CAUSE] After more debugging output, it turns out we had an invalid reloc tree:</p> <p>BTRFS error (device loop1): reloc tree mismatch, root 8 has no reloc root, expect reloc root key (-8, 132, 8) gen 17</p> <p>Note the above root key is (TREE_RELOC_OBJECTID, ROOT_ITEM, QUOTA_TREE_OBJECTID), meaning it&#39;s a reloc tree for quota tree.</p> <p>But reloc trees can only exist for subvolumes, as for non-subvolume trees, we just COW the involved tree block, no need to create a reloc tree since those tree blocks won&#39;t be shared with other trees.</p> <p>Only subvolumes tree can share tree blocks with other trees (thus they have BTRFS_ROOT_SHAREABLE flag).</p> <p>Thus this new debug output proves my previous assumption that corrupted on-disk data can trigger that ASSERT().</p> <p>[FIX] Besides the dedicated fix and the graceful exit, also let tree-checker to check such root keys, to make sure reloc trees can only exist for subvolumes.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>btrfs: reject invalid reloc tree root keys with stack dump</p> <p>[BUG] Syzbot reported a crash that an ASSERT() got triggered inside prepare_to_merge().</p> <p>That ASSERT() makes sure the reloc tree is properly pointed back by its subvolume tree.</p> <p>[CAUSE] After more debugging output, it turns out we had an invalid reloc tree:</p> <p>BTRFS error (device loop1): reloc tree mismatch, root 8 has no reloc root, expect reloc root key (-8, 132, 8) gen 17</p> <p>Note the above root key is (TREE_RELOC_OBJECTID, ROOT_ITEM, QUOTA_TREE_OBJECTID), meaning it&#39;s a reloc tree for quota tree.</p> <p>But reloc trees can only exist for subvolumes, as for non-subvolume trees, we just COW the involved tree block, no need to create a reloc tree since those tree blocks won&#39;t be shared with other trees.</p> <p>Only subvolumes tree can share tree blocks with other trees (thus they have BTRFS_ROOT_SHAREABLE flag).</p> <p>Thus this new debug output proves my previous assumption that corrupted on-disk data can trigger that ASSERT().</p> <p>[FIX] Besides the dedicated fix and the graceful exit, also let tree-checker to check such root keys, to make sure reloc trees can only exist for subvolumes.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2023-53618 https://cve.radiocsirt.org/vuln/ghsa-2244-8r8j-955v <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>btrfs: reject invalid reloc tree root keys with stack dump</p> <p>[BUG] Syzbot reported a crash that an ASSERT() got triggered inside prepare_to_merge().</p> <p>That ASSERT() makes sure the reloc tree is properly pointed back by its subvolume tree.</p> <p>[CAUSE] After more debugging output, it turns out we had an invalid reloc tree:</p> <p>BTRFS error (device loop1): reloc tree mismatch, root 8 has no reloc root, expect reloc root key (-8, 132, 8) gen 17</p> <p>Note the above root key is (TREE_RELOC_OBJECTID, ROOT_ITEM, QUOTA_TREE_OBJECTID), meaning it&#39;s a reloc tree for quota tree.</p> <p>But reloc trees can only exist for subvolumes, as for non-subvolume trees, we just COW the involved tree block, no need to create a reloc tree since those tree blocks won&#39;t be shared with other trees.</p> <p>Only subvolumes tree can share tree blocks with other trees (thus they have BTRFS_ROOT_SHAREABLE flag).</p> <p>Thus this new debug output proves my previous assumption that corrupted on-disk data can trigger that ASSERT().</p> <p>[FIX] Besides the dedicated fix and the graceful exit, also let tree-checker to check such root keys, to make sure reloc trees can only exist for subvolumes.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>btrfs: reject invalid reloc tree root keys with stack dump</p> <p>[BUG] Syzbot reported a crash that an ASSERT() got triggered inside prepare_to_merge().</p> <p>That ASSERT() makes sure the reloc tree is properly pointed back by its subvolume tree.</p> <p>[CAUSE] After more debugging output, it turns out we had an invalid reloc tree:</p> <p>BTRFS error (device loop1): reloc tree mismatch, root 8 has no reloc root, expect reloc root key (-8, 132, 8) gen 17</p> <p>Note the above root key is (TREE_RELOC_OBJECTID, ROOT_ITEM, QUOTA_TREE_OBJECTID), meaning it&#39;s a reloc tree for quota tree.</p> <p>But reloc trees can only exist for subvolumes, as for non-subvolume trees, we just COW the involved tree block, no need to create a reloc tree since those tree blocks won&#39;t be shared with other trees.</p> <p>Only subvolumes tree can share tree blocks with other trees (thus they have BTRFS_ROOT_SHAREABLE flag).</p> <p>Thus this new debug output proves my previous assumption that corrupted on-disk data can trigger that ASSERT().</p> <p>[FIX] Besides the dedicated fix and the graceful exit, also let tree-checker to check such root keys, to make sure reloc trees can only exist for subvolumes.</p> https://cve.radiocsirt.org/vuln/ghsa-2244-8r8j-955v https://cve.radiocsirt.org/vuln/suse-su-2025:21040-1 <p>Security update for the Linux Kernel</p> <p>Security update for the Linux Kernel</p> https://cve.radiocsirt.org/vuln/suse-su-2025:21040-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-53618 <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 163 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: btrfs: reject invalid reloc tree root keys with stack dump [BUG] Syzbot reported a crash that an ASSERT() got triggered inside prepare_to_merge(). That ASSERT() makes sure the reloc tree is properly pointed back by its subvolume tree. [CAUSE] After more debugging output, it turns out we had an invalid reloc tree: BTRFS error (device loop1): reloc tree mismatch, root 8 has no reloc root, expect reloc root key (-8, 132, 8) gen 17 Note the above root key is (TREE_RELOC_OBJECTID, ROOT_ITEM, QUOTA_TREE_OBJECTID), meaning it&#39;s a reloc tree for quota tree. But reloc trees can only exist for subvolumes, as for non-subvolume trees, we just COW the involved tree block, no need to create a reloc tree since those tree blocks won&#39;t be shared with other trees. Only subvolumes tree can share tree blocks with other trees (thus they have BTRFS_ROOT_SHAREABLE flag). Thus this new debug output proves my previous assumption that corrupted on-disk data can trigger that ASSERT(). [FIX] Besides the dedicated fix and the graceful exit, also let tree-checker to check such root keys, to make sure reloc trees can only exist for subvolumes.</p> <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 163 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: btrfs: reject invalid reloc tree root keys with stack dump [BUG] Syzbot reported a crash that an ASSERT() got triggered inside prepare_to_merge(). That ASSERT() makes sure the reloc tree is properly pointed back by its subvolume tree. [CAUSE] After more debugging output, it turns out we had an invalid reloc tree: BTRFS error (device loop1): reloc tree mismatch, root 8 has no reloc root, expect reloc root key (-8, 132, 8) gen 17 Note the above root key is (TREE_RELOC_OBJECTID, ROOT_ITEM, QUOTA_TREE_OBJECTID), meaning it&#39;s a reloc tree for quota tree. But reloc trees can only exist for subvolumes, as for non-subvolume trees, we just COW the involved tree block, no need to create a reloc tree since those tree blocks won&#39;t be shared with other trees. Only subvolumes tree can share tree blocks with other trees (thus they have BTRFS_ROOT_SHAREABLE flag). Thus this new debug output proves my previous assumption that corrupted on-disk data can trigger that ASSERT(). [FIX] Besides the dedicated fix and the graceful exit, also let tree-checker to check such root keys, to make sure reloc trees can only exist for subvolumes.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-53618 https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2229 <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und andere nicht näher spezifizierte Angriffe durchzuführen.</p> <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und andere nicht näher spezifizierte Angriffe durchzuführen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2229