{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-90399 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-90399 is a high-severity memory corruption vulnerability in Linux, published on 17 Sep 2026. 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-2026-90399 and fix it if it is affected.\n\nWhat it is: CVE-2026-90399 is a high-severity memory corruption vulnerability in Linux, published on 17 Sep 2026. 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-2026-90399 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-2026-90399/ (Markdown: https://insights.sbomify.com/CVE-2026-90399/index.md)","id":"CVE-2026-90399","markdown":"https://insights.sbomify.com/CVE-2026-90399/index.md","name":"CVE-2026-90399","record":{"aliases":["AZL-102621","BELL-CVE-2026-90399","DEBIAN-CVE-2026-90399","GHSA-2568-8wcm-qh64","UBUNTU-CVE-2026-90399"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel WiFi driver","requires_auth":"none","summary":"A stride mismatch in the ath12k WiFi driver allows out-of-bounds writes when processing short firmware TLVs, potentially leading to memory corruption or crashes.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":8.4,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: ath12k: fix stride mismatch in mac_phy_caps_parse()\n\nCurrently, in ath12k_wmi_mac_phy_caps_parse(), kzalloc() sizes the\nmac_phy_caps buffer as tot_phy_id * len, where len is clamped to\nmin(firmware_len, sizeof(struct ath12k_wmi_mac_phy_caps_params)). The\nsubsequent memcpy() destination advances by sizeof(full struct) per slot\nvia C pointer arithmetic, not by the clamped len. When firmware sends\nshort TLVs, the second and later slots are written past the end of the\nallocation.\n\nThe reader in ath12k_pull_mac_phy_cap_svc_ready_ext() also indexes the\nbuffer with full-struct pointer arithmetic, so the allocation must match\nthat stride.\n\nFix by using kzalloc_objs(), which derives the element size from the\npointer type, making allocation size and pointer stride provably\nconsistent regardless of what len the firmware provides.\n\nTested-on: WCN7850 hw2.0 PCI WLAN.HMT.1.1.c7-00108-QCAHMTSWPL_V1.0_V2.0_SILICONZ_UPSTREAM-3","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: ath12k: fix stride mismatch in mac_phy_caps_parse()","id":"CVE-2026-90399","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"md: recheck spare changes before starting sync","id":"CVE-2026-90400"},"packages":[],"prev":{"headline":"wifi: ath11k: fix stride mismatch in mac_phy_caps_parse()","id":"CVE-2026-90398"},"products":["Linux"],"published":"2026-09-17","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-21","vendors":["Linux"]},"summary":"A stride mismatch in the ath12k WiFi driver allows out-of-bounds writes when processing short firmware TLVs, potentially leading to memory corruption or crashes.","url":"https://insights.sbomify.com/CVE-2026-90399/"}