CVE-2026-23130

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-02-14. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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:

  • a management frame is queued for transmission.
  • 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.
  • 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

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
0%
KEV
Not listed

Published

February 14, 2026

Last Modified

June 17, 2026

Advisory Details (2)

Auto-updated Aug 24, 2026
No patch confirmed yet.
generic

wifi: ath12k: fix dead lock while flushing management frames - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f88e9fc30a261d63946ddc6cc6a33405e6aa27c3
generic

wifi: ath12k: fix dead lock while flushing management frames - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/06ac2aa13f701a0296e92f5f54ae24224d426b28

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 6.18.8—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.18~rc7-1~exp1 (96 versions)6.18.8-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(5)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 4× in last 7d / 9× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 113 total refreshes for this CVE.

  1. 2026-09-18 21:42 UTCOSV refresh
  2. 2026-09-16 14:07 UTCEPSS rescore
  3. 2026-09-16 05:15 UTCEPSS rescore
  4. 2026-09-13 16:47 UTCEPSS rescore
  5. 2026-09-11 14:52 UTCEPSS rescore
  6. 2026-09-10 09:34 UTCEPSS rescore
  7. 2026-09-04 05:06 UTCEPSS rescore
  8. 2026-08-31 00:23 UTCOSV refresh
  9. 2026-08-25 13:48 UTCEPSS rescore
  10. 2026-08-20 22:55 UTCEPSS rescore
  11. 2026-08-19 17:03 UTCEPSS rescore
  12. 2026-08-17 13:47 UTCEPSS rescore
  13. 2026-08-16 14:56 UTCEPSS rescore
  14. 2026-08-14 10:05 UTCVendor advisory
  15. 2026-08-14 10:05 UTCGHSA enrichment
  16. 2026-08-13 02:23 UTCVendor advisory
  17. 2026-08-13 02:23 UTCGHSA enrichment
  18. 2026-08-11 07:55 UTCVendor advisory
  19. 2026-08-11 07:55 UTCGHSA enrichment
  20. 2026-08-09 14:39 UTCVendor advisory
  21. 2026-08-09 14:39 UTCGHSA enrichment
  22. 2026-08-07 21:56 UTCVendor advisory
  23. 2026-08-07 21:56 UTCGHSA enrichment
  24. 2026-08-06 03:48 UTCEG score recompute
  25. 2026-08-06 03:48 UTCGHSA enrichment
Show 75 more
  1. 2026-08-05 19:17 UTCEPSS rescore
  2. 2026-08-04 10:38 UTCEPSS rescore
  3. 2026-08-02 20:37 UTCEG score recompute
  4. 2026-08-02 20:37 UTCVendor advisory
  5. 2026-08-02 20:37 UTCGHSA enrichment
  6. 2026-08-02 02:26 UTCEPSS rescore
  7. 2026-08-01 04:15 UTCEPSS rescore
  8. 2026-07-27 14:13 UTCEPSS rescore
  9. 2026-07-26 14:54 UTCEPSS rescore
  10. 2026-07-26 14:54 UTCEPSS rescore
  11. 2026-07-24 14:17 UTCEPSS rescore
  12. 2026-07-23 03:06 UTCEG score recompute
  13. 2026-07-21 15:24 UTCEPSS rescore
  14. 2026-07-21 15:24 UTCEPSS rescore
  15. 2026-07-18 10:04 UTCEPSS rescore
  16. 2026-07-18 10:04 UTCEPSS rescore
  17. 2026-07-17 14:29 UTCOSV refresh
  18. 2026-07-16 17:03 UTCEPSS rescore
  19. 2026-07-16 17:03 UTCEPSS rescore
  20. 2026-07-15 16:57 UTCEPSS rescore
  21. 2026-07-15 16:57 UTCEPSS rescore
  22. 2026-07-13 22:30 UTCEPSS rescore
  23. 2026-07-13 06:13 UTCEPSS rescore
  24. 2026-07-13 06:13 UTCEPSS rescore
  25. 2026-07-08 15:15 UTCEPSS rescore
  26. 2026-07-08 15:15 UTCEPSS rescore
  27. 2026-07-07 13:46 UTCEPSS rescore
  28. 2026-07-06 16:27 UTCEPSS rescore
  29. 2026-07-06 16:27 UTCEPSS rescore
  30. 2026-07-06 02:23 UTCEPSS rescore
  31. 2026-07-06 02:23 UTCEPSS rescore
  32. 2026-07-05 02:30 UTCEPSS rescore
  33. 2026-06-29 13:02 UTCOSV refresh
  34. 2026-06-28 14:07 UTCEPSS rescore
  35. 2026-06-28 14:07 UTCEPSS rescore
  36. 2026-06-28 04:56 UTCEPSS rescore
  37. 2026-06-28 04:56 UTCEPSS rescore
  38. 2026-06-24 14:05 UTCEPSS rescore
  39. 2026-06-24 14:05 UTCEPSS rescore
  40. 2026-06-23 21:33 UTCEPSS rescore
  41. 2026-06-23 21:32 UTCEPSS rescore
  42. 2026-06-22 14:25 UTCEPSS rescore
  43. 2026-06-22 14:25 UTCEPSS rescore
  44. 2026-06-21 01:59 UTCEPSS rescore
  45. 2026-06-21 01:59 UTCEPSS rescore
  46. 2026-06-19 19:25 UTCEPSS rescore
  47. 2026-06-19 19:25 UTCEPSS rescore
  48. 2026-06-18 17:52 UTCEPSS rescore
  49. 2026-06-17 17:53 UTCEPSS rescore
  50. 2026-06-17 17:53 UTCEPSS rescore
  51. 2026-06-15 17:48 UTCEPSS rescore
  52. 2026-06-14 23:18 UTCEPSS rescore
  53. 2026-06-13 23:00 UTCEPSS rescore
  54. 2026-06-13 23:00 UTCEPSS rescore
  55. 2026-06-12 23:12 UTCEPSS rescore
  56. 2026-06-12 03:41 UTCGHSA enrichment
  57. 2026-06-11 14:00 UTCEPSS rescore
  58. 2026-06-10 22:18 UTCEPSS rescore
  59. 2026-06-10 13:22 UTCEPSS rescore
  60. 2026-06-10 02:10 UTCGHSA enrichment
  61. 2026-06-08 14:17 UTCEPSS rescore
  62. 2026-06-08 14:17 UTCEPSS rescore
  63. 2026-06-07 18:03 UTCGHSA enrichment
  64. 2026-06-07 15:25 UTCEPSS rescore
  65. 2026-06-07 15:24 UTCEPSS rescore
  66. 2026-06-06 13:47 UTCEPSS rescore
  67. 2026-06-06 13:47 UTCEPSS rescore
  68. 2026-06-06 13:47 UTCEPSS rescore
  69. 2026-06-05 22:47 UTCEPSS rescore
  70. 2026-06-05 06:10 UTCEPSS rescore
  71. 2026-06-05 06:10 UTCEPSS rescore
  72. 2026-06-04 13:12 UTCEPSS rescore
  73. 2026-06-04 13:12 UTCEPSS rescore
  74. 2026-06-04 13:12 UTCEPSS rescore
  75. 2026-06-02 20:13 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-23130?
CVE-2026-23130 is a medium vulnerability published on February 14, 2026. 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…
When was CVE-2026-23130 disclosed?
CVE-2026-23130 was first published in the National Vulnerability Database on February 14, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-23130 actively exploited?
CVE-2026-23130 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 99.7% of all scored CVEs.
What is the CVSS score of CVE-2026-23130?
CVE-2026-23130 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-23130?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-23130, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-23130

Explore →

Is Your Infrastructure Affected by CVE-2026-23130?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs