CVE-2026-23130: wifi: ath12k: fix dead lock while flushing management frames
In the Linux kernel, the following vulnerability has been resolved:
wifi: ath12k: fix dead lock while flushing management frames
Commit [1] converted the management transmission work item into a
wiphy work. Since a wiphy work can only run under wiphy lock
protection, a race condition happens in below scenario:
1. a management frame is queued for transmission.
2. ath12k_mac_op_flush() gets called to flush pending frames associated
with the hardware (i.e, vif being NULL). Then in ath12k_mac_flush()
the process waits for the transmission done.
3. Since wiphy lock has been taken by the flush process, the transmission
work item has no chance to run, hence the dead lock.
>From user view, this dead lock results in below issue:
wlp8s0: authenticate with xxxxxx (local address=xxxxxx)
wlp8s0: send auth to xxxxxx (try 1/3)
wlp8s0: authenticate with xxxxxx (local address=xxxxxx)
wlp8s0: send auth to xxxxxx (try 1/3)
wlp8s0: authenticated
wlp8s0: associate with xxxxxx (try 1/3)
wlp8s0: aborting association with xxxxxx by local choice (Reason: 3=DEAUTH_LEAVING)
ath12k_pci 0000:08:00.0: failed to flush mgmt transmit queue, mgmt pkts pending 1
The dead lock can be avoided by invoking wiphy_work_flush() to proactively
run the queued work item. Note actually it is already present in
ath12k_mac_op_flush(), however it does not protect the case where vif
being NULL. Hence move it ahead to cover this case as well.
Tested-on: WCN7850 hw2.0 PCI WLAN.HMT.1.1.c5-00302-QCAHMTSWPL_V1.0_V2.0_SILICONZ-1.115823.3
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue can deadlock the ath12k Wi-Fi driver while flushing management frames. For users, it may appear as repeated authentication or association failures and pending management packets. The source evidence points to availability and reliability impact, not data theft or privilege escalation.
Executive priority
Treat this as a targeted reliability fix for Linux Wi-Fi endpoints, not an emergency breach indicator. Prioritize fleets where wireless connectivity is operationally important or difficult to replace.
Technical view
The race occurs after management transmission work was converted to wiphy work. ath12k_mac_op_flush() can hold the wiphy lock while waiting for transmission completion, preventing the queued work item from running. The fix moves wiphy_work_flush() earlier so it also covers the vif == NULL hardware flush case.
Likely exposure
Likely exposure is Linux systems using affected kernel builds with the ath12k Wi-Fi driver. The source lists Linux as the affected product and references stable kernel fixes. Version details in the source bundle are incomplete and should be verified against vendor kernel packages.
Exploitation context
No active exploitation is reported in KEV or the provided sources. The public description shows a driver deadlock during wireless management-frame handling. The sources do not establish remote exploitability, privilege escalation, or confidentiality impact.
Researcher notes
Evidence is limited to the CVE description and two Linux stable commit references. The issue is a locking-order deadlock in ath12k management-frame flushing. No CVSS, CWE, exploit evidence, or distribution-specific affected package list is provided.
Mitigation direction
Update to a Linux kernel package that includes the referenced stable fixes.
Check Linux distribution advisories for backported ath12k fixes.
Prioritize Wi-Fi-dependent endpoints using ath12k-supported hardware.
Use wired networking or alternate Wi-Fi hardware where update timing is constrained.
Validation and detection
Inventory Linux kernel versions and systems using the ath12k driver.
Confirm whether vendor kernel changelogs include the referenced stable commits.
Review logs for failed management transmit queue flush messages.
Test Wi-Fi authentication and association after applying the kernel update.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2026-23130 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
0ADP providers
3Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Feb 14, 2026, 15:09 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.