https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 03:10:03 +0000 https://cve.radiocsirt.org/vuln/bdu:2026-01524 bdu:2026-01524 https://cve.radiocsirt.org/vuln/bdu:2026-01524 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0587 certfr-2025-avi-0587 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0587 https://cve.radiocsirt.org/vuln/euvd-2026-310992 EUVD-2026-310992 https://cve.radiocsirt.org/vuln/euvd-2026-310992 https://cve.radiocsirt.org/vuln/fkie_cve-2022-50067 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>btrfs: unset reloc control if transaction commit fails in prepare_to_relocate()</p> <p>In btrfs_relocate_block_group(), the rc is allocated. Then btrfs_relocate_block_group() calls</p> <p>relocate_block_group() prepare_to_relocate() set_reloc_control()</p> <p>that assigns rc to the variable fs_info-&gt;reloc_ctl. When prepare_to_relocate() returns, it calls</p> <p>btrfs_commit_transaction() btrfs_start_dirty_block_groups() btrfs_alloc_path() kmem_cache_zalloc()</p> <p>which may fail for example (or other errors could happen). When the failure occurs, btrfs_relocate_block_group() detects the error and frees rc and doesn&#39;t set fs_info-&gt;reloc_ctl to NULL. After that, in btrfs_init_reloc_root(), rc is retrieved from fs_info-&gt;reloc_ctl and then used, which may cause a use-after-free bug.</p> <p>This possible bug can be triggered by calling btrfs_ioctl_balance() before calling btrfs_ioctl_defrag().</p> <p>To fix this possible bug, in prepare_to_relocate(), check if btrfs_commit_transaction() fails. If the failure occurs, unset_reloc_control() is called to set fs_info-&gt;reloc_ctl to NULL.</p> <p>The error log in our fault-injection testing is shown as follows:</p> <p>[ 58.751070] BUG: KASAN: use-after-free in btrfs_init_reloc_root+0x7ca/0x920 [btrfs] ... [ 58.753577] Call Trace: ... [ 58.755800] kasan_report+0x45/0x60 [ 58.756066] btrfs_init_reloc_root+0x7ca/0x920 [btrfs] [ 58.757304] record_root_in_trans+0x792/0xa10 [btrfs]…</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>btrfs: unset reloc control if transaction commit fails in prepare_to_relocate()</p> <p>In btrfs_relocate_block_group(), the rc is allocated. Then btrfs_relocate_block_group() calls</p> <p>relocate_block_group() prepare_to_relocate() set_reloc_control()</p> <p>that assigns rc to the variable fs_info-&gt;reloc_ctl. When prepare_to_relocate() returns, it calls</p> <p>btrfs_commit_transaction() btrfs_start_dirty_block_groups() btrfs_alloc_path() kmem_cache_zalloc()</p> <p>which may fail for example (or other errors could happen). When the failure occurs, btrfs_relocate_block_group() detects the error and frees rc and doesn&#39;t set fs_info-&gt;reloc_ctl to NULL. After that, in btrfs_init_reloc_root(), rc is retrieved from fs_info-&gt;reloc_ctl and then used, which may cause a use-after-free bug.</p> <p>This possible bug can be triggered by calling btrfs_ioctl_balance() before calling btrfs_ioctl_defrag().</p> <p>To fix this possible bug, in prepare_to_relocate(), check if btrfs_commit_transaction() fails. If the failure occurs, unset_reloc_control() is called to set fs_info-&gt;reloc_ctl to NULL.</p> <p>The error log in our fault-injection testing is shown as follows:</p> <p>[ 58.751070] BUG: KASAN: use-after-free in btrfs_init_reloc_root+0x7ca/0x920 [btrfs] ... [ 58.753577] Call Trace: ... [ 58.755800] kasan_report+0x45/0x60 [ 58.756066] btrfs_init_reloc_root+0x7ca/0x920 [btrfs] [ 58.757304] record_root_in_trans+0x792/0xa10 [btrfs]…</p> https://cve.radiocsirt.org/vuln/fkie_cve-2022-50067 https://cve.radiocsirt.org/vuln/ghsa-fp64-r8jf-r586 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>btrfs: unset reloc control if transaction commit fails in prepare_to_relocate()</p> <p>In btrfs_relocate_block_group(), the rc is allocated. Then btrfs_relocate_block_group() calls</p> <p>relocate_block_group() prepare_to_relocate() set_reloc_control()</p> <p>that assigns rc to the variable fs_info-&gt;reloc_ctl. When prepare_to_relocate() returns, it calls</p> <p>btrfs_commit_transaction() btrfs_start_dirty_block_groups() btrfs_alloc_path() kmem_cache_zalloc()</p> <p>which may fail for example (or other errors could happen). When the failure occurs, btrfs_relocate_block_group() detects the error and frees rc and doesn&#39;t set fs_info-&gt;reloc_ctl to NULL. After that, in btrfs_init_reloc_root(), rc is retrieved from fs_info-&gt;reloc_ctl and then used, which may cause a use-after-free bug.</p> <p>This possible bug can be triggered by calling btrfs_ioctl_balance() before calling btrfs_ioctl_defrag().</p> <p>To fix this possible bug, in prepare_to_relocate(), check if btrfs_commit_transaction() fails. If the failure occurs, unset_reloc_control() is called to set fs_info-&gt;reloc_ctl to NULL.</p> <p>The error log in our fault-injection testing is shown as follows:</p> <p>[ 58.751070] BUG: KASAN: use-after-free in btrfs_init_reloc_root+0x7ca/0x920 [btrfs] ... [ 58.753577] Call Trace: ... [ 58.755800] kasan_report+0x45/0x60 [ 58.756066] btrfs_init_reloc_root+0x7ca/0x920 [btrfs] [ 58.757304] record_root_in_trans+0x792/0xa10 [btrfs]…</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>btrfs: unset reloc control if transaction commit fails in prepare_to_relocate()</p> <p>In btrfs_relocate_block_group(), the rc is allocated. Then btrfs_relocate_block_group() calls</p> <p>relocate_block_group() prepare_to_relocate() set_reloc_control()</p> <p>that assigns rc to the variable fs_info-&gt;reloc_ctl. When prepare_to_relocate() returns, it calls</p> <p>btrfs_commit_transaction() btrfs_start_dirty_block_groups() btrfs_alloc_path() kmem_cache_zalloc()</p> <p>which may fail for example (or other errors could happen). When the failure occurs, btrfs_relocate_block_group() detects the error and frees rc and doesn&#39;t set fs_info-&gt;reloc_ctl to NULL. After that, in btrfs_init_reloc_root(), rc is retrieved from fs_info-&gt;reloc_ctl and then used, which may cause a use-after-free bug.</p> <p>This possible bug can be triggered by calling btrfs_ioctl_balance() before calling btrfs_ioctl_defrag().</p> <p>To fix this possible bug, in prepare_to_relocate(), check if btrfs_commit_transaction() fails. If the failure occurs, unset_reloc_control() is called to set fs_info-&gt;reloc_ctl to NULL.</p> <p>The error log in our fault-injection testing is shown as follows:</p> <p>[ 58.751070] BUG: KASAN: use-after-free in btrfs_init_reloc_root+0x7ca/0x920 [btrfs] ... [ 58.753577] Call Trace: ... [ 58.755800] kasan_report+0x45/0x60 [ 58.756066] btrfs_init_reloc_root+0x7ca/0x920 [btrfs] [ 58.757304] record_root_in_trans+0x792/0xa10 [btrfs]…</p> https://cve.radiocsirt.org/vuln/ghsa-fp64-r8jf-r586 https://cve.radiocsirt.org/vuln/suse-su-2025:02264-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:02264-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-50067 <p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 94 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: btrfs: unset reloc control if transaction commit fails in prepare_to_relocate() In btrfs_relocate_block_group(), the rc is allocated. Then btrfs_relocate_block_group() calls relocate_block_group() prepare_to_relocate() set_reloc_control() that assigns rc to the variable fs_info-&gt;reloc_ctl. When prepare_to_relocate() returns, it calls btrfs_commit_transaction() btrfs_start_dirty_block_groups() btrfs_alloc_path() kmem_cache_zalloc() which may fail for example (or other errors could happen). When the failure occurs, btrfs_relocate_block_group() detects the error and frees rc and doesn&#39;t set fs_info-&gt;reloc_ctl to NULL. After that, in btrfs_init_reloc_root(), rc is retrieved from fs_info-&gt;reloc_ctl and then used, which may cause a use-after-free bug. This possible bug can be triggered by calling btrfs_ioctl_balance() before calling btrfs_ioctl_defrag(). To fix this possible bug, in prepare_to_relocate(), check if btrfs_commit_transaction() fails. If the failure occurs, unset_reloc_control() is called to set fs_info-&gt;reloc_ctl to NULL. The error log in our fault-injection testing is shown as follows: [ 58.751070] BUG: KASAN: use-after-free in btrfs_init_reloc_root+0x7ca/0x920 [btrfs] ... [ 58.753577] Call Trace: ... [ 58.755800] kasan_report+0x45/0x60 [ 58.756066] btrfs_init_reloc_root+0x7ca/0x920 [btrfs] [ 58.757304] record_root_in_trans+0x792/0xa10 [btrfs] [ 58.7…</p> <p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 94 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: btrfs: unset reloc control if transaction commit fails in prepare_to_relocate() In btrfs_relocate_block_group(), the rc is allocated. Then btrfs_relocate_block_group() calls relocate_block_group() prepare_to_relocate() set_reloc_control() that assigns rc to the variable fs_info-&gt;reloc_ctl. When prepare_to_relocate() returns, it calls btrfs_commit_transaction() btrfs_start_dirty_block_groups() btrfs_alloc_path() kmem_cache_zalloc() which may fail for example (or other errors could happen). When the failure occurs, btrfs_relocate_block_group() detects the error and frees rc and doesn&#39;t set fs_info-&gt;reloc_ctl to NULL. After that, in btrfs_init_reloc_root(), rc is retrieved from fs_info-&gt;reloc_ctl and then used, which may cause a use-after-free bug. This possible bug can be triggered by calling btrfs_ioctl_balance() before calling btrfs_ioctl_defrag(). To fix this possible bug, in prepare_to_relocate(), check if btrfs_commit_transaction() fails. If the failure occurs, unset_reloc_control() is called to set fs_info-&gt;reloc_ctl to NULL. The error log in our fault-injection testing is shown as follows: [ 58.751070] BUG: KASAN: use-after-free in btrfs_init_reloc_root+0x7ca/0x920 [btrfs] ... [ 58.753577] Call Trace: ... [ 58.755800] kasan_report+0x45/0x60 [ 58.756066] btrfs_init_reloc_root+0x7ca/0x920 [btrfs] [ 58.757304] record_root_in_trans+0x792/0xa10 [btrfs] [ 58.7…</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-50067 https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1350 <p>Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen.</p> <p>Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1350