CVE-2022-49543

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2025-10-22. 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.3%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 the warning of dev_wake in mhi_pm_disable_transition()

When test device recovery with below command, it has warning in message as below. echo assert > /sys/kernel/debug/ath11k/wcn6855\ hw2.0/simulate_fw_crash echo assert > /sys/kernel/debug/ath11k/qca6390\ hw2.0/simulate_fw_crash

warning message: [ 1965.642121] ath11k_pci 0000:06:00.0: simulating firmware assert crash [ 1968.471364] ieee80211 phy0: Hardware restart was requested [ 1968.511305] ------------[ cut here ]------------ [ 1968.511368] WARNING: CPU: 3 PID: 1546 at drivers/bus/mhi/core/pm.c:505 mhi_pm_disable_transition+0xb37/0xda0 [mhi] [ 1968.511443] Modules linked in: ath11k_pci ath11k mac80211 libarc4 cfg80211 qmi_helpers qrtr_mhi mhi qrtr nvme nvme_core [ 1968.511563] CPU: 3 PID: 1546 Comm: kworker/u17:0 Kdump: loaded Tainted: G W 5.17.0-rc3-wt-ath+ #579 [ 1968.511629] Hardware name: Intel(R) Client Systems NUC8i7HVK/NUC8i7HVB, BIOS HNKBLi70.86A.0067.2021.0528.1339 05/28/2021 [ 1968.511704] Workqueue: mhi_hiprio_wq mhi_pm_st_worker [mhi] [ 1968.511787] RIP: 0010:mhi_pm_disable_transition+0xb37/0xda0 [mhi] [ 1968.511870] Code: a9 fe ff ff 4c 89 ff 44 89 04 24 e8 03 46 f6 e5 44 8b 04 24 41 83 f8 01 0f 84 21 fe ff ff e9 4c fd ff ff 0f 0b e9 af f8 ff ff <0f> 0b e9 5c f8 ff ff 48 89 df e8 da 9e ee e3 e9 12 fd ff ff 4c 89 [ 1968.511923] RSP: 0018:ffffc900024efbf0 EFLAGS: 00010286 [ 1968.511969] RAX: 00000000ffffffff RBX: ffff88811d241250 RCX: ffffffffc0176922 [ 1968.512014] RDX: 0000000000000000 RSI: 0000000000000004 RDI: ffff888118a90a24 [ 1968.512059] RBP: ffff888118a90800 R08: 0000000000000000 R09: ffff888118a90a27 [ 1968.512102] R10: ffffed1023152144 R11: 0000000000000001 R12: ffff888118a908ac [ 1968.512229] R13: ffff888118a90928 R14: dffffc0000000000 R15: ffff888118a90a24 [ 1968.512310] FS: 0000000000000000(0000) GS:ffff888234200000(0000) knlGS:0000000000000000 [ 1968.512405] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 1968.512493] CR2: 00007f5538f443a8 CR3: 000000016dc28001 CR4: 00000000003706e0 [ 1968.512587] Call Trace: [ 1968.512672] [ 1968.512751] ? _raw_spin_unlock_irq+0x1f/0x40 [ 1968.512859] mhi_pm_st_worker+0x3ac/0x790 [mhi] [ 1968.512959] ? mhi_pm_mission_mode_transition.isra.0+0x7d0/0x7d0 [mhi] [ 1968.513063] process_one_work+0x86a/0x1400 [ 1968.513184] ? pwq_dec_nr_in_flight+0x230/0x230 [ 1968.513312] ? move_linked_works+0x125/0x290 [ 1968.513416] worker_thread+0x6db/0xf60 [ 1968.513536] ? process_one_work+0x1400/0x1400 [ 1968.513627] kthread+0x241/0x2d0 [ 1968.513733] ? kthread_complete_and_exit+0x20/0x20 [ 1968.513821] ret_from_fork+0x22/0x30 [ 1968.513924]

Reason is mhi_deassert_dev_wake() from mhi_device_put() is called but mhi_assert_dev_wake() from __mhi_device_get_sync() is not called in progress of recovery. Commit 8e0559921f9a ("bus: mhi: core: Skip device wake in error or shutdown state") add check for the pm_state of mhi in __mhi_device_get_sync(), and the pm_state is not the normal state untill recovery is completed, so it leads the dev_wake is not 0 and above warning print in mhi_pm_disable_transition() while checking mhi_cntrl->dev_wake.

Add check in ath11k_pci_write32()/ath11k_pci_read32() to skip call mhi_device_put() if mhi_device_get_sync() does not really do wake, then the warning gone.

Tested-on: WCN6855 hw2.0 PCI WLAN.HSP.1.1-03003-QCAHSPSWPL_V1_V2_SILICONZ_LITE-2

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
29
EG Risk 29/100CISA SSVC

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%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.3%
EPSS %ILE
16th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

February 26, 2025

Last Modified

August 15, 2026

Advisory Details (3)

Auto-updated Aug 15, 2026
Patch available.
generic

ath11k: fix the warning of dev_wake in mhi_pm_disable_transition() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0d7a8a6204ea9271f1d0a8c66a9fd2f54d2e3cbc
generic

ath11k: fix the warning of dev_wake in mhi_pm_disable_transition() - kernel/git/stable/linux.git - Linux kernel stable tree

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

ath11k: fix the warning of dev_wake in mhi_pm_disable_transition() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5f18206cddae033c488e4879f198699092ca0524

Vendor Advisories for CVE-2022-49543(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.14 (fixes >=5.10.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.18.5-1: fixed in 5.18.5-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.18.5-1: fixed in 5.18.5-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.18.5-1: fixed in 5.18.5-1
—

Data Freshness Timeline

(refreshed 7× in last 7d / 22× 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 171 total refreshes for this CVE.

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2022-49543?
CVE-2022-49543 is a medium vulnerability published on February 26, 2025. In the Linux kernel, the following vulnerability has been resolved: ath11k: fix the warning of devwake in mhipmdisabletransition() When test device recovery with below command, it has warning in message as below. echo assert > /sys/kernel/debug/ath11k/wcn6855\ hw2.0/simulatefwcrash echo assert >…
When was CVE-2022-49543 disclosed?
CVE-2022-49543 was first published on February 26, 2025, with the most recent update on August 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-49543 actively exploited?
CVE-2022-49543 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (16th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-49543?
CVE-2022-49543 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2022-49543?
A fix for CVE-2022-49543 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2022-49543 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-49543

Explore →

Is Your Infrastructure Affected by CVE-2022-49543?

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

Book a Demo →Browse All CVEs