https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-04T08:19:08.281313+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/bdu:2026-02818 bdu:2026-02818 2026-10-04T08:19:08.618636+00:00 bdu:2026-02818 https://cve.radiocsirt.org/vuln/bell-cve-2025-68249 BELL-CVE-2025-68249 2026-10-04T08:19:08.618708+00:00

Affected: Alpaquita:23: linux-lts, Alpaquita:25: 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-04T08:19:08.618743+00:00 certfr-2026-avi-0108 https://cve.radiocsirt.org/vuln/euvd-2026-315078 EUVD-2026-315078 2026-10-04T08:19:08.618761+00:00 EUVD-2026-315078 https://cve.radiocsirt.org/vuln/fkie_cve-2025-68249 fkie_cve-2025-68249 2026-10-04T08:19:08.618773+00:00

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

most: usb: hdm_probe: Fix calling put_device() before device initialization

The early error path in hdm_probe() can jump to err_free_mdev before &mdev->dev has been initialized with device_initialize(). Calling put_device(&mdev->dev) there triggers a device core WARN and ends up invoking kref_put(&kobj->kref, kobject_release) on an uninitialized kobject.

In this path the private struct was only kmalloc'ed and the intended release is effectively kfree(mdev) anyway, so free it directly instead of calling put_device() on an uninitialized device.

This removes the WARNING and fixes the pre-initialization error path.

 https://cve.radiocsirt.org/vuln/ghsa-wpmx-q548-j5gm GHSA-wpmx-q548-j5gm 2026-10-04T08:19:08.618824+00:00

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

most: usb: hdm_probe: Fix calling put_device() before device initialization

The early error path in hdm_probe() can jump to err_free_mdev before &mdev->dev has been initialized with device_initialize(). Calling put_device(&mdev->dev) there triggers a device core WARN and ends up invoking kref_put(&kobj->kref, kobject_release) on an uninitialized kobject.

In this path the private struct was only kmalloc'ed and the intended release is effectively kfree(mdev) anyway, so free it directly instead of calling put_device() on an uninitialized device.

This removes the WARNING and fixes the pre-initialization error path.

 https://cve.radiocsirt.org/vuln/opensuse-su-2026:20145-1 openSUSE-SU-2026:20145-1 — Security update for the Linux Kernel 2026-10-04T08:19:08.618860+00:00

Security update for the Linux Kernel

 https://cve.radiocsirt.org/vuln/suse-su-2026:0278-1 SUSE-SU-2026:0278-1 — Security update for the Linux Kernel 2026-10-04T08:19:08.619032+00:00

Security update for the Linux Kernel

 https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-68249 UBUNTU-CVE-2025-68249 2026-10-04T08:19:08.619271+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 175 more

In the Linux kernel, the following vulnerability has been resolved: most: usb: hdm_probe: Fix calling put_device() before device initialization The early error path in hdm_probe() can jump to err_free_mdev before &mdev->dev has been initialized with device_initialize(). Calling put_device(&mdev->dev) there triggers a device core WARN and ends up invoking kref_put(&kobj->kref, kobject_release) on an uninitialized kobject. In this path the private struct was only kmalloc'ed and the intended release is effectively kfree(mdev) anyway, so free it directly instead of calling put_device() on an uninitialized device. This removes the WARNING and fixes the pre-initialization error path.

 https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2868 WID-SEC-W-2025-2868 — Linux Kernel: Mehrere Schwachstellen 2026-10-04T08:19:08.619549+00:00

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.