CVE-2022-49123

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2022-54488 (ENISA EUVD) · GHSA-26p5-hwvm-hf8m (GitHub Security Advisories)Source: ENISA EUVD

5.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

ath11k: Fix frames flush failure caused by deadlock

We are seeing below warnings:

kernel: [25393.301506] ath11k_pci 0000:01:00.0: failed to flush mgmt transmit queue 0 kernel: [25398.421509] ath11k_pci 0000:01:00.0: failed to flush mgmt transmit queue 0 kernel: [25398.421831] ath11k_pci 0000:01:00.0: dropping mgmt frame for vdev 0, is_started 0

this means ath11k fails to flush mgmt. frames because wmi_mgmt_tx_work has no chance to run in 5 seconds.

By setting /proc/sys/kernel/hung_task_timeout_secs to 20 and increasing ATH11K_FLUSH_TIMEOUT to 50 we get below warnings:

kernel: [ 120.763160] INFO: task wpa_supplicant:924 blocked for more than 20 seconds. kernel: [ 120.763169] Not tainted 5.10.90 #12 kernel: [ 120.763177] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. kernel: [ 120.763186] task:wpa_supplicant state:D stack: 0 pid: 924 ppid: 1 flags:0x000043a0 kernel: [ 120.763201] Call Trace: kernel: [ 120.763214] __schedule+0x785/0x12fa kernel: [ 120.763224] ? lockdep_hardirqs_on_prepare+0xe2/0x1bb kernel: [ 120.763242] schedule+0x7e/0xa1 kernel: [ 120.763253] schedule_timeout+0x98/0xfe kernel: [ 120.763266] ? run_local_timers+0x4a/0x4a kernel: [ 120.763291] ath11k_mac_flush_tx_complete+0x197/0x2b1 [ath11k 13c3a9bf37790f4ac8103b3decf7ab4008ac314a] kernel: [ 120.763306] ? init_wait_entry+0x2e/0x2e kernel: [ 120.763343] __ieee80211_flush_queues+0x167/0x21f [mac80211 335da900954f1c5ea7f1613d92088ce83342042c] kernel: [ 120.763378] __ieee80211_recalc_idle+0x105/0x125 [mac80211 335da900954f1c5ea7f1613d92088ce83342042c] kernel: [ 120.763411] ieee80211_recalc_idle+0x14/0x27 [mac80211 335da900954f1c5ea7f1613d92088ce83342042c] kernel: [ 120.763441] ieee80211_free_chanctx+0x77/0xa2 [mac80211 335da900954f1c5ea7f1613d92088ce83342042c] kernel: [ 120.763473] __ieee80211_vif_release_channel+0x100/0x131 [mac80211 335da900954f1c5ea7f1613d92088ce83342042c] kernel: [ 120.763540] ieee80211_vif_release_channel+0x66/0x81 [mac80211 335da900954f1c5ea7f1613d92088ce83342042c] kernel: [ 120.763572] ieee80211_destroy_auth_data+0xa3/0xe6 [mac80211 335da900954f1c5ea7f1613d92088ce83342042c] kernel: [ 120.763612] ieee80211_mgd_deauth+0x178/0x29b [mac80211 335da900954f1c5ea7f1613d92088ce83342042c] kernel: [ 120.763654] cfg80211_mlme_deauth+0x1a8/0x22c [cfg80211 8945aa5bc2af5f6972336665d8ad6f9c191ad5be] kernel: [ 120.763697] nl80211_deauthenticate+0xfa/0x123 [cfg80211 8945aa5bc2af5f6972336665d8ad6f9c191ad5be] kernel: [ 120.763715] genl_rcv_msg+0x392/0x3c2 kernel: [ 120.763750] ? nl80211_associate+0x432/0x432 [cfg80211 8945aa5bc2af5f6972336665d8ad6f9c191ad5be] kernel: [ 120.763782] ? nl80211_associate+0x432/0x432 [cfg80211 8945aa5bc2af5f6972336665d8ad6f9c191ad5be] kernel: [ 120.763802] ? genl_rcv+0x36/0x36 kernel: [ 120.763814] netlink_rcv_skb+0x89/0xf7 kernel: [ 120.763829] genl_rcv+0x28/0x36 kernel: [ 120.763840] netlink_unicast+0x179/0x24b kernel: [ 120.763854] netlink_sendmsg+0x393/0x401 kernel: [ 120.763872] sock_sendmsg+0x72/0x76 kernel: [ 120.763886] ____sys_sendmsg+0x170/0x1e6 kernel: [ 120.763897] ? copy_msghdr_from_user+0x7a/0xa2 kernel: [ 120.763914] ___sys_sendmsg+0x95/0xd1 kernel: [ 120.763940] __sys_sendmsg+0x85/0xbf kernel: [ 120.763956] do_syscall_64+0x43/0x55 kernel: [ 120.763966] entry_SYSCALL_64_after_hwframe+0x44/0xa9 kernel: [ 120.763977] RIP: 0033:0x79089f3fcc83 kernel: [ 120.763986] RSP: 002b:00007ffe604f0508 EFLAGS: 00000246 ORIG_RAX: 000000000000002e kernel: [ 120.763997] RAX: ffffffffffffffda RBX: 000059b40e987690 RCX: 000079089f3fcc83 kernel: [ 120.764006] RDX: 0000000000000000 RSI: 00007ffe604f0558 RDI: 0000000000000009 kernel: [ 120.764014] RBP: 00007ffe604f0540 R08: 0000000000000004 R09: 0000000000400000 kernel: [ 120.764023] R10: 00007ffe604f0638 R11: 0000000000000246 R12: 000059b40ea04980 kernel: [ 120.764032] R13: 00007ffe604 ---truncated---

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
6th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-25). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

February 26, 2025

Last Modified

August 13, 2026

Advisory Details (2)

Auto-updated Aug 13, 2026
Patch available.
Web page

ath11k: Fix frames flush failure caused by deadlock - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/261b07519518bd14cb168b287b17e1d195f8d0c8
Web page

ath11k: Fix frames flush failure caused by deadlock - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/33e723dc054edfc94da90eecca3b72cb424ce4a3

Vendor Advisories for CVE-2022-49123(3)

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

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatkernel-0:5.14.0-162.6.1.el9_12022-11-15redhat
redhatkernel-0:4.18.0-425.3.1.el82022-11-08redhat
linuxKernel @ 5.17.3 (fixes >=5.17.0)—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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.17.3-1: fixed in 5.17.3-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.17.3-1: fixed in 5.17.3-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.17.3-1: fixed in 5.17.3-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 38× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 98 of 195 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 2 repeat rows among the latest 100 are merged into the row they repeat. The 97 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2022-49123?
CVE-2022-49123 is a medium-severity vulnerability; its CVE record was published on February 26, 2025. In the Linux kernel, the following vulnerability has been resolved: ath11k: Fix frames flush failure caused by deadlock We are seeing below warnings: kernel: [25393.301506] ath11k_pci 0000:01:00.0: failed to flush mgmt transmit queue 0 kernel: [25398.421509] ath11k_pci 0000:01:00.0: failed to flush…
When was the CVE record for CVE-2022-49123 published?
The CVE record for CVE-2022-49123 was published on February 26, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 13, 2026; the record at its source may have been updated since.
Is CVE-2022-49123 actively exploited?
CVE-2022-49123 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (6th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-49123?
CVE-2022-49123 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2022-49123?
A fix for CVE-2022-49123 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2022-49123 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-49123

Explore →

Is Your Infrastructure Affected by CVE-2022-49123?

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

Book a Demo →Browse All CVEs