# wifi: ath12k: fix dead lock while flushing management frames

CVE record · `CVE-2026-23130`

- **Identifiers:** `CVE-2026-23130`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 14 Feb 2026
- **Updated:** 5 Nov 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 14 Feb 2026, 15:09 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `56dcbf0b520796e26b2bbe5686bdd305ad924954 to before 06ac2aa13f701a0296e92f5f54ae24224d426b28` (git)
  - affected: `56dcbf0b520796e26b2bbe5686bdd305ad924954 to before f88e9fc30a261d63946ddc6cc6a33405e6aa27c3` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `6.14`
  - unaffected: `before 6.14` (semver)
  - unaffected: `6.18.8 to 6.18.*, inclusive` (semver)
  - unaffected: `6.19 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The ath12k Wi-Fi driver in the Linux kernel, affected from 6.14, can deadlock while flushing pending management frames, for example when a wireless association is aborted. The source gives few details on what an attacker would need, and the deadlock stalls the driver. Upgrade to Linux kernel 6.18.8 or later in the 6.18 series, or to 6.19 or later.

Written 17 Nov 2026.

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0009, the 1st percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 14 Feb 2026, 15:09 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2026-23130)
- 14 Feb 2026, 15:16 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-23130)

## Sources

- [CVE List: CVE-2026-23130](https://www.cve.org/CVERecord?id=CVE-2026-23130)
- [NVD: CVE-2026-23130](https://nvd.nist.gov/vuln/detail/CVE-2026-23130)

### References from the CNA

- <https://git.kernel.org/stable/c/06ac2aa13f701a0296e92f5f54ae24224d426b28>
- <https://git.kernel.org/stable/c/f88e9fc30a261d63946ddc6cc6a33405e6aa27c3>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2026-23130>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2026-23130/>. Everything for agents: <https://agentprime.io/llms.txt>.
