CVE-2025-68380 Details
Description
In the Linux kernel, the following vulnerability has been resolved: wifi: ath11k: fix peer HE MCS assignment In ath11k_wmi_send_peer_assoc_cmd(), peer's transmit MCS is sent to firmware as receive MCS while peer's receive MCS sent as transmit MCS, which goes against firmwire's definition. 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->rx_mcs_set field. Ext Tag: HE Capabilities [...] Supported HE-MCS and NSS Set [...] Rx and Tx MCS Maps 160 MHz [...] Tx HE-MCS Map 160 MHz: 0xffff Swap the assignment to fix this issue. As the HE rate control mask is meant to limit our own transmit MCS, it needs to go via he_mcs->rx_mcs_set field. With the aforementioned swapping done, change is needed as well to apply it to the peer's receive MCS. 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
A vulnerability in the Linux kernel's ath11k wireless driver can lead to a firmware crash. This issue arises because the driver's handling of the High Efficiency (HE) Modulation and Coding Scheme (MCS) assignments for peer devices is incorrect. When connecting to an access point that improperly indicates unsupported transmission capabilities, the firmware mistakenly assigns a value that triggers a crash. The vulnerability is present in the Linux kernel's stable releases, specifically within the ath11k wireless driver.
Users can update to the latest version of the Linux kernel where this vulnerability has been fixed. Instructions for updating the kernel can be found in the official Linux documentation.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
Volerion
Assessed Dec 24, 2025References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/097c870b91817779e5a312c6539099a884b1fe2b | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/381096a417b7019896e93e86f4c585c592bf98e2 | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/4304bd7a334e981f189b9973056a58f84cc2b482 | kernel.org | |
| https://git.kernel.org/stable/c/4a013ca2d490c73c40588d62712ffaa432046a04 | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/6b1a0da75932353f66e710976ca85a7131f647ff | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/92791290e4f6a1de25d35af792ab8918a70737f6 | kernel.org |
Weakness Enumeration
No weakness enumeration is available for this CVE.
Affected Products
| Product | Versions |
|---|---|
| Linux kernel | All versions |
CPE
Remediation
| |
| Qualcomm WCN6855 | All versions |
CPE
Remediation
| |
| Qualcomm QCN9274 | All versions |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Oct 13, 2026 | CVE Translated | [email protected] |
| Jun 17, 2026 | CVE Modified | kernel.org |
| Jan 11, 2026 | CVE Modified | kernel.org |
| Dec 24, 2025 | New CVE Received | kernel.org |
Volerion