https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-02T15:36:29.549241+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/bdu:2026-12330 bdu:2026-12330 2026-10-02T15:36:29.788105+00:00 bdu:2026-12330 https://cve.radiocsirt.org/vuln/bell-cve-2026-23357 BELL-CVE-2026-23357 2026-10-02T15:36:29.788162+00:00

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

 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0376 certfr-2026-avi-0376 — De multiples vulnérabilités ont été découvertes dans les produits Microsoft. Elles permettent à un attaquant de provoqu… 2026-10-02T15:36:29.788196+00:00 certfr-2026-avi-0376 https://cve.radiocsirt.org/vuln/euvd-2026-315498 EUVD-2026-315498 2026-10-02T15:36:29.788214+00:00 EUVD-2026-315498 https://cve.radiocsirt.org/vuln/fkie_cve-2026-23357 fkie_cve-2026-23357 2026-10-02T15:36:29.788226+00:00

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

can: mcp251x: fix deadlock in error path of mcp251x_open

The mcp251x_open() function call free_irq() in its error path with the mpc_lock mutex held. But if an interrupt already occurred the interrupt handler will be waiting for the mpc_lock and free_irq() will deadlock waiting for the handler to finish.

This issue is similar to the one fixed in commit 7dd9c26bd6cf ("can: mcp251x: fix deadlock if an interrupt occurs during mcp251x_open") but for the error path.

To solve this issue move the call to free_irq() after the lock is released. Setting `priv->force_quit = 1` beforehand ensure that the IRQ handler will exit right away once it acquired the lock.

 https://cve.radiocsirt.org/vuln/ghsa-f94p-fcww-cpfj GHSA-f94p-fcww-cpfj 2026-10-02T15:36:29.788273+00:00

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

can: mcp251x: fix deadlock in error path of mcp251x_open

The mcp251x_open() function call free_irq() in its error path with the mpc_lock mutex held. But if an interrupt already occurred the interrupt handler will be waiting for the mpc_lock and free_irq() will deadlock waiting for the handler to finish.

This issue is similar to the one fixed in commit 7dd9c26bd6cf ("can: mcp251x: fix deadlock if an interrupt occurs during mcp251x_open") but for the error path.

To solve this issue move the call to free_irq() after the lock is released. Setting `priv->force_quit = 1` beforehand ensure that the IRQ handler will exit right away once it acquired the lock.

 https://cve.radiocsirt.org/vuln/msrc_cve-2026-23357 msrc_CVE-2026-23357 — can: mcp251x: fix deadlock in error path of mcp251x_open 2026-10-02T15:36:29.788298+00:00 msrc_CVE-2026-23357 https://cve.radiocsirt.org/vuln/opensuse-su-2026:20826-1 openSUSE-SU-2026:20826-1 — Security update for the Linux Kernel 2026-10-02T15:36:29.788315+00:00

Security update for the Linux Kernel

 https://cve.radiocsirt.org/vuln/suse-su-2026:21834-1 SUSE-SU-2026:21834-1 — Security update for the Linux Kernel 2026-10-02T15:36:29.788439+00:00

Security update for the Linux Kernel

 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-23357 UBUNTU-CVE-2026-23357 2026-10-02T15:36:29.788556+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 232 more

In the Linux kernel, the following vulnerability has been resolved: can: mcp251x: fix deadlock in error path of mcp251x_open The mcp251x_open() function call free_irq() in its error path with the mpc_lock mutex held. But if an interrupt already occurred the interrupt handler will be waiting for the mpc_lock and free_irq() will deadlock waiting for the handler to finish. This issue is similar to the one fixed in commit 7dd9c26bd6cf ("can: mcp251x: fix deadlock if an interrupt occurs during mcp251x_open") but for the error path. To solve this issue move the call to free_irq() after the lock is released. Setting `priv->force_quit = 1` beforehand ensure that the IRQ handler will exit right away once it acquired the lock.

 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0861 WID-SEC-W-2026-0861 — Linux Kernel: Mehrere Schwachstellen 2026-10-02T15:36:29.788814+00:00

Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service zu verursachen, Sicherheitsmaßnahmen zu umgehen, Informationen offenzulegen, weitere nicht spezifizierte Auswirkungen zu verursachen und potentiell Code auszuführen.