https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-03T14:13:01.171154+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/bdu:2026-13766 bdu:2026-13766 2026-10-03T14:13:01.561573+00:00 bdu:2026-13766 https://cve.radiocsirt.org/vuln/bell-cve-2023-54209 BELL-CVE-2023-54209 2026-10-03T14:13:01.561661+00:00

Affected: Alpaquita:23: linux-lts, Alpaquita:stream: linux-lts

 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0108 certfr-2026-avi-0108 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at… 2026-10-03T14:13:01.561695+00:00 certfr-2026-avi-0108 https://cve.radiocsirt.org/vuln/euvd-2026-312424 EUVD-2026-312424 2026-10-03T14:13:01.561714+00:00 EUVD-2026-312424 https://cve.radiocsirt.org/vuln/fkie_cve-2023-54209 fkie_cve-2023-54209 2026-10-03T14:13:01.561727+00:00

In the Linux kernel, the following vulnerability has been resolved:

block: fix blktrace debugfs entries leakage

Commit 99d055b4fd4b ("block: remove per-disk debugfs files in blk_unregister_queue") moves blk_trace_shutdown() from blk_release_queue() to blk_unregister_queue(), this is safe if blktrace is created through sysfs, however, there is a regression in corner case.

blktrace can still be enabled after del_gendisk() through ioctl if the disk is opened before del_gendisk(), and if blktrace is not shutdown through ioctl before closing the disk, debugfs entries will be leaked.

Fix this problem by shutdown blktrace in disk_release(), this is safe because blk_trace_remove() is reentrant.

 https://cve.radiocsirt.org/vuln/ghsa-mxfp-7rqw-mqhc GHSA-mxfp-7rqw-mqhc 2026-10-03T14:13:01.561760+00:00

In the Linux kernel, the following vulnerability has been resolved:

block: fix blktrace debugfs entries leakage

Commit 99d055b4fd4b ("block: remove per-disk debugfs files in blk_unregister_queue") moves blk_trace_shutdown() from blk_release_queue() to blk_unregister_queue(), this is safe if blktrace is created through sysfs, however, there is a regression in corner case.

blktrace can still be enabled after del_gendisk() through ioctl if the disk is opened before del_gendisk(), and if blktrace is not shutdown through ioctl before closing the disk, debugfs entries will be leaked.

Fix this problem by shutdown blktrace in disk_release(), this is safe because blk_trace_remove() is reentrant.

 https://cve.radiocsirt.org/vuln/suse-su-2026:0278-1 SUSE-SU-2026:0278-1 — Security update for the Linux Kernel 2026-10-03T14:13:01.561783+00:00

Security update for the Linux Kernel

 https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-54209 UBUNTU-CVE-2023-54209 2026-10-03T14:13:01.562033+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 79 more

In the Linux kernel, the following vulnerability has been resolved: block: fix blktrace debugfs entries leakage Commit 99d055b4fd4b ("block: remove per-disk debugfs files in blk_unregister_queue") moves blk_trace_shutdown() from blk_release_queue() to blk_unregister_queue(), this is safe if blktrace is created through sysfs, however, there is a regression in corner case. blktrace can still be enabled after del_gendisk() through ioctl if the disk is opened before del_gendisk(), and if blktrace is not shutdown through ioctl before closing the disk, debugfs entries will be leaked. Fix this problem by shutdown blktrace in disk_release(), this is safe because blk_trace_remove() is reentrant.

 https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2941 WID-SEC-W-2025-2941 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service 2026-10-03T14:13:01.562167+00:00

Ein Angreifer kann diese Schwachstellen ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu Denial‑of‑Service, Speicherbeschädigung oder weiteren nicht definierten Auswirkungen führen.