https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 09:34:15 +0000 https://cve.radiocsirt.org/vuln/bdu:2026-11593 bdu:2026-11593 https://cve.radiocsirt.org/vuln/bdu:2026-11593 https://cve.radiocsirt.org/vuln/bell-cve-2026-23167 <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> https://cve.radiocsirt.org/vuln/bell-cve-2026-23167 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0316 certfr-2026-avi-0316 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0316 https://cve.radiocsirt.org/vuln/euvd-2026-315384 EUVD-2026-315384 https://cve.radiocsirt.org/vuln/euvd-2026-315384 https://cve.radiocsirt.org/vuln/fkie_cve-2026-23167 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>nfc: nci: Fix race between rfkill and nci_unregister_device().</p> <p>syzbot reported the splat below [0] without a repro.</p> <p>It indicates that struct nci_dev.cmd_wq had been destroyed before nci_close_device() was called via rfkill.</p> <p>nci_dev.cmd_wq is only destroyed in nci_unregister_device(), which (I think) was called from virtual_ncidev_close() when syzbot close()d an fd of virtual_ncidev.</p> <p>The problem is that nci_unregister_device() destroys nci_dev.cmd_wq first and then calls nfc_unregister_device(), which removes the device from rfkill by rfkill_unregister().</p> <p>So, the device is still visible via rfkill even after nci_dev.cmd_wq is destroyed.</p> <p>Let&#39;s unregister the device from rfkill first in nci_unregister_device().</p> <p>Note that we cannot call nfc_unregister_device() before nci_close_device() because</p> <p>1) nfc_unregister_device() calls device_del() which frees all memory allocated by devm_kzalloc() and linked to ndev-&gt;conn_info_list</p> <p>2) nci_rx_work() could try to queue nci_conn_info to ndev-&gt;conn_info_list which could be leaked</p> <p>Thus, nfc_unregister_device() is split into two functions so we can remove rfkill interfaces only before nci_close_device().</p> <p>[0]: DEBUG_LOCKS_WARN_ON(1) WARNING: kernel/locking/lockdep.c:238 at hlock_class kernel/locking/lockdep.c:238 [inline], CPU#0: syz.0.8675/6349 WARNING: kernel/locking/lockdep.c:238 at check_wait_context kernel/locking/lockdep.c:4854 [inline], CPU…</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>nfc: nci: Fix race between rfkill and nci_unregister_device().</p> <p>syzbot reported the splat below [0] without a repro.</p> <p>It indicates that struct nci_dev.cmd_wq had been destroyed before nci_close_device() was called via rfkill.</p> <p>nci_dev.cmd_wq is only destroyed in nci_unregister_device(), which (I think) was called from virtual_ncidev_close() when syzbot close()d an fd of virtual_ncidev.</p> <p>The problem is that nci_unregister_device() destroys nci_dev.cmd_wq first and then calls nfc_unregister_device(), which removes the device from rfkill by rfkill_unregister().</p> <p>So, the device is still visible via rfkill even after nci_dev.cmd_wq is destroyed.</p> <p>Let&#39;s unregister the device from rfkill first in nci_unregister_device().</p> <p>Note that we cannot call nfc_unregister_device() before nci_close_device() because</p> <p>1) nfc_unregister_device() calls device_del() which frees all memory allocated by devm_kzalloc() and linked to ndev-&gt;conn_info_list</p> <p>2) nci_rx_work() could try to queue nci_conn_info to ndev-&gt;conn_info_list which could be leaked</p> <p>Thus, nfc_unregister_device() is split into two functions so we can remove rfkill interfaces only before nci_close_device().</p> <p>[0]: DEBUG_LOCKS_WARN_ON(1) WARNING: kernel/locking/lockdep.c:238 at hlock_class kernel/locking/lockdep.c:238 [inline], CPU#0: syz.0.8675/6349 WARNING: kernel/locking/lockdep.c:238 at check_wait_context kernel/locking/lockdep.c:4854 [inline], CPU…</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-23167 https://cve.radiocsirt.org/vuln/ghsa-mg8f-6pj8-cf5j <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>nfc: nci: Fix race between rfkill and nci_unregister_device().</p> <p>syzbot reported the splat below [0] without a repro.</p> <p>It indicates that struct nci_dev.cmd_wq had been destroyed before nci_close_device() was called via rfkill.</p> <p>nci_dev.cmd_wq is only destroyed in nci_unregister_device(), which (I think) was called from virtual_ncidev_close() when syzbot close()d an fd of virtual_ncidev.</p> <p>The problem is that nci_unregister_device() destroys nci_dev.cmd_wq first and then calls nfc_unregister_device(), which removes the device from rfkill by rfkill_unregister().</p> <p>So, the device is still visible via rfkill even after nci_dev.cmd_wq is destroyed.</p> <p>Let&#39;s unregister the device from rfkill first in nci_unregister_device().</p> <p>Note that we cannot call nfc_unregister_device() before nci_close_device() because</p> <p>1) nfc_unregister_device() calls device_del() which frees all memory allocated by devm_kzalloc() and linked to ndev-&gt;conn_info_list</p> <p>2) nci_rx_work() could try to queue nci_conn_info to ndev-&gt;conn_info_list which could be leaked</p> <p>Thus, nfc_unregister_device() is split into two functions so we can remove rfkill interfaces only before nci_close_device().</p> <p>[0]: DEBUG_LOCKS_WARN_ON(1) WARNING: kernel/locking/lockdep.c:238 at hlock_class kernel/locking/lockdep.c:238 [inline], CPU#0: syz.0.8675/6349 WARNING: kernel/locking/lockdep.c:238 at check_wait_context kernel/locking/lockdep.c:4854 [inline], CPU…</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>nfc: nci: Fix race between rfkill and nci_unregister_device().</p> <p>syzbot reported the splat below [0] without a repro.</p> <p>It indicates that struct nci_dev.cmd_wq had been destroyed before nci_close_device() was called via rfkill.</p> <p>nci_dev.cmd_wq is only destroyed in nci_unregister_device(), which (I think) was called from virtual_ncidev_close() when syzbot close()d an fd of virtual_ncidev.</p> <p>The problem is that nci_unregister_device() destroys nci_dev.cmd_wq first and then calls nfc_unregister_device(), which removes the device from rfkill by rfkill_unregister().</p> <p>So, the device is still visible via rfkill even after nci_dev.cmd_wq is destroyed.</p> <p>Let&#39;s unregister the device from rfkill first in nci_unregister_device().</p> <p>Note that we cannot call nfc_unregister_device() before nci_close_device() because</p> <p>1) nfc_unregister_device() calls device_del() which frees all memory allocated by devm_kzalloc() and linked to ndev-&gt;conn_info_list</p> <p>2) nci_rx_work() could try to queue nci_conn_info to ndev-&gt;conn_info_list which could be leaked</p> <p>Thus, nfc_unregister_device() is split into two functions so we can remove rfkill interfaces only before nci_close_device().</p> <p>[0]: DEBUG_LOCKS_WARN_ON(1) WARNING: kernel/locking/lockdep.c:238 at hlock_class kernel/locking/lockdep.c:238 [inline], CPU#0: syz.0.8675/6349 WARNING: kernel/locking/lockdep.c:238 at check_wait_context kernel/locking/lockdep.c:4854 [inline], CPU…</p> https://cve.radiocsirt.org/vuln/ghsa-mg8f-6pj8-cf5j https://cve.radiocsirt.org/vuln/opensuse-su-2026:20416-1 <p>Security update for the Linux Kernel</p> <p>Security update for the Linux Kernel</p> https://cve.radiocsirt.org/vuln/opensuse-su-2026:20416-1 https://cve.radiocsirt.org/vuln/suse-su-2026:0962-1 <p>Security update for the Linux Kernel</p> <p>Security update for the Linux Kernel</p> https://cve.radiocsirt.org/vuln/suse-su-2026:0962-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-23167 <p><strong>Affected:</strong> 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 231 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: nfc: nci: Fix race between rfkill and nci_unregister_device(). syzbot reported the splat below [0] without a repro. It indicates that struct nci_dev.cmd_wq had been destroyed before nci_close_device() was called via rfkill. nci_dev.cmd_wq is only destroyed in nci_unregister_device(), which (I think) was called from virtual_ncidev_close() when syzbot close()d an fd of virtual_ncidev. The problem is that nci_unregister_device() destroys nci_dev.cmd_wq first and then calls nfc_unregister_device(), which removes the device from rfkill by rfkill_unregister(). So, the device is still visible via rfkill even after nci_dev.cmd_wq is destroyed. Let&#39;s unregister the device from rfkill first in nci_unregister_device(). Note that we cannot call nfc_unregister_device() before nci_close_device() because 1) nfc_unregister_device() calls device_del() which frees all memory allocated by devm_kzalloc() and linked to ndev-&gt;conn_info_list 2) nci_rx_work() could try to queue nci_conn_info to ndev-&gt;conn_info_list which could be leaked Thus, nfc_unregister_device() is split into two functions so we can remove rfkill interfaces only before nci_close_device(). [0]: DEBUG_LOCKS_WARN_ON(1) WARNING: kernel/locking/lockdep.c:238 at hlock_class kernel/locking/lockdep.c:238 [inline], CPU#0: syz.0.8675/6349 WARNING: kernel/locking/lockdep.c:238 at check_wait_context kernel/locking/lockdep.c:4854 [inline], CPU#0: syz.0.86…</p> <p><strong>Affected:</strong> 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 231 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: nfc: nci: Fix race between rfkill and nci_unregister_device(). syzbot reported the splat below [0] without a repro. It indicates that struct nci_dev.cmd_wq had been destroyed before nci_close_device() was called via rfkill. nci_dev.cmd_wq is only destroyed in nci_unregister_device(), which (I think) was called from virtual_ncidev_close() when syzbot close()d an fd of virtual_ncidev. The problem is that nci_unregister_device() destroys nci_dev.cmd_wq first and then calls nfc_unregister_device(), which removes the device from rfkill by rfkill_unregister(). So, the device is still visible via rfkill even after nci_dev.cmd_wq is destroyed. Let&#39;s unregister the device from rfkill first in nci_unregister_device(). Note that we cannot call nfc_unregister_device() before nci_close_device() because 1) nfc_unregister_device() calls device_del() which frees all memory allocated by devm_kzalloc() and linked to ndev-&gt;conn_info_list 2) nci_rx_work() could try to queue nci_conn_info to ndev-&gt;conn_info_list which could be leaked Thus, nfc_unregister_device() is split into two functions so we can remove rfkill interfaces only before nci_close_device(). [0]: DEBUG_LOCKS_WARN_ON(1) WARNING: kernel/locking/lockdep.c:238 at hlock_class kernel/locking/lockdep.c:238 [inline], CPU#0: syz.0.8675/6349 WARNING: kernel/locking/lockdep.c:238 at check_wait_context kernel/locking/lockdep.c:4854 [inline], CPU#0: syz.0.86…</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-23167 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0421 <p>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.</p> <p>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.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0421