CVE-2022-50700

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2025-12-24. the CNA's CVSS baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

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

wifi: ath10k: Delay the unmapping of the buffer

On WCN3990, we are seeing a rare scenario where copy engine hardware is sending a copy complete interrupt to the host driver while still processing the buffer that the driver has sent, this is leading into an SMMU fault triggering kernel panic. This is happening on copy engine channel 3 (CE3) where the driver normally enqueues WMI commands to the firmware. Upon receiving a copy complete interrupt, host driver will immediately unmap and frees the buffer presuming that hardware has processed the buffer. In the issue case, upon receiving copy complete interrupt, host driver will unmap and free the buffer but since hardware is still accessing the buffer (which in this case got unmapped in parallel), SMMU hardware will trigger an SMMU fault resulting in a kernel panic.

In order to avoid this, as a work around, add a delay before unmapping the copy engine source DMA buffer. This is conditionally done for WCN3990 and only for the CE3 channel where issue is seen.

Below is the crash signature:

wifi smmu error: kernel: [ 10.120965] arm-smmu 15000000.iommu: Unhandled context fault: fsr=0x402, iova=0x7fdfd8ac0, fsynr=0x500003,cbfrsynra=0xc1, cb=6 arm-smmu 15000000.iommu: Unhandled context fault:fsr=0x402, iova=0x7fe06fdc0, fsynr=0x710003, cbfrsynra=0xc1, cb=6 qcom-q6v5-mss 4080000.remoteproc: fatal error received: err_qdi.c:1040:EF:wlan_process:0x1:WLAN RT:0x2091: cmnos_thread.c:3998:Asserted in copy_engine.c:AXI_ERROR_DETECTED:2149 remoteproc remoteproc0: crash detected in 4080000.remoteproc: type fatal error <3> remoteproc remoteproc0: handling crash #1 in 4080000.remoteproc

pc : __arm_lpae_unmap+0x500/0x514 lr : __arm_lpae_unmap+0x4bc/0x514 sp : ffffffc011ffb530 x29: ffffffc011ffb590 x28: 0000000000000000 x27: 0000000000000000 x26: 0000000000000004 x25: 0000000000000003 x24: ffffffc011ffb890 x23: ffffffa762ef9be0 x22: ffffffa77244ef00 x21: 0000000000000009 x20: 00000007fff7c000 x19: 0000000000000003 x18: 0000000000000000 x17: 0000000000000004 x16: ffffffd7a357d9f0 x15: 0000000000000000 x14: 00fd5d4fa7ffffff x13: 000000000000000e x12: 0000000000000000 x11: 00000000ffffffff x10: 00000000fffffe00 x9 : 000000000000017c x8 : 000000000000000c x7 : 0000000000000000 x6 : ffffffa762ef9000 x5 : 0000000000000003 x4 : 0000000000000004 x3 : 0000000000001000 x2 : 00000007fff7c000 x1 : ffffffc011ffb890 x0 : 0000000000000000 Call trace: __arm_lpae_unmap+0x500/0x514 __arm_lpae_unmap+0x4bc/0x514 __arm_lpae_unmap+0x4bc/0x514 arm_lpae_unmap_pages+0x78/0xa4 arm_smmu_unmap_pages+0x78/0x104 __iommu_unmap+0xc8/0x1e4 iommu_unmap_fast+0x38/0x48 __iommu_dma_unmap+0x84/0x104 iommu_dma_free+0x34/0x50 dma_free_attrs+0xa4/0xd0 ath10k_htt_rx_free+0xc4/0xf4 [ath10k_core] ath10k_core_stop+0x64/0x7c [ath10k_core] ath10k_halt+0x11c/0x180 [ath10k_core] ath10k_stop+0x54/0x94 [ath10k_core] drv_stop+0x48/0x1c8 [mac80211] ieee80211_do_open+0x638/0x77c [mac80211] ieee80211_open+0x48/0x5c [mac80211] __dev_open+0xb4/0x174 __dev_change_flags+0xc4/0x1dc dev_change_flags+0x3c/0x7c devinet_ioctl+0x2b4/0x580 inet_ioctl+0xb0/0x1b4 sock_do_ioctl+0x4c/0x16c compat_ifreq_ioctl+0x1cc/0x35c compat_sock_ioctl+0x110/0x2ac __arm64_compat_sys_ioctl+0xf4/0x3e0 el0_svc_common+0xb4/0x17c el0_svc_compat_handler+0x2c/0x58 el0_svc_compat+0x8/0x2c

Tested-on: WCN3990 hw1.0 SNOC WLAN.HL.2.0-01387-QCAHLSWMTPLZ-1

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
38(Track)
EG Risk 38/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
Severity75% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
16%
KEV
Not listed

Published

December 24, 2025

Last Modified

August 5, 2026

Advisory Details (3)

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

wifi: ath10k: Delay the unmapping of the buffer - kernel/git/stable/linux.git - Linux kernel stable tree

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

wifi: ath10k: Delay the unmapping of the buffer - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/79a124b588aadb5a22695542778de14366ff3219
generic

wifi: ath10k: Delay the unmapping of the buffer - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c4bedc3cda09d896c92adcdb6b62aa93b0c47a8a

Vendor Advisories for CVE-2022-50700(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 / EcosystemFixed in / PatchReleasedSource
redhatkernel-0:4.18.0-513.5.1.el8_92023-11-14redhat
redhatkernel-0:5.14.0-362.8.1.el9_32023-11-07redhat
linuxKernel @ 6.0.16—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 rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (498 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux—6.1.4-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux—6.1.4-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux—6.1.4-1—

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2022-50700?
CVE-2022-50700 is a high vulnerability published on December 24, 2025. In the Linux kernel, the following vulnerability has been resolved: wifi: ath10k: Delay the unmapping of the buffer On WCN3990, we are seeing a rare scenario where copy engine hardware is sending a copy complete interrupt to the host driver while still processing the buffer that the driver has…
When was CVE-2022-50700 disclosed?
CVE-2022-50700 was first published in the National Vulnerability Database on December 24, 2025, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-50700 actively exploited?
CVE-2022-50700 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 83.9% of all scored CVEs.
What is the CVSS score of CVE-2022-50700?
CVE-2022-50700 has a CVSS v4.0 base score of 7.5 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2022-50700?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-50700, 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-2022-50700

Explore →

Is Your Infrastructure Affected by CVE-2022-50700?

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

Start Free Scan →Browse All CVEs