CVE-2022-50701

HIGHPre-NVD 7.17.1
EchelonGraph scoreMEDIUM confidence

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

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2025-205176 (ENISA EUVD) · GHSA-9vm9-fqq4-5wqv (GitHub Security Advisories)Source: ENISA EUVD

7.1EG
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.1%CVSS: 7.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

wifi: mt76: mt7921s: fix slab-out-of-bounds access in sdio host

SDIO may need addtional 511 bytes to align bus operation. If the tailroom of this skb is not big enough, we would access invalid memory region. For low level operation, increase skb size to keep valid memory access in SDIO host.

Error message: [69.951] BUG: KASAN: slab-out-of-bounds in sg_copy_buffer+0xe9/0x1a0 [69.951] Read of size 64 at addr ffff88811c9cf000 by task kworker/u16:7/451 [69.951] CPU: 4 PID: 451 Comm: kworker/u16:7 Tainted: G W OE 6.1.0-rc5 #1 [69.951] Workqueue: kvub300c vub300_cmndwork_thread [vub300] [69.951] Call Trace: [69.951] [69.952] dump_stack_lvl+0x49/0x63 [69.952] print_report+0x171/0x4a8 [69.952] kasan_report+0xb4/0x130 [69.952] kasan_check_range+0x149/0x1e0 [69.952] memcpy+0x24/0x70 [69.952] sg_copy_buffer+0xe9/0x1a0 [69.952] sg_copy_to_buffer+0x12/0x20 [69.952] __command_write_data.isra.0+0x23c/0xbf0 [vub300] [69.952] vub300_cmndwork_thread+0x17f3/0x58b0 [vub300] [69.952] process_one_work+0x7ee/0x1320 [69.952] worker_thread+0x53c/0x1240 [69.952] kthread+0x2b8/0x370 [69.952] ret_from_fork+0x1f/0x30 [69.952]

[69.952] Allocated by task 854: [69.952] kasan_save_stack+0x26/0x50 [69.952] kasan_set_track+0x25/0x30 [69.952] kasan_save_alloc_info+0x1b/0x30 [69.952] __kasan_kmalloc+0x87/0xa0 [69.952] __kmalloc_node_track_caller+0x63/0x150 [69.952] kmalloc_reserve+0x31/0xd0 [69.952] __alloc_skb+0xfc/0x2b0 [69.952] __mt76_mcu_msg_alloc+0xbf/0x230 [mt76] [69.952] mt76_mcu_send_and_get_msg+0xab/0x110 [mt76] [69.952] __mt76_mcu_send_firmware.cold+0x94/0x15d [mt76] [69.952] mt76_connac_mcu_send_ram_firmware+0x415/0x54d [mt76_connac_lib] [69.952] mt76_connac2_load_ram.cold+0x118/0x4bc [mt76_connac_lib] [69.952] mt7921_run_firmware.cold+0x2e9/0x405 [mt7921_common] [69.952] mt7921s_mcu_init+0x45/0x80 [mt7921s] [69.953] mt7921_init_work+0xe1/0x2a0 [mt7921_common] [69.953] process_one_work+0x7ee/0x1320 [69.953] worker_thread+0x53c/0x1240 [69.953] kthread+0x2b8/0x370 [69.953] ret_from_fork+0x1f/0x30 [69.953] The buggy address belongs to the object at ffff88811c9ce800 which belongs to the cache kmalloc-2k of size 2048 [69.953] The buggy address is located 0 bytes to the right of 2048-byte region [ffff88811c9ce800, ffff88811c9cf000)

[69.953] Memory state around the buggy address: [69.953] ffff88811c9cef00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [69.953] ffff88811c9cef80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [69.953] >ffff88811c9cf000: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc [69.953] ^ [69.953] ffff88811c9cf080: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc [69.953] ffff88811c9cf100: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc

CVSS v3
7.1
EG Score
7.1HIGHmedium confidence
EG Risk
32
EG Risk 32/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)
Severity71% × 45%
Impact severity (EG Severity): CVSS 7.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 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.1%
EPSS %ILE
4th
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.1): severity, escalated by confirmed exploitation. This CVE's 7.1 is its impact severity (EG Severity), not escalated.

EG Severity
7.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-09). 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

December 24, 2025

Last Modified

November 10, 2026

Advisory Details (3)

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

wifi: mt76: mt7921s: fix slab-out-of-bounds access in sdio host - kernel/git/stable/linux.git - Linux kernel stable tree

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

wifi: mt76: mt7921s: fix slab-out-of-bounds access in sdio host - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0b358e36433d2c46a65488a146bf8b4623fc5bbb
Web page

wifi: mt76: mt7921s: fix slab-out-of-bounds access in sdio host - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8b5174a7f25d03df0ffa171ff86de383a89e8e89

Vendor Advisories for CVE-2022-50701(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.1.16 (fixes >=5.16.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

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.1.20-1: fixed in 6.1.20-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.1.20-1: fixed in 6.1.20-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.1.20-1: fixed in 6.1.20-1
—

Data Freshness Timeline

(refreshed 9× in last 7d / 37× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 273 rows 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. None are among the latest 100 rows. The 173 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2022-50701?
CVE-2022-50701 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: mt76: mt7921s: fix slab-out-of-bounds access in sdio host SDIO may need addtional 511 bytes to align bus operation. If the tailroom of this skb is not big enough, we would access invalid memory region. For low level…
When was the CVE record for CVE-2022-50701 published?
The CVE record for CVE-2022-50701 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 November 10, 2026; the record at its source may have been updated since.
Is CVE-2022-50701 actively exploited?
CVE-2022-50701 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (4th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-50701?
CVE-2022-50701 has a CVSS base score of 7.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2022-50701?
A fix for CVE-2022-50701 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2022-50701 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-50701

Explore →

Is Your Infrastructure Affected by CVE-2022-50701?

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

Book a Demo →Browse All CVEs