{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-74367 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-74367 is a high-severity vulnerability in Linux, published on 15 Aug 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-74367 and fix it if it is affected.\n\nWhat it is: CVE-2026-74367 is a high-severity vulnerability in Linux, published on 15 Aug 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-74367 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-74367/ (Markdown: https://insights.sbomify.com/CVE-2026-74367/index.md)","id":"CVE-2026-74367","markdown":"https://insights.sbomify.com/CVE-2026-74367/index.md","name":"CVE-2026-74367","record":{"aliases":["BELL-CVE-2026-74367","DEBIAN-CVE-2026-74367","GHSA-cww3-p2pw-g5j8","UBUNTU-CVE-2026-74367"],"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":"low_privilege","summary":"Inconsistent state in ath12k WiFi driver error paths can lead to system instability or denial of service.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/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 inconsistent arvif state in vdev_create error paths\n\nath12k_mac_vdev_create() has three error path issues that leave arvif\nin an inconsistent state:\n\n1. When ath12k_wmi_vdev_create() fails, the function returns directly\n   without clearing arvif-\u003ear, which was already set before the WMI\n   call. Subsequent code checking arvif-\u003ear to determine vdev readiness\n   will see a non-NULL value despite no vdev existing in firmware.\n\n2. When ath12k_wmi_send_peer_delete_cmd() fails in err_peer_del, the\n   code jumped to err: skipping the DP peer cleanup and vdev rollback,\n   leaving num_created_vdevs, vdev maps and arvif list membership live.\n\n3. When ath12k_wait_for_peer_delete_done() fails, the code jumped to\n   err_vdev_del: skipping the DP peer cleanup.\n\nFix by changing the ath12k_wmi_vdev_create() failure to goto err instead\nof returning directly, routing both err_peer_del failure paths through\nerr_dp_peer_del: for proper DP peer and vdev rollback, and consolidating\nthe arvif state cleanup at err:.\n\nTested-on: WCN7850 hw2.0 PCI WLAN.HMT.1.1.c5-00302-QCAHMTSWPL_V1.0_V2.0_SILICONZ-1.115823.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 inconsistent arvif state in vdev_create error paths","id":"CVE-2026-74367","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"wifi: ath12k: fix memory leak in ath12k_wifi7_dp_rx_h_verify_tkip_mic()","id":"CVE-2026-74368"},"packages":[],"prev":{"headline":"wifi: ath12k: fix NULL deref in change_sta_links for unready link","id":"CVE-2026-74366"},"products":["Linux"],"published":"2026-08-15","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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-16","vendors":["Linux"]},"summary":"Inconsistent state in ath12k WiFi driver error paths can lead to system instability or denial of service.","url":"https://insights.sbomify.com/CVE-2026-74367/"}