https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 17:30:07 +0000 https://cve.radiocsirt.org/vuln/bdu:2024-01936 bdu:2024-01936 https://cve.radiocsirt.org/vuln/bdu:2024-01936 https://cve.radiocsirt.org/vuln/bell-cve-2023-52569 <p><strong>Affected:</strong> Alpaquita:stream: linux-lts</p> <p><strong>Affected:</strong> Alpaquita:stream: linux-lts</p> https://cve.radiocsirt.org/vuln/bell-cve-2023-52569 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/euvd-2026-320413 EUVD-2026-320413 https://cve.radiocsirt.org/vuln/euvd-2026-320413 https://cve.radiocsirt.org/vuln/fkie_cve-2023-52569 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>btrfs: remove BUG() after failure to insert delayed dir index item</p> <p>Instead of calling BUG() when we fail to insert a delayed dir index item into the delayed node&#39;s tree, we can just release all the resources we have allocated/acquired before and return the error to the caller. This is fine because all existing call chains undo anything they have done before calling btrfs_insert_delayed_dir_index() or BUG_ON (when creating pending snapshots in the transaction commit path).</p> <p>So remove the BUG() call and do proper error handling.</p> <p>This relates to a syzbot report linked below, but does not fix it because it only prevents hitting a BUG(), it does not fix the issue where somehow we attempt to use twice the same index number for different index items.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>btrfs: remove BUG() after failure to insert delayed dir index item</p> <p>Instead of calling BUG() when we fail to insert a delayed dir index item into the delayed node&#39;s tree, we can just release all the resources we have allocated/acquired before and return the error to the caller. This is fine because all existing call chains undo anything they have done before calling btrfs_insert_delayed_dir_index() or BUG_ON (when creating pending snapshots in the transaction commit path).</p> <p>So remove the BUG() call and do proper error handling.</p> <p>This relates to a syzbot report linked below, but does not fix it because it only prevents hitting a BUG(), it does not fix the issue where somehow we attempt to use twice the same index number for different index items.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2023-52569 https://cve.radiocsirt.org/vuln/ghsa-484w-f535-whcj <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>btrfs: remove BUG() after failure to insert delayed dir index item</p> <p>Instead of calling BUG() when we fail to insert a delayed dir index item into the delayed node&#39;s tree, we can just release all the resources we have allocated/acquired before and return the error to the caller. This is fine because all existing call chains undo anything they have done before calling btrfs_insert_delayed_dir_index() or BUG_ON (when creating pending snapshots in the transaction commit path).</p> <p>So remove the BUG() call and do proper error handling.</p> <p>This relates to a syzbot report linked below, but does not fix it because it only prevents hitting a BUG(), it does not fix the issue where somehow we attempt to use twice the same index number for different index items.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>btrfs: remove BUG() after failure to insert delayed dir index item</p> <p>Instead of calling BUG() when we fail to insert a delayed dir index item into the delayed node&#39;s tree, we can just release all the resources we have allocated/acquired before and return the error to the caller. This is fine because all existing call chains undo anything they have done before calling btrfs_insert_delayed_dir_index() or BUG_ON (when creating pending snapshots in the transaction commit path).</p> <p>So remove the BUG() call and do proper error handling.</p> <p>This relates to a syzbot report linked below, but does not fix it because it only prevents hitting a BUG(), it does not fix the issue where somehow we attempt to use twice the same index number for different index items.</p> https://cve.radiocsirt.org/vuln/ghsa-484w-f535-whcj https://cve.radiocsirt.org/vuln/gsd-2023-52569 gsd-2023-52569 https://cve.radiocsirt.org/vuln/gsd-2023-52569 https://cve.radiocsirt.org/vuln/msrc_cve-2023-52569 msrc_CVE-2023-52569 https://cve.radiocsirt.org/vuln/msrc_cve-2023-52569 https://cve.radiocsirt.org/vuln/suse-su-2024:0856-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:0856-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-52569 <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 102 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: btrfs: remove BUG() after failure to insert delayed dir index item Instead of calling BUG() when we fail to insert a delayed dir index item into the delayed node&#39;s tree, we can just release all the resources we have allocated/acquired before and return the error to the caller. This is fine because all existing call chains undo anything they have done before calling btrfs_insert_delayed_dir_index() or BUG_ON (when creating pending snapshots in the transaction commit path). So remove the BUG() call and do proper error handling. This relates to a syzbot report linked below, but does not fix it because it only prevents hitting a BUG(), it does not fix the issue where somehow we attempt to use twice the same index number for different index items.</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 102 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: btrfs: remove BUG() after failure to insert delayed dir index item Instead of calling BUG() when we fail to insert a delayed dir index item into the delayed node&#39;s tree, we can just release all the resources we have allocated/acquired before and return the error to the caller. This is fine because all existing call chains undo anything they have done before calling btrfs_insert_delayed_dir_index() or BUG_ON (when creating pending snapshots in the transaction commit path). So remove the BUG() call and do proper error handling. This relates to a syzbot report linked below, but does not fix it because it only prevents hitting a BUG(), it does not fix the issue where somehow we attempt to use twice the same index number for different index items.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-52569 https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0534 <p>Ein lokaler Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand herbeizuführen oder einen nicht spezifizierten Angriff durchzuführen.</p> <p>Ein lokaler Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand herbeizuführen oder einen nicht spezifizierten Angriff durchzuführen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0534