<?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://vulnerability.circl.lu</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>Sun, 04 Oct 2026 11:35:20 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-31509 — nfc: nci: fix circular locking dependency in nci_close_device</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-31509</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 circular locking dependency in nci_close_device&lt;/p&gt;
&lt;p&gt;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:&lt;/p&gt;
&lt;p&gt;nci_rx_work -&amp;gt; nci_rx_data_packet -&amp;gt; nci_data_exchange_complete
    -&amp;gt; __sk_destruct -&amp;gt; rawsock_destruct -&amp;gt; nfc_deactivate_target
    -&amp;gt; nci_deactivate_target -&amp;gt; nci_request -&amp;gt; mutex_lock(&amp;amp;ndev-&amp;gt;req_lock)&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;NIPA has been hitting this running the nci selftest with a debug
kernel on roughly 4% of the runs.&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 circular locking dependency in nci_close_device&lt;/p&gt;
&lt;p&gt;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:&lt;/p&gt;
&lt;p&gt;nci_rx_work -&amp;gt; nci_rx_data_packet -&amp;gt; nci_data_exchange_complete
    -&amp;gt; __sk_destruct -&amp;gt; rawsock_destruct -&amp;gt; nfc_deactivate_target
    -&amp;gt; nci_deactivate_target -&amp;gt; nci_request -&amp;gt; mutex_lock(&amp;amp;ndev-&amp;gt;req_lock)&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;NIPA has been hitting this running the nci selftest with a debug
kernel on roughly 4% of the runs.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-31509</guid>
    </item>
  </channel>
</rss>
