https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-04T14:39:45.912457+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/bdu:2025-03750 bdu:2025-03750 2026-10-04T14:39:46.067314+00:00 bdu:2025-03750 https://cve.radiocsirt.org/vuln/bell-cve-2024-45013 BELL-CVE-2024-45013 2026-10-04T14:39:46.067379+00:00

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

 https://cve.radiocsirt.org/vuln/certfr-2024-avi-0870 certfr-2024-avi-0870 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at… 2026-10-04T14:39:46.067412+00:00 certfr-2024-avi-0870 https://cve.radiocsirt.org/vuln/cnvd-2024-39518 cnvd-2024-39518 2026-10-04T14:39:46.067431+00:00 cnvd-2024-39518 https://cve.radiocsirt.org/vuln/euvd-2026-346073 EUVD-2026-346073 2026-10-04T14:39:46.067443+00:00 EUVD-2026-346073 https://cve.radiocsirt.org/vuln/fkie_cve-2024-45013 fkie_cve-2024-45013 2026-10-04T14:39:46.067453+00:00

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

nvme: move stopping keep-alive into nvme_uninit_ctrl()

Commit 4733b65d82bd ("nvme: start keep-alive after admin queue setup") moves starting keep-alive from nvme_start_ctrl() into nvme_init_ctrl_finish(), but don't move stopping keep-alive into nvme_uninit_ctrl(), so keep-alive work can be started and keep pending after failing to start controller, finally use-after-free is triggered if nvme host driver is unloaded.

This patch fixes kernel panic when running nvme/004 in case that connection failure is triggered, by moving stopping keep-alive into nvme_uninit_ctrl().

This way is reasonable because keep-alive is now started in nvme_init_ctrl_finish().

 https://cve.radiocsirt.org/vuln/ghsa-4j5q-jrmv-h6pp GHSA-4j5q-jrmv-h6pp 2026-10-04T14:39:46.067485+00:00

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

nvme: move stopping keep-alive into nvme_uninit_ctrl()

Commit 4733b65d82bd ("nvme: start keep-alive after admin queue setup") moves starting keep-alive from nvme_start_ctrl() into nvme_init_ctrl_finish(), but don't move stopping keep-alive into nvme_uninit_ctrl(), so keep-alive work can be started and keep pending after failing to start controller, finally use-after-free is triggered if nvme host driver is unloaded.

This patch fixes kernel panic when running nvme/004 in case that connection failure is triggered, by moving stopping keep-alive into nvme_uninit_ctrl().

This way is reasonable because keep-alive is now started in nvme_init_ctrl_finish().

 https://cve.radiocsirt.org/vuln/suse-su-2024:3551-1 SUSE-SU-2024:3551-1 — Security update for the Linux Kernel 2026-10-04T14:39:46.067506+00:00

Security update for the Linux Kernel

 https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-45013 UBUNTU-CVE-2024-45013 2026-10-04T14:39:46.067625+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 88 more

In the Linux kernel, the following vulnerability has been resolved: nvme: move stopping keep-alive into nvme_uninit_ctrl() Commit 4733b65d82bd ("nvme: start keep-alive after admin queue setup") moves starting keep-alive from nvme_start_ctrl() into nvme_init_ctrl_finish(), but don't move stopping keep-alive into nvme_uninit_ctrl(), so keep-alive work can be started and keep pending after failing to start controller, finally use-after-free is triggered if nvme host driver is unloaded. This patch fixes kernel panic when running nvme/004 in case that connection failure is triggered, by moving stopping keep-alive into nvme_uninit_ctrl(). This way is reasonable because keep-alive is now started in nvme_init_ctrl_finish().

 https://cve.radiocsirt.org/vuln/wid-sec-w-2024-2124 WID-SEC-W-2024-2124 — Linux Kernel: Mehrere Schwachstellen 2026-10-04T14:39:46.067814+00:00

Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder einen unspezifischen Angriff durchzuführen.