https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-03T17:30:20.040141+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/bdu:2024-01936 bdu:2024-01936 2026-10-03T17:30:20.188886+00:00 bdu:2024-01936 https://cve.radiocsirt.org/vuln/bell-cve-2023-52569 BELL-CVE-2023-52569 2026-10-03T17:30:20.188959+00:00

Affected: Alpaquita:stream: linux-lts

 https://cve.radiocsirt.org/vuln/certfr-2024-avi-0242 certfr-2024-avi-0242 — De multiples vulnérabilités ont été découvertes dans <span class="textit">le noyau Linux de SUSE</span>. Certaines d'en… 2026-10-03T17:30:20.188994+00:00 certfr-2024-avi-0242 https://cve.radiocsirt.org/vuln/euvd-2026-320413 EUVD-2026-320413 2026-10-03T17:30:20.189013+00:00 EUVD-2026-320413 https://cve.radiocsirt.org/vuln/fkie_cve-2023-52569 fkie_cve-2023-52569 2026-10-03T17:30:20.189025+00:00

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'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.

 https://cve.radiocsirt.org/vuln/ghsa-484w-f535-whcj GHSA-484w-f535-whcj 2026-10-03T17:30:20.189058+00:00

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'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.

 https://cve.radiocsirt.org/vuln/gsd-2023-52569 gsd-2023-52569 2026-10-03T17:30:20.189081+00:00 gsd-2023-52569 https://cve.radiocsirt.org/vuln/msrc_cve-2023-52569 msrc_CVE-2023-52569 — btrfs: remove BUG() after failure to insert delayed dir index item 2026-10-03T17:30:20.189092+00:00 msrc_CVE-2023-52569 https://cve.radiocsirt.org/vuln/suse-su-2024:0856-1 SUSE-SU-2024:0856-1 — Security update for the Linux Kernel 2026-10-03T17:30:20.189109+00:00

Security update for the Linux Kernel

 https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-52569 UBUNTU-CVE-2023-52569 2026-10-03T17:30:20.189163+00:00

Affected: 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

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'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.

 https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0534 WID-SEC-W-2024-0534 — Linux Kernel: Mehrere Schwachstellen 2026-10-03T17:30:20.189331+00:00

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.