<?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 20:16:18 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-68409 — wifi: mac80211: defer link RX stats percpu free to RCU</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-68409</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: defer link RX stats percpu free to RCU&lt;/p&gt;
&lt;p&gt;sta_remove_link() frees a removed MLO link&amp;#39;s RX stats percpu buffer right
away, but defers only the link container to RCU:&lt;/p&gt;
&lt;p&gt;sta_info_free_link(&amp;amp;alloc-&amp;gt;info);
	kfree_rcu(alloc, rcu_head);&lt;/p&gt;
&lt;p&gt;The RX fast path reads link_sta under rcu_read_lock and writes the percpu
stats. A reader that resolved link_sta before the removal keeps the
pointer. The container stays alive from the kfree_rcu, so the read still
works. But the percpu block it points to is already freed. This needs
uses_rss. That is when pcpu_rx_stats exists.&lt;/p&gt;
&lt;p&gt;The full STA teardown frees the deflink stats only after
synchronize_net(). The link removal path had no such barrier. The race is
hard to win in practice, but the free should still wait for RCU.&lt;/p&gt;
&lt;p&gt;Free the link together with its data from a single RCU callback, so the
percpu block is reclaimed only after readers drain.&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: defer link RX stats percpu free to RCU&lt;/p&gt;
&lt;p&gt;sta_remove_link() frees a removed MLO link&amp;#39;s RX stats percpu buffer right
away, but defers only the link container to RCU:&lt;/p&gt;
&lt;p&gt;sta_info_free_link(&amp;amp;alloc-&amp;gt;info);
	kfree_rcu(alloc, rcu_head);&lt;/p&gt;
&lt;p&gt;The RX fast path reads link_sta under rcu_read_lock and writes the percpu
stats. A reader that resolved link_sta before the removal keeps the
pointer. The container stays alive from the kfree_rcu, so the read still
works. But the percpu block it points to is already freed. This needs
uses_rss. That is when pcpu_rx_stats exists.&lt;/p&gt;
&lt;p&gt;The full STA teardown frees the deflink stats only after
synchronize_net(). The link removal path had no such barrier. The race is
hard to win in practice, but the free should still wait for RCU.&lt;/p&gt;
&lt;p&gt;Free the link together with its data from a single RCU callback, so the
percpu block is reclaimed only after readers drain.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-68409</guid>
    </item>
  </channel>
</rss>
