https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-04T02:30:04.954265+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/bdu:2025-08996 bdu:2025-08996 2026-10-04T02:30:05.165695+00:00 bdu:2025-08996 https://cve.radiocsirt.org/vuln/bell-cve-2025-38105 BELL-CVE-2025-38105 2026-10-04T02:30:05.165768+00:00

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

 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0723 certfr-2025-avi-0723 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at… 2026-10-04T02:30:05.165813+00:00 certfr-2025-avi-0723 https://cve.radiocsirt.org/vuln/euvd-2026-323473 EUVD-2026-323473 2026-10-04T02:30:05.165848+00:00 EUVD-2026-323473 https://cve.radiocsirt.org/vuln/fkie_cve-2025-38105 fkie_cve-2025-38105 2026-10-04T02:30:05.165867+00:00

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

ALSA: usb-audio: Kill timer properly at removal

The USB-audio MIDI code initializes the timer, but in a rare case, the driver might be freed without the disconnect call. This leaves the timer in an active state while the assigned object is released via snd_usbmidi_free(), which ends up with a kernel warning when the debug configuration is enabled, as spotted by fuzzer.

For avoiding the problem, put timer_shutdown_sync() at snd_usbmidi_free(), so that the timer can be killed properly. While we're at it, replace the existing timer_delete_sync() at the disconnect callback with timer_shutdown_sync(), too.

 https://cve.radiocsirt.org/vuln/ghsa-7f9v-c8qw-m5c4 GHSA-7f9v-c8qw-m5c4 2026-10-04T02:30:05.165907+00:00

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

ALSA: usb-audio: Kill timer properly at removal

The USB-audio MIDI code initializes the timer, but in a rare case, the driver might be freed without the disconnect call. This leaves the timer in an active state while the assigned object is released via snd_usbmidi_free(), which ends up with a kernel warning when the debug configuration is enabled, as spotted by fuzzer.

For avoiding the problem, put timer_shutdown_sync() at snd_usbmidi_free(), so that the timer can be killed properly. While we're at it, replace the existing timer_delete_sync() at the disconnect callback with timer_shutdown_sync(), too.

 https://cve.radiocsirt.org/vuln/msrc_cve-2025-38105 msrc_CVE-2025-38105 — ALSA: usb-audio: Kill timer properly at removal 2026-10-04T02:30:05.165928+00:00 msrc_CVE-2025-38105 https://cve.radiocsirt.org/vuln/suse-su-2025:02846-1 SUSE-SU-2025:02846-1 — Security update for the Linux Kernel 2026-10-04T02:30:05.165946+00:00

Security update for the Linux Kernel

 https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-38105 UBUNTU-CVE-2025-38105 2026-10-04T02:30:05.166009+00:00

Affected: Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 213 more

In the Linux kernel, the following vulnerability has been resolved: ALSA: usb-audio: Kill timer properly at removal The USB-audio MIDI code initializes the timer, but in a rare case, the driver might be freed without the disconnect call. This leaves the timer in an active state while the assigned object is released via snd_usbmidi_free(), which ends up with a kernel warning when the debug configuration is enabled, as spotted by fuzzer. For avoiding the problem, put timer_shutdown_sync() at snd_usbmidi_free(), so that the timer can be killed properly. While we're at it, replace the existing timer_delete_sync() at the disconnect callback with timer_shutdown_sync(), too.

 https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1452 WID-SEC-W-2025-1452 — Linux Kernel: Mehrere Schwachstellen 2026-10-04T02:30:05.166268+00:00

Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und andere, nicht spezifizierte Auswirkungen zu verursachen.