<?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-29T20:18:49.784395+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-2026-68409</id>
    <title>CVE-2026-68409 — wifi: mac80211: defer link RX stats percpu free to RCU</title>
    <updated>2026-09-29T20:18:49.786910+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: defer link RX stats percpu free to RCU</p>
<p>sta_remove_link() frees a removed MLO link's RX stats percpu buffer right
away, but defers only the link container to RCU:</p>
<p>sta_info_free_link(&amp;alloc-&gt;info);
	kfree_rcu(alloc, rcu_head);</p>
<p>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.</p>
<p>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.</p>
<p>Free the link together with its data from a single RCU callback, so the
percpu block is reclaimed only after readers drain.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-68409"/>
  </entry>
</feed>
