<?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 13:57:24 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-68380 — wifi: ath11k: fix peer HE MCS assignment</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-68380</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: ath11k: fix peer HE MCS assignment&lt;/p&gt;
&lt;p&gt;In ath11k_wmi_send_peer_assoc_cmd(), peer&amp;#39;s transmit MCS is sent to
firmware as receive MCS while peer&amp;#39;s receive MCS sent as transmit MCS,
which goes against firmwire&amp;#39;s definition.&lt;/p&gt;
&lt;p&gt;While connecting to a misbehaved AP that advertises 0xffff (meaning not
supported) for 160 MHz transmit MCS map, firmware crashes due to 0xffff
is assigned to he_mcs-&amp;gt;rx_mcs_set field.&lt;/p&gt;
&lt;p&gt;Ext Tag: HE Capabilities
	    [...]
	    Supported HE-MCS and NSS Set
		[...]
	        Rx and Tx MCS Maps 160 MHz
		    [...]
	            Tx HE-MCS Map 160 MHz: 0xffff&lt;/p&gt;
&lt;p&gt;Swap the assignment to fix this issue.&lt;/p&gt;
&lt;p&gt;As the HE rate control mask is meant to limit our own transmit MCS, it
needs to go via he_mcs-&amp;gt;rx_mcs_set field. With the aforementioned swapping
done, change is needed as well to apply it to the peer&amp;#39;s receive MCS.&lt;/p&gt;
&lt;p&gt;Tested-on: WCN6855 hw2.1 PCI WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.41
Tested-on: QCN9274 hw2.0 PCI WLAN.WBE.1.4.1-00199-QCAHKSWPL_SILICONZ-1&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: ath11k: fix peer HE MCS assignment&lt;/p&gt;
&lt;p&gt;In ath11k_wmi_send_peer_assoc_cmd(), peer&amp;#39;s transmit MCS is sent to
firmware as receive MCS while peer&amp;#39;s receive MCS sent as transmit MCS,
which goes against firmwire&amp;#39;s definition.&lt;/p&gt;
&lt;p&gt;While connecting to a misbehaved AP that advertises 0xffff (meaning not
supported) for 160 MHz transmit MCS map, firmware crashes due to 0xffff
is assigned to he_mcs-&amp;gt;rx_mcs_set field.&lt;/p&gt;
&lt;p&gt;Ext Tag: HE Capabilities
	    [...]
	    Supported HE-MCS and NSS Set
		[...]
	        Rx and Tx MCS Maps 160 MHz
		    [...]
	            Tx HE-MCS Map 160 MHz: 0xffff&lt;/p&gt;
&lt;p&gt;Swap the assignment to fix this issue.&lt;/p&gt;
&lt;p&gt;As the HE rate control mask is meant to limit our own transmit MCS, it
needs to go via he_mcs-&amp;gt;rx_mcs_set field. With the aforementioned swapping
done, change is needed as well to apply it to the peer&amp;#39;s receive MCS.&lt;/p&gt;
&lt;p&gt;Tested-on: WCN6855 hw2.1 PCI WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.41
Tested-on: QCN9274 hw2.0 PCI WLAN.WBE.1.4.1-00199-QCAHKSWPL_SILICONZ-1&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-68380</guid>
    </item>
  </channel>
</rss>
