{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-68380 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-68380 is a denial of service vulnerability in Linux, published on 24 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-68380 and fix it if it is affected.\n\nWhat it is: CVE-2025-68380 is a denial of service vulnerability in Linux, published on 24 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-68380 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-68380/ (Markdown: https://insights.sbomify.com/CVE-2025-68380/index.md)","id":"CVE-2025-68380","markdown":"https://insights.sbomify.com/CVE-2025-68380/index.md","name":"CVE-2025-68380","record":{"aliases":["BELL-CVE-2025-68380","DEBIAN-CVE-2025-68380","GHSA-96x7-qg22-qw59","ROOT-OS-DEBIAN-12-CVE-2025-68380","ROOT-OS-DEBIAN-13-CVE-2025-68380","ROOT-OS-UBUNTU-2404-CVE-2025-68380","UBUNTU-CVE-2025-68380"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel WiFi driver","requires_auth":"none","summary":"A misconfigured access point can crash the Linux kernel's ath11k WiFi driver by triggering a firmware crash due to incorrect MCS assignment.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: ath11k: fix peer HE MCS assignment\n\nIn ath11k_wmi_send_peer_assoc_cmd(), peer's transmit MCS is sent to\nfirmware as receive MCS while peer's receive MCS sent as transmit MCS,\nwhich goes against firmwire's definition.\n\nWhile connecting to a misbehaved AP that advertises 0xffff (meaning not\nsupported) for 160 MHz transmit MCS map, firmware crashes due to 0xffff\nis assigned to he_mcs-\u003erx_mcs_set field.\n\n\tExt Tag: HE Capabilities\n\t    [...]\n\t    Supported HE-MCS and NSS Set\n\t\t[...]\n\t        Rx and Tx MCS Maps 160 MHz\n\t\t    [...]\n\t            Tx HE-MCS Map 160 MHz: 0xffff\n\nSwap the assignment to fix this issue.\n\nAs the HE rate control mask is meant to limit our own transmit MCS, it\nneeds to go via he_mcs-\u003erx_mcs_set field. With the aforementioned swapping\ndone, change is needed as well to apply it to the peer's receive MCS.\n\nTested-on: WCN6855 hw2.1 PCI WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.41\nTested-on: QCN9274 hw2.0 PCI WLAN.WBE.1.4.1-00199-QCAHKSWPL_SILICONZ-1","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"wifi: ath11k: fix peer HE MCS assignment","id":"CVE-2025-68380","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2025"},"n_packages":0,"n_references":6,"next":{"headline":"Packetbeat Improper Bounds Check","id":"CVE-2025-68381"},"packages":[],"prev":{"headline":"RDMA/rxe: Fix null deref on srq-\u003erq.queue after resize failure","id":"CVE-2025-68379"},"products":["Linux"],"published":"2025-12-24","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-05-11","vendors":["Linux"]},"summary":"A misconfigured access point can crash the Linux kernel's ath11k WiFi driver by triggering a firmware crash due to incorrect MCS assignment.","url":"https://insights.sbomify.com/CVE-2025-68380/"}