CVE-2025-68380: wifi: ath11k: fix peer HE MCS assignment
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.20% (FIRST EPSS).
- Fixed version: Linux Linux 097c870b91817779e5a312c6539099a884b1fe2b, 381096a417b7019896e93e86f4c585c592bf98e2, 4304bd7a334e981f189b9973056a58f84cc2b482.
Low priority for now. Upgrade to Linux Linux 097c870b91817779e5a312c6539099a884b1fe2b, 381096a417b7019896e93e86f4c585c592bf98e2, 4304bd7a334e981f189b9973056a58f84cc2b482 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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
- Published
- Dec 24, 2025
- Updated
- Oct 13, 2026
- EPSS
- 0.2% · 9th percentile
- CWE
- —
Report tools
Action score
0
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.16affected
- 61fe43e7216df6e9a912d831aafc7142fa20f280 and later · before 92791290e4f6a1de25d35af792ab8918a70737f6affected · git
- 61fe43e7216df6e9a912d831aafc7142fa20f280 and later · before 4304bd7a334e981f189b9973056a58f84cc2b482affected · git
- 61fe43e7216df6e9a912d831aafc7142fa20f280 and later · before 097c870b91817779e5a312c6539099a884b1fe2baffected · git
- 61fe43e7216df6e9a912d831aafc7142fa20f280 and later · before 381096a417b7019896e93e86f4c585c592bf98e2affected · git
- 61fe43e7216df6e9a912d831aafc7142fa20f280 and later · before 6b1a0da75932353f66e710976ca85a7131f647ffaffected · git
- 61fe43e7216df6e9a912d831aafc7142fa20f280 and later · before 4a013ca2d490c73c40588d62712ffaa432046a04affected · git
- before 5.16not affected · semver
- 6.1.160 and later · up to and including 6.1.*not affected · semver
- 6.6.120 and later · up to and including 6.6.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.162-1 | 6.1.162-1 |
| Debian:13 | linux | before 6.12.63-1 | 6.12.63-1 |
| Debian:14 | linux | before 6.17.13-1 | 6.17.13-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2025-68378Dec 24, 2025 · bpf: Fix stackmap overflow check in __bpf_get_stackid()0Monitor
- ← EarlierCVE-2025-68379Dec 24, 2025 · RDMA/rxe: Fix null deref on srq->rq.queue after resize failure31Monitor
- Later →CVE-2025-68724Dec 24, 2025 · crypto: asymmetric_keys - prevent overflow in asymmetric_key_generate_id31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 097c870b91817779e5a312c6539099a884b1fe2b | Vendor (CNA) |
| Linux Linux | 381096a417b7019896e93e86f4c585c592bf98e2 | Vendor (CNA) |
| Linux Linux | 4304bd7a334e981f189b9973056a58f84cc2b482 | Vendor (CNA) |
| Linux Linux | 4a013ca2d490c73c40588d62712ffaa432046a04 | Vendor (CNA) |
| Linux Linux | 6b1a0da75932353f66e710976ca85a7131f647ff | Vendor (CNA) |
| Linux Linux | 92791290e4f6a1de25d35af792ab8918a70737f6 | Vendor (CNA) |
| debian:linux | 6.1.162-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/381096a417b7019896e93e86f4c585c592bf98e2
- git.kernel.org/stable/c/4304bd7a334e981f189b9973056a58f84cc2b482
- git.kernel.org/stable/c/4a013ca2d490c73c40588d62712ffaa432046a04
- git.kernel.org/stable/c/6b1a0da75932353f66e710976ca85a7131f647ff
- git.kernel.org/stable/c/92791290e4f6a1de25d35af792ab8918a70737f6
Vendor advisories and official records. Exploit/PoC links are deliberately left out.