https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 05:35:24 +0000 https://cve.radiocsirt.org/vuln/bdu:2024-00728 bdu:2024-00728 https://cve.radiocsirt.org/vuln/bdu:2024-00728 https://cve.radiocsirt.org/vuln/certfr-2024-avi-0242 certfr-2024-avi-0242 https://cve.radiocsirt.org/vuln/certfr-2024-avi-0242 https://cve.radiocsirt.org/vuln/cnvd-2024-06431 cnvd-2024-06431 https://cve.radiocsirt.org/vuln/cnvd-2024-06431 https://cve.radiocsirt.org/vuln/euvd-2026-259401 EUVD-2026-259401 https://cve.radiocsirt.org/vuln/euvd-2026-259401 https://cve.radiocsirt.org/vuln/fkie_cve-2024-23850 <p>In btrfs_get_root_ref in fs/btrfs/disk-io.c in the Linux kernel through 6.7.1, there can be an assertion failure and crash because a subvolume can be read out too soon after its root item is inserted upon subvolume creation.</p> <p>In btrfs_get_root_ref in fs/btrfs/disk-io.c in the Linux kernel through 6.7.1, there can be an assertion failure and crash because a subvolume can be read out too soon after its root item is inserted upon subvolume creation.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2024-23850 https://cve.radiocsirt.org/vuln/ghsa-8c82-xj9x-mxgj <p>In btrfs_get_root_ref in fs/btrfs/disk-io.c in the Linux kernel through 6.7.1, there can be an assertion failure and crash because a subvolume can be read out too soon after its root item is inserted upon subvolume creation.</p> <p>In btrfs_get_root_ref in fs/btrfs/disk-io.c in the Linux kernel through 6.7.1, there can be an assertion failure and crash because a subvolume can be read out too soon after its root item is inserted upon subvolume creation.</p> https://cve.radiocsirt.org/vuln/ghsa-8c82-xj9x-mxgj https://cve.radiocsirt.org/vuln/gsd-2024-23850 gsd-2024-23850 https://cve.radiocsirt.org/vuln/gsd-2024-23850 https://cve.radiocsirt.org/vuln/msrc_cve-2024-23850 msrc_CVE-2024-23850 https://cve.radiocsirt.org/vuln/msrc_cve-2024-23850 https://cve.radiocsirt.org/vuln/oesa-2024-1283 <p><strong>Affected:</strong> openEuler:22.03-LTS: kernel</p> <p>The Linux Kernel, the operating system core itself. Security Fix(es): In the Linux kernel, the following vulnerability has been resolved: f2fs: explicitly null-terminate the xattr list When setting an xattr, explicitly null-terminate the xattr list. This eliminates the fragile assumption that the unused xattr space is always zeroed.(CVE-2023-52436) In the Linux kernel, the following vulnerability has been resolved: binder: fix use-after-free in shinker&amp;apos;s callback The mmap read lock is used during the shrinker&amp;apos;s callback, which means that using alloc-&amp;gt;vma pointer isn&amp;apos;t safe as it can race with munmap(). As of commit dd2283f2605e (&amp;quot;mm: mmap: zap pages with read mmap_sem in munmap&amp;quot;) the mmap lock is downgraded after the vma has been isolated. I was able to reproduce this issue by manually adding some delays and triggering page reclaiming through the shrinker&amp;apos;s debug sysfs. The following KASAN report confirms the UAF: ================================================================== BUG: KASAN: slab-use-after-free in zap_page_range_single+0x470/0x4b8 Read of size 8 at addr ffff356ed50e50f0 by task bash/478 CPU: 1 PID: 478 Comm: bash Not tainted 6.6.0-rc5-00055-g1c8b86a3799f-dirty #70 Hardware name: linux,dummy-virt (DT) Call trace: zap_page_range_single+0x470/0x4b8 binder_alloc_free_page+0x608/0xadc __list_lru_walk_one+0x130/0x3b0 list_lru_walk_node+0xc4/0x22c binder_shrink_scan+0x108/0x1…</p> <p><strong>Affected:</strong> openEuler:22.03-LTS: kernel</p> <p>The Linux Kernel, the operating system core itself. Security Fix(es): In the Linux kernel, the following vulnerability has been resolved: f2fs: explicitly null-terminate the xattr list When setting an xattr, explicitly null-terminate the xattr list. This eliminates the fragile assumption that the unused xattr space is always zeroed.(CVE-2023-52436) In the Linux kernel, the following vulnerability has been resolved: binder: fix use-after-free in shinker&amp;apos;s callback The mmap read lock is used during the shrinker&amp;apos;s callback, which means that using alloc-&amp;gt;vma pointer isn&amp;apos;t safe as it can race with munmap(). As of commit dd2283f2605e (&amp;quot;mm: mmap: zap pages with read mmap_sem in munmap&amp;quot;) the mmap lock is downgraded after the vma has been isolated. I was able to reproduce this issue by manually adding some delays and triggering page reclaiming through the shrinker&amp;apos;s debug sysfs. The following KASAN report confirms the UAF: ================================================================== BUG: KASAN: slab-use-after-free in zap_page_range_single+0x470/0x4b8 Read of size 8 at addr ffff356ed50e50f0 by task bash/478 CPU: 1 PID: 478 Comm: bash Not tainted 6.6.0-rc5-00055-g1c8b86a3799f-dirty #70 Hardware name: linux,dummy-virt (DT) Call trace: zap_page_range_single+0x470/0x4b8 binder_alloc_free_page+0x608/0xadc __list_lru_walk_one+0x130/0x3b0 list_lru_walk_node+0xc4/0x22c binder_shrink_scan+0x108/0x1…</p> https://cve.radiocsirt.org/vuln/oesa-2024-1283 https://cve.radiocsirt.org/vuln/suse-su-2024:0855-1 <p>Security update for the Linux Kernel</p> <p>Security update for the Linux Kernel</p> https://cve.radiocsirt.org/vuln/suse-su-2024:0855-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-23850 <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 104 more</p> <p>In btrfs_get_root_ref in fs/btrfs/disk-io.c in the Linux kernel through 6.7.1, there can be an assertion failure and crash because a subvolume can be read out too soon after its root item is inserted upon subvolume creation.</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 104 more</p> <p>In btrfs_get_root_ref in fs/btrfs/disk-io.c in the Linux kernel through 6.7.1, there can be an assertion failure and crash because a subvolume can be read out too soon after its root item is inserted upon subvolume creation.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-23850 https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0177 <p>Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen.</p> <p>Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0177