<?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>Tue, 29 Sep 2026 12:49:49 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-54288 — wifi: mac80211: fortify the spinlock against deadlock by interrupt</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2023-54288</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;wifi: mac80211: fortify the spinlock against deadlock by interrupt&lt;/p&gt;
&lt;p&gt;In the function ieee80211_tx_dequeue() there is a particular locking
sequence:&lt;/p&gt;
&lt;p&gt;begin:
	spin_lock(&amp;amp;local-&amp;gt;queue_stop_reason_lock);
	q_stopped = local-&amp;gt;queue_stop_reasons[q];
	spin_unlock(&amp;amp;local-&amp;gt;queue_stop_reason_lock);&lt;/p&gt;
&lt;p&gt;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;amp;local-&amp;gt;queue_stop_reason_lock again.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;The only remaining spin_lock(&amp;amp;local-&amp;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.&lt;/p&gt;
&lt;p&gt;This is the probable trace of the deadlock:&lt;/p&gt;
&lt;p&gt;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} -&amp;gt; {SOFTIRQ-ON-W} usage.
kernel: kworker/5:0/25656 [HC0[0]:SC0[0]:HE1:SE1] takes:
kernel: ffff9d6190779478 (&amp;amp;local-&amp;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…&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;wifi: mac80211: fortify the spinlock against deadlock by interrupt&lt;/p&gt;
&lt;p&gt;In the function ieee80211_tx_dequeue() there is a particular locking
sequence:&lt;/p&gt;
&lt;p&gt;begin:
	spin_lock(&amp;amp;local-&amp;gt;queue_stop_reason_lock);
	q_stopped = local-&amp;gt;queue_stop_reasons[q];
	spin_unlock(&amp;amp;local-&amp;gt;queue_stop_reason_lock);&lt;/p&gt;
&lt;p&gt;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;amp;local-&amp;gt;queue_stop_reason_lock again.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;The only remaining spin_lock(&amp;amp;local-&amp;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.&lt;/p&gt;
&lt;p&gt;This is the probable trace of the deadlock:&lt;/p&gt;
&lt;p&gt;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} -&amp;gt; {SOFTIRQ-ON-W} usage.
kernel: kworker/5:0/25656 [HC0[0]:SC0[0]:HE1:SE1] takes:
kernel: ffff9d6190779478 (&amp;amp;local-&amp;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…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2023-54288</guid>
    </item>
  </channel>
</rss>
