<?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 16:00:36 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-64117 — wifi: mac80211: capture fast-RX rate before mesh reuses skb-&gt;cb</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-64117</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: capture fast-RX rate before mesh reuses skb-&amp;gt;cb&lt;/p&gt;
&lt;p&gt;ieee80211_invoke_fast_rx() reads RX status through
IEEE80211_SKB_RXCB(skb), which aliases the same skb-&amp;gt;cb storage
that ieee80211_rx_mesh_data() reuses as IEEE80211_TX_INFO.  In the
unicast forward path, mesh_data does:&lt;/p&gt;
&lt;p&gt;info = IEEE80211_SKB_CB(fwd_skb);
	memset(info, 0, sizeof(*info));&lt;/p&gt;
&lt;p&gt;on the same skb the caller still names via rx-&amp;gt;skb, then either
queues the skb for TX (success) or kfree_skb()&amp;#39;s it (no-route)
before returning RX_QUEUED.  The caller&amp;#39;s RX_QUEUED arm then
calls sta_stats_encode_rate(status) on memory that is either
zeroed (success path) or freed (no-route path).  The latter is
KASAN slab-use-after-free in ieee80211_prepare_and_rx_handle.&lt;/p&gt;
&lt;p&gt;Fix by encoding the rate from status before invoking
ieee80211_rx_mesh_data(), so the RX_QUEUED arm consumes a value
captured while status was still backed by valid memory.&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: capture fast-RX rate before mesh reuses skb-&amp;gt;cb&lt;/p&gt;
&lt;p&gt;ieee80211_invoke_fast_rx() reads RX status through
IEEE80211_SKB_RXCB(skb), which aliases the same skb-&amp;gt;cb storage
that ieee80211_rx_mesh_data() reuses as IEEE80211_TX_INFO.  In the
unicast forward path, mesh_data does:&lt;/p&gt;
&lt;p&gt;info = IEEE80211_SKB_CB(fwd_skb);
	memset(info, 0, sizeof(*info));&lt;/p&gt;
&lt;p&gt;on the same skb the caller still names via rx-&amp;gt;skb, then either
queues the skb for TX (success) or kfree_skb()&amp;#39;s it (no-route)
before returning RX_QUEUED.  The caller&amp;#39;s RX_QUEUED arm then
calls sta_stats_encode_rate(status) on memory that is either
zeroed (success path) or freed (no-route path).  The latter is
KASAN slab-use-after-free in ieee80211_prepare_and_rx_handle.&lt;/p&gt;
&lt;p&gt;Fix by encoding the rate from status before invoking
ieee80211_rx_mesh_data(), so the RX_QUEUED arm consumes a value
captured while status was still backed by valid memory.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-64117</guid>
    </item>
  </channel>
</rss>
