<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-29T23:46:02.659583+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2023-54288</id>
    <title>CVE-2023-54288 — wifi: mac80211: fortify the spinlock against deadlock by interrupt</title>
    <updated>2026-09-29T23:46:02.718273+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>wifi: mac80211: fortify the spinlock against deadlock by interrupt</p>
<p>In the function ieee80211_tx_dequeue() there is a particular locking
sequence:</p>
<p>begin:
	spin_lock(&amp;local-&gt;queue_stop_reason_lock);
	q_stopped = local-&gt;queue_stop_reasons[q];
	spin_unlock(&amp;local-&gt;queue_stop_reason_lock);</p>
<p>However small the chance (increased by ftracetest), an asynchronous
interrupt can occur in between of spin_lock() and spin_unlock(),
and the interrupt routine will attempt to lock the same
&amp;local-&gt;queue_stop_reason_lock again.</p>
<p>This will cause a costly reset of the CPU and the wifi device or an
altogether hang in the single CPU and single core scenario.</p>
<p>The only remaining spin_lock(&amp;local-&gt;queue_stop_reason_lock) that
did not disable interrupts was patched, which should prevent any
deadlocks on the same CPU/core and the same wifi device.</p>
<p>This is the probable trace of the deadlock:</p>
<p>kernel: ================================
kernel: WARNING: inconsistent lock state
kernel: 6.3.0-rc6-mt-20230401-00001-gf86822a1170f #4 Tainted: G        W
kernel: --------------------------------
kernel: inconsistent {IN-SOFTIRQ-W} -&gt; {SOFTIRQ-ON-W} usage.
kernel: kworker/5:0/25656 [HC0[0]:SC0[0]:HE1:SE1] takes:
kernel: ffff9d6190779478 (&amp;local-&gt;queue_stop_reason_lock){+.?.}-{2:2}, at: return_to_handler+0x0/0x40
kernel: {IN-SOFTIRQ-W} state was registered at:
kernel:   lock_acquire+0xc7/0x2d0
kernel:   _raw_spin_lock+0x36/0x50
kernel:   ieee802…</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2023-54288"/>
  </entry>
</feed>
