CVE-2022-50700

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2025-12-24. A secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week

Also known asEUVD-2025-205178 (ENISA EUVD) · GHSA-7rvm-m8gm-c79m (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 7.5Exploit: None knownExposed services: Not assessed

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.5HIGHmedium confidence
EG Risk
34
EG Risk 34/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)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.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 low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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.3%
EPSS %ILE
16th
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 (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-30). 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 low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 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 low or medium mission impact; Track* at high (mission-essential systems).

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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)14 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 total (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

December 24, 2025

Last Modified

October 15, 2026

Advisory Details (3)

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

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

https://git.kernel.org/stable/c/acd4324e5f1f11351630234297f95076f0ac9a2f
Web page

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

https://git.kernel.org/stable/c/79a124b588aadb5a22695542778de14366ff3219
Web page

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 / EcosystemFix (by version range) / 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 (fixes >=4.18.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 (498 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.1.4-1: fixed in 6.1.4-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.1.4-1: fixed in 6.1.4-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.1.4-1: fixed in 6.1.4-1
—

Data Freshness Timeline

(refreshed 10× in last 7d / 45× 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 99 of 256 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. 1 repeat row among the latest 100 is merged into the row it repeats. The 157 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2022-50700?
CVE-2022-50700 is a high-severity vulnerability; its CVE record was 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 the CVE record for CVE-2022-50700 published?
The CVE record for CVE-2022-50700 was published on December 24, 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 October 15, 2026; the record at its source may have been updated since.
Is CVE-2022-50700 actively exploited?
CVE-2022-50700 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-50700?
CVE-2022-50700 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2022-50700?
A fix for CVE-2022-50700 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2022-50700 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-50700

Explore →

Is Your Infrastructure Affected by CVE-2022-50700?

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

Book a Demo →Browse All CVEs