<?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>Fri, 02 Oct 2026 15:08:21 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-74325 — wifi: mt76: use kfree_rcu for offchannel link in mt76_put_vif_phy_link</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-74325</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: mt76: use kfree_rcu for offchannel link in mt76_put_vif_phy_link&lt;/p&gt;
&lt;p&gt;mt76_put_vif_phy_link() frees the offchannel mlink with plain kfree()
after rcu_assign_pointer(NULL). However, rcu_assign_pointer only prevents
future RCU readers from obtaining the pointer -- it does not wait for
existing readers that already hold it via rcu_dereference.&lt;/p&gt;
&lt;p&gt;The TX datapath (e.g. mt7996_mac_write_txwi) dereferences mlink-&amp;gt;wcid
and mlink-&amp;gt;idx under rcu_read_lock. If a TX softirq obtained the pointer
via rcu_dereference just before the NULL assignment, it will dereference
freed memory after the kfree.&lt;/p&gt;
&lt;p&gt;struct mt76_vif_link already contains an rcu_head field that is unused at
this free site -- a developer oversight, since the adjacent
kfree_rcu_mightsleep call for rx_sc in the same function shows the
pattern was understood.&lt;/p&gt;
&lt;p&gt;Replace kfree(mlink) with kfree_rcu(mlink, rcu_head).&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: mt76: use kfree_rcu for offchannel link in mt76_put_vif_phy_link&lt;/p&gt;
&lt;p&gt;mt76_put_vif_phy_link() frees the offchannel mlink with plain kfree()
after rcu_assign_pointer(NULL). However, rcu_assign_pointer only prevents
future RCU readers from obtaining the pointer -- it does not wait for
existing readers that already hold it via rcu_dereference.&lt;/p&gt;
&lt;p&gt;The TX datapath (e.g. mt7996_mac_write_txwi) dereferences mlink-&amp;gt;wcid
and mlink-&amp;gt;idx under rcu_read_lock. If a TX softirq obtained the pointer
via rcu_dereference just before the NULL assignment, it will dereference
freed memory after the kfree.&lt;/p&gt;
&lt;p&gt;struct mt76_vif_link already contains an rcu_head field that is unused at
this free site -- a developer oversight, since the adjacent
kfree_rcu_mightsleep call for rx_sc in the same function shows the
pattern was understood.&lt;/p&gt;
&lt;p&gt;Replace kfree(mlink) with kfree_rcu(mlink, rcu_head).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-74325</guid>
    </item>
  </channel>
</rss>
