CVE-2026-23420

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-04-03. 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

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

wifi: wlcore: Fix a locking bug

Make sure that wl->mutex is locked before it is unlocked. This has been detected by the Clang thread-safety analyzer.

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
1%
KEV
Not listed

Published

April 3, 2026

Last Modified

July 24, 2026

Advisory Details (8)

Auto-updated Jul 25, 2026
No patch confirmed yet.
generic

wifi: wlcore: Fix a locking bug - kernel/git/stable/linux.git - Linux kernel stable tree

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

wifi: wlcore: Fix a locking bug - kernel/git/stable/linux.git - Linux kernel stable tree

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

wifi: wlcore: Fix a locking bug - kernel/git/stable/linux.git - Linux kernel stable tree

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

wifi: wlcore: Fix a locking bug - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7ab511003c5ae3bf5364d7699a2e3ab1db513680
generic

wifi: wlcore: Fix a locking bug - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/72c6df8f284b3a49812ce2ac136727ace70acc7c
generic

wifi: wlcore: Fix a locking bug - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5feeea59ed142e15c3284d0b1a364c6786bf3487
generic

wifi: wlcore: Fix a locking bug - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4ae8faf31b24c78653f4433298ee52813a56967a
generic

wifi: wlcore: Fix a locking bug - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1a1c28a08d74716f3f8e3a21c86b30d0ff13521a

Vendor Advisories for CVE-2026-23420(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(18)

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

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (53 versions)5.10.257-1
linux-6.16.1.106-3~deb11u1 ... 6.1.164-1~deb11u1 (16 versions)6.1.170-1~deb11u1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (48 versions)6.1.170-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (120 versions)6.19.8-1

Weakness Classification(1)

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

All Vendor Advisories

(24)

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 / 19× 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 168 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-23420?
CVE-2026-23420 is a medium vulnerability published on April 3, 2026. In the Linux kernel, the following vulnerability has been resolved: wifi: wlcore: Fix a locking bug Make sure that wl->mutex is locked before it is unlocked. This has been detected by the Clang thread-safety analyzer.
When was CVE-2026-23420 disclosed?
CVE-2026-23420 was first published in the National Vulnerability Database on April 3, 2026, with the most recent update on July 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-23420 actively exploited?
CVE-2026-23420 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.4% of all scored CVEs.
What is the CVSS score of CVE-2026-23420?
CVE-2026-23420 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-23420?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-23420, 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-23420

Explore →

Is Your Infrastructure Affected by CVE-2026-23420?

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