https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-02T11:57:50.797533+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/bdu:2026-12542 bdu:2026-12542 2026-10-02T11:57:51.544095+00:00 bdu:2026-12542 https://cve.radiocsirt.org/vuln/bell-cve-2026-31509 BELL-CVE-2026-31509 2026-10-02T11:57:51.544170+00:00

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

 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0519 certfr-2026-avi-0519 — De multiples vulnérabilités ont été découvertes dans Microsoft Azure Linux. Elles permettent à un attaquant de provoque… 2026-10-02T11:57:51.544209+00:00 certfr-2026-avi-0519 https://cve.radiocsirt.org/vuln/euvd-2026-315595 EUVD-2026-315595 2026-10-02T11:57:51.544227+00:00 EUVD-2026-315595 https://cve.radiocsirt.org/vuln/fkie_cve-2026-31509 fkie_cve-2026-31509 2026-10-02T11:57:51.544245+00:00

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

nfc: nci: fix circular locking dependency in nci_close_device

nci_close_device() flushes rx_wq and tx_wq while holding req_lock. This causes a circular locking dependency because nci_rx_work() running on rx_wq can end up taking req_lock too:

nci_rx_work -> nci_rx_data_packet -> nci_data_exchange_complete -> __sk_destruct -> rawsock_destruct -> nfc_deactivate_target -> nci_deactivate_target -> nci_request -> mutex_lock(&ndev->req_lock)

Move the flush of rx_wq after req_lock has been released. This should safe (I think) because NCI_UP has already been cleared and the transport is closed, so the work will see it and return -ENETDOWN.

NIPA has been hitting this running the nci selftest with a debug kernel on roughly 4% of the runs.

 https://cve.radiocsirt.org/vuln/ghsa-x33w-8476-hwm3 GHSA-x33w-8476-hwm3 2026-10-02T11:57:51.544281+00:00

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

nfc: nci: fix circular locking dependency in nci_close_device

nci_close_device() flushes rx_wq and tx_wq while holding req_lock. This causes a circular locking dependency because nci_rx_work() running on rx_wq can end up taking req_lock too:

nci_rx_work -> nci_rx_data_packet -> nci_data_exchange_complete -> __sk_destruct -> rawsock_destruct -> nfc_deactivate_target -> nci_deactivate_target -> nci_request -> mutex_lock(&ndev->req_lock)

Move the flush of rx_wq after req_lock has been released. This should safe (I think) because NCI_UP has already been cleared and the transport is closed, so the work will see it and return -ENETDOWN.

NIPA has been hitting this running the nci selftest with a debug kernel on roughly 4% of the runs.

 https://cve.radiocsirt.org/vuln/msrc_cve-2026-31509 msrc_CVE-2026-31509 — nfc: nci: fix circular locking dependency in nci_close_device 2026-10-02T11:57:51.544304+00:00 msrc_CVE-2026-31509 https://cve.radiocsirt.org/vuln/opensuse-su-2026:21555-1 openSUSE-SU-2026:21555-1 — Security update for the Linux Kernel 2026-10-02T11:57:51.544323+00:00

Security update for the Linux Kernel

 https://cve.radiocsirt.org/vuln/suse-su-2026:23066-1 SUSE-SU-2026:23066-1 — Security update for the Linux Kernel 2026-10-02T11:57:51.544834+00:00

Security update for the Linux Kernel

 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-31509 UBUNTU-CVE-2026-31509 2026-10-02T11:57:51.545317+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: nfc: nci: fix circular locking dependency in nci_close_device nci_close_device() flushes rx_wq and tx_wq while holding req_lock. This causes a circular locking dependency because nci_rx_work() running on rx_wq can end up taking req_lock too: nci_rx_work -> nci_rx_data_packet -> nci_data_exchange_complete -> __sk_destruct -> rawsock_destruct -> nfc_deactivate_target -> nci_deactivate_target -> nci_request -> mutex_lock(&ndev->req_lock) Move the flush of rx_wq after req_lock has been released. This should safe (I think) because NCI_UP has already been cleared and the transport is closed, so the work will see it and return -ENETDOWN. NIPA has been hitting this running the nci selftest with a debug kernel on roughly 4% of the runs.

 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1252 WID-SEC-W-2026-1252 — Linux Kernel: Mehrere Schwachstellen 2026-10-02T11:57:51.545580+00:00

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen, Sicherheitsmaßnahmen zu umgehen, Informationen offenzulegen, andere nicht näher spezifizierte Auswirkungen zu verursachen und möglicherweise Code auszuführen.