<?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 04:49:42 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-68405 — wifi: mac80211: free AP_VLAN bc_buf SKBs outside IRQ lock</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-68405</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: free AP_VLAN bc_buf SKBs outside IRQ lock&lt;/p&gt;
&lt;p&gt;ieee80211_do_stop() removes AP_VLAN packets from the parent AP
ps-&amp;gt;bc_buf while holding ps-&amp;gt;bc_buf.lock with IRQs disabled. It then
calls ieee80211_free_txskb() before dropping the lock.&lt;/p&gt;
&lt;p&gt;ieee80211_free_txskb() is not just a passive SKB release. For SKBs with
TX status state it can report a dropped frame through cfg80211/nl80211,
and that path can reach netlink tap transmit. This is the same reason
the pending queue cleanup in ieee80211_do_stop() already unlinks SKBs
under the queue lock and frees them after IRQ state is restored.&lt;/p&gt;
&lt;p&gt;The buggy scenario involves two paths, with each column showing the
order within that path:&lt;/p&gt;
&lt;p&gt;AP_VLAN management TX:             AP_VLAN stop:
1. attach ACK-status state         1. clear the running state
2. queue a multicast SKB on        2. take ps-&amp;gt;bc_buf.lock with IRQs
   parent ps-&amp;gt;bc_buf                  disabled
                                   3. unlink the AP_VLAN SKB
                                   4. call ieee80211_free_txskb()&lt;/p&gt;
&lt;p&gt;Unlink matching AP_VLAN SKBs from ps-&amp;gt;bc_buf under the existing lock,
but move them to a local free queue. Drop the lock and restore IRQ state
before calling ieee80211_free_txskb().&lt;/p&gt;
&lt;p&gt;WARNING: kernel/softirq.c:430 at __local_bh_enable_ip&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: free AP_VLAN bc_buf SKBs outside IRQ lock&lt;/p&gt;
&lt;p&gt;ieee80211_do_stop() removes AP_VLAN packets from the parent AP
ps-&amp;gt;bc_buf while holding ps-&amp;gt;bc_buf.lock with IRQs disabled. It then
calls ieee80211_free_txskb() before dropping the lock.&lt;/p&gt;
&lt;p&gt;ieee80211_free_txskb() is not just a passive SKB release. For SKBs with
TX status state it can report a dropped frame through cfg80211/nl80211,
and that path can reach netlink tap transmit. This is the same reason
the pending queue cleanup in ieee80211_do_stop() already unlinks SKBs
under the queue lock and frees them after IRQ state is restored.&lt;/p&gt;
&lt;p&gt;The buggy scenario involves two paths, with each column showing the
order within that path:&lt;/p&gt;
&lt;p&gt;AP_VLAN management TX:             AP_VLAN stop:
1. attach ACK-status state         1. clear the running state
2. queue a multicast SKB on        2. take ps-&amp;gt;bc_buf.lock with IRQs
   parent ps-&amp;gt;bc_buf                  disabled
                                   3. unlink the AP_VLAN SKB
                                   4. call ieee80211_free_txskb()&lt;/p&gt;
&lt;p&gt;Unlink matching AP_VLAN SKBs from ps-&amp;gt;bc_buf under the existing lock,
but move them to a local free queue. Drop the lock and restore IRQ state
before calling ieee80211_free_txskb().&lt;/p&gt;
&lt;p&gt;WARNING: kernel/softirq.c:430 at __local_bh_enable_ip&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-68405</guid>
    </item>
  </channel>
</rss>
