CVE-2022-50701

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
7.1EG
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.1Exploit: None knownExposed: 0

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.1(medium)
EG Risk
37(Track)
EG Risk 37/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
Severity71% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
4%
KEV
Not listed

Published

December 24, 2025

Last Modified

August 5, 2026

Advisory Details (3)

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

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
generic

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
generic

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 / 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.1.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

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux—6.1.20-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux—6.1.20-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux—6.1.20-1—

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2022-50701?
CVE-2022-50701 is a high vulnerability 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 CVE-2022-50701 disclosed?
CVE-2022-50701 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-50701 actively exploited?
CVE-2022-50701 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 95.9% of all scored CVEs.
What is the CVSS score of CVE-2022-50701?
CVE-2022-50701 has a CVSS v4.0 base score of 7.1 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2022-50701?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-50701, 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-50701

Explore →

Is Your Infrastructure Affected by CVE-2022-50701?

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

Start Free Scan →Browse All CVEs