<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Thu, 19 Nov 2026 17:19:46 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-23167 — nfc: nci: Fix race between rfkill and nci_unregister_device().</title>
      <link>https://db.gcve.eu/vuln/cve-2026-23167</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;nfc: nci: Fix race between rfkill and nci_unregister_device().&lt;/p&gt;
&lt;p&gt;syzbot reported the splat below [0] without a repro.&lt;/p&gt;
&lt;p&gt;It indicates that struct nci_dev.cmd_wq had been destroyed before
nci_close_device() was called via rfkill.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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().&lt;/p&gt;
&lt;p&gt;So, the device is still visible via rfkill even after nci_dev.cmd_wq
is destroyed.&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s unregister the device from rfkill first in nci_unregister_device().&lt;/p&gt;
&lt;p&gt;Note that we cannot call nfc_unregister_device() before
nci_close_device() because&lt;/p&gt;
&lt;p&gt;1) nfc_unregister_device() calls device_del() which frees
     all memory allocated by devm_kzalloc() and linked to
     ndev-&amp;gt;conn_info_list&lt;/p&gt;
&lt;p&gt;2) nci_rx_work() could try to queue nci_conn_info to
     ndev-&amp;gt;conn_info_list which could be leaked&lt;/p&gt;
&lt;p&gt;Thus, nfc_unregister_device() is split into two functions so we
can remove rfkill interfaces only before nci_close_device().&lt;/p&gt;
&lt;p&gt;[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…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;nfc: nci: Fix race between rfkill and nci_unregister_device().&lt;/p&gt;
&lt;p&gt;syzbot reported the splat below [0] without a repro.&lt;/p&gt;
&lt;p&gt;It indicates that struct nci_dev.cmd_wq had been destroyed before
nci_close_device() was called via rfkill.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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().&lt;/p&gt;
&lt;p&gt;So, the device is still visible via rfkill even after nci_dev.cmd_wq
is destroyed.&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s unregister the device from rfkill first in nci_unregister_device().&lt;/p&gt;
&lt;p&gt;Note that we cannot call nfc_unregister_device() before
nci_close_device() because&lt;/p&gt;
&lt;p&gt;1) nfc_unregister_device() calls device_del() which frees
     all memory allocated by devm_kzalloc() and linked to
     ndev-&amp;gt;conn_info_list&lt;/p&gt;
&lt;p&gt;2) nci_rx_work() could try to queue nci_conn_info to
     ndev-&amp;gt;conn_info_list which could be leaked&lt;/p&gt;
&lt;p&gt;Thus, nfc_unregister_device() is split into two functions so we
can remove rfkill interfaces only before nci_close_device().&lt;/p&gt;
&lt;p&gt;[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…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-23167</guid>
    </item>
    <item>
      <title>USN-8162-1 — linux-nvidia-tegra-5.15 vulnerabilities</title>
      <link>https://db.gcve.eu/vuln/usn-8162-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:20.04:LTS: linux-nvidia-tegra-5.15&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - ARM64 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Drivers core;
  - Bluetooth drivers;
  - DMA engine subsystem;
  - GPU drivers;
  - HID subsystem;
  - Intel Trace Hub HW tracing drivers;
  - IIO ADC drivers;
  - IRQ chip drivers;
  - Modular ISDN driver;
  - LED subsystem;
  - UACCE accelerator framework;
  - Ethernet bonding driver;
  - Network drivers;
  - STMicroelectronics network drivers;
  - Ethernet team driver;
  - NVME drivers;
  - PHY drivers;
  - SLIMbus drivers;
  - W1 Dallas&amp;#39;s 1-wire bus driver;
  - Xen hypervisor drivers;
  - BTRFS file system;
  - Ext4 file system;
  - Network file system (NFS) client;
  - Network file system (NFS) server daemon;
  - NTFS3 file system;
  - SMB network file system;
  - NFC subsystem;
  - BPF subsystem;
  - IRQ subsystem;
  - Memory management;
  - Bluetooth subsystem;
  - CAN network layer;
  - Networking core;
  - IPv4 networking;
  - IPv6 networking;
  - L2TP protocol;
  - Netfilter;
  - NET/ROM layer;
  - Network traffic control;
  - SCTP protocol;
  - TLS protocol;
  - XFRM subsystem;
  - Creative Sound Blaster X-Fi driver;
  - USB sound devices;
(CVE-2023-53421, CVE-2023-53520, CVE-2023-53662, CVE-2023-54207,
CVE-2025-37849, CVE-2025-38057, CVE-2025-38125, CVE-2025-38232,
CVE-2025-38408, CVE-2025-38591, CVE-2025-4014…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:20.04:LTS: linux-nvidia-tegra-5.15&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - ARM64 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Drivers core;
  - Bluetooth drivers;
  - DMA engine subsystem;
  - GPU drivers;
  - HID subsystem;
  - Intel Trace Hub HW tracing drivers;
  - IIO ADC drivers;
  - IRQ chip drivers;
  - Modular ISDN driver;
  - LED subsystem;
  - UACCE accelerator framework;
  - Ethernet bonding driver;
  - Network drivers;
  - STMicroelectronics network drivers;
  - Ethernet team driver;
  - NVME drivers;
  - PHY drivers;
  - SLIMbus drivers;
  - W1 Dallas&amp;#39;s 1-wire bus driver;
  - Xen hypervisor drivers;
  - BTRFS file system;
  - Ext4 file system;
  - Network file system (NFS) client;
  - Network file system (NFS) server daemon;
  - NTFS3 file system;
  - SMB network file system;
  - NFC subsystem;
  - BPF subsystem;
  - IRQ subsystem;
  - Memory management;
  - Bluetooth subsystem;
  - CAN network layer;
  - Networking core;
  - IPv4 networking;
  - IPv6 networking;
  - L2TP protocol;
  - Netfilter;
  - NET/ROM layer;
  - Network traffic control;
  - SCTP protocol;
  - TLS protocol;
  - XFRM subsystem;
  - Creative Sound Blaster X-Fi driver;
  - USB sound devices;
(CVE-2023-53421, CVE-2023-53520, CVE-2023-53662, CVE-2023-54207,
CVE-2025-37849, CVE-2025-38057, CVE-2025-38125, CVE-2025-38232,
CVE-2025-38408, CVE-2025-38591, CVE-2025-4014…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/usn-8162-1</guid>
    </item>
  </channel>
</rss>
