<?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>Sun, 04 Oct 2026 13:00:37 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-64030 — wifi: mac80211: bounds-check link_id in ieee80211_ml_epcs</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-64030</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: bounds-check link_id in ieee80211_ml_epcs&lt;/p&gt;
&lt;p&gt;IEEE80211_MLE_STA_EPCS_CONTROL_LINK_ID is 0x000f, so link_id extracted
from a PRIO_ACCESS ML element PER_STA_PROFILE subelement can be 0..15.
sdata-&amp;gt;link[] has IEEE80211_MLD_MAX_NUM_LINKS (15) entries (indices 0..14),
making index 15 out-of-bounds.&lt;/p&gt;
&lt;p&gt;A connected WiFi 7 AP can trigger this by sending an EPCS Enable Response
action frame with a PER_STA_PROFILE subelement where link_id = 15.  The
unsolicited-notification path (dialog_token = 0) is reachable any time
EPCS is already enabled, without any prior client request.&lt;/p&gt;
&lt;p&gt;sdata-&amp;gt;link[15] reads into the first word of sdata-&amp;gt;activate_links_work
(a wiphy_work whose embedded list_head is non-NULL after INIT_LIST_HEAD),
so the NULL check on the result does not catch the invalid access.  The
garbage pointer is then passed to ieee80211_sta_wmm_params(), which
dereferences link-&amp;gt;sdata and crashes the kernel.&lt;/p&gt;
&lt;p&gt;The same class of bug was fixed for ieee80211_ml_reconfiguration() by
commit 162d331d833d (&amp;#34;wifi: mac80211: bounds-check link_id in
ieee80211_ml_reconfiguration&amp;#34;).&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: bounds-check link_id in ieee80211_ml_epcs&lt;/p&gt;
&lt;p&gt;IEEE80211_MLE_STA_EPCS_CONTROL_LINK_ID is 0x000f, so link_id extracted
from a PRIO_ACCESS ML element PER_STA_PROFILE subelement can be 0..15.
sdata-&amp;gt;link[] has IEEE80211_MLD_MAX_NUM_LINKS (15) entries (indices 0..14),
making index 15 out-of-bounds.&lt;/p&gt;
&lt;p&gt;A connected WiFi 7 AP can trigger this by sending an EPCS Enable Response
action frame with a PER_STA_PROFILE subelement where link_id = 15.  The
unsolicited-notification path (dialog_token = 0) is reachable any time
EPCS is already enabled, without any prior client request.&lt;/p&gt;
&lt;p&gt;sdata-&amp;gt;link[15] reads into the first word of sdata-&amp;gt;activate_links_work
(a wiphy_work whose embedded list_head is non-NULL after INIT_LIST_HEAD),
so the NULL check on the result does not catch the invalid access.  The
garbage pointer is then passed to ieee80211_sta_wmm_params(), which
dereferences link-&amp;gt;sdata and crashes the kernel.&lt;/p&gt;
&lt;p&gt;The same class of bug was fixed for ieee80211_ml_reconfiguration() by
commit 162d331d833d (&amp;#34;wifi: mac80211: bounds-check link_id in
ieee80211_ml_reconfiguration&amp;#34;).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-64030</guid>
    </item>
  </channel>
</rss>
