CVE-2022-50726

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

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

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

A fix is available — apply it.

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

net/mlx5: Fix possible use-after-free in async command interface

mlx5_cmd_cleanup_async_ctx should return only after all its callback handlers were completed. Before this patch, the below race between mlx5_cmd_cleanup_async_ctx and mlx5_cmd_exec_cb_handler was possible and lead to a use-after-free:

  • mlx5_cmd_cleanup_async_ctx is called while num_inflight is 2 (i.e.
elevated by 1, a single inflight callback).
  • mlx5_cmd_cleanup_async_ctx decreases num_inflight to 1.
  • mlx5_cmd_exec_cb_handler is called, decreases num_inflight to 0 and
is about to call wake_up().
  • mlx5_cmd_cleanup_async_ctx calls wait_event, which returns
immediately as the condition (num_inflight == 0) holds.
  • mlx5_cmd_cleanup_async_ctx returns.
  • The caller of mlx5_cmd_cleanup_async_ctx frees the mlx5_async_ctx
object.
  • mlx5_cmd_exec_cb_handler goes on and calls wake_up() on the freed
object.

Fix it by syncing using a completion object. Mark it completed when num_inflight reaches 0.

Trace:

BUG: KASAN: use-after-free in do_raw_spin_lock+0x23d/0x270 Read of size 4 at addr ffff888139cd12f4 by task swapper/5/0

CPU: 5 PID: 0 Comm: swapper/5 Not tainted 6.0.0-rc3_for_upstream_debug_2022_08_30_13_10 #1 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 Call Trace: dump_stack_lvl+0x57/0x7d print_report.cold+0x2d5/0x684 ? do_raw_spin_lock+0x23d/0x270 kasan_report+0xb1/0x1a0 ? do_raw_spin_lock+0x23d/0x270 do_raw_spin_lock+0x23d/0x270 ? rwlock_bug.part.0+0x90/0x90 ? __delete_object+0xb8/0x100 ? lock_downgrade+0x6e0/0x6e0 _raw_spin_lock_irqsave+0x43/0x60 ? __wake_up_common_lock+0xb9/0x140 __wake_up_common_lock+0xb9/0x140 ? __wake_up_common+0x650/0x650 ? destroy_tis_callback+0x53/0x70 [mlx5_core] ? kasan_set_track+0x21/0x30 ? destroy_tis_callback+0x53/0x70 [mlx5_core] ? kfree+0x1ba/0x520 ? do_raw_spin_unlock+0x54/0x220 mlx5_cmd_exec_cb_handler+0x136/0x1a0 [mlx5_core] ? mlx5_cmd_cleanup_async_ctx+0x220/0x220 [mlx5_core] ? mlx5_cmd_cleanup_async_ctx+0x220/0x220 [mlx5_core] mlx5_cmd_comp_handler+0x65a/0x12b0 [mlx5_core] ? dump_command+0xcc0/0xcc0 [mlx5_core] ? lockdep_hardirqs_on_prepare+0x400/0x400 ? cmd_comp_notifier+0x7e/0xb0 [mlx5_core] cmd_comp_notifier+0x7e/0xb0 [mlx5_core] atomic_notifier_call_chain+0xd7/0x1d0 mlx5_eq_async_int+0x3ce/0xa20 [mlx5_core] atomic_notifier_call_chain+0xd7/0x1d0 ? irq_release+0x140/0x140 [mlx5_core] irq_int_handler+0x19/0x30 [mlx5_core] __handle_irq_event_percpu+0x1f2/0x620 handle_irq_event+0xb2/0x1d0 handle_edge_irq+0x21e/0xb00 __common_interrupt+0x79/0x1a0 common_interrupt+0x78/0xa0 asm_common_interrupt+0x22/0x40 RIP: 0010:default_idle+0x42/0x60 Code: c1 83 e0 07 48 c1 e9 03 83 c0 03 0f b6 14 11 38 d0 7c 04 84 d2 75 14 8b 05 eb 47 22 02 85 c0 7e 07 0f 00 2d e0 9f 48 00 fb f4 48 c7 c7 80 08 7f 85 e8 d1 d3 3e fe eb de 66 66 2e 0f 1f 84 00 RSP: 0018:ffff888100dbfdf0 EFLAGS: 00000242 RAX: 0000000000000001 RBX: ffffffff84ecbd48 RCX: 1ffffffff0afe110 RDX: 0000000000000004 RSI: 0000000000000000 RDI: ffffffff835cc9bc RBP: 0000000000000005 R08: 0000000000000001 R09: ffff88881dec4ac3 R10: ffffed1103bd8958 R11: 0000017d0ca571c9 R12: 0000000000000005 R13: ffffffff84f024e0 R14: 0000000000000000 R15: dffffc0000000000 ? default_idle_call+0xcc/0x450 default_idle_call+0xec/0x450 do_idle+0x394/0x450 ? arch_cpu_idle_exit+0x40/0x40 ? do_idle+0x17/0x450 cpu_startup_entry+0x19/0x20 start_secondary+0x221/0x2b0 ? set_cpu_sibling_map+0x2070/0x2070 secondary_startup_64_no_verify+0xcd/0xdb

Allocated by task 49502: kasan_save_stack+0x1e/0x40 __kasan_kmalloc+0x81/0xa0 kvmalloc_node+0x48/0xe0 mlx5e_bulk_async_init+0x35/0x110 [mlx5_core] mlx5e_tls_priv_tx_list_cleanup+0x84/0x3e0 [mlx5_core] mlx5e_ktls_cleanup_tx+0x38f/0x760 [mlx5_core] mlx5e_cleanup_nic_tx+0xa7/0x100 [mlx5_core] mlx5e_detach_netdev+0x1c ---truncated---

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

Published

December 24, 2025

Last Modified

August 5, 2026

Advisory Details (5)

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

net/mlx5: Fix possible use-after-free in async command interface - kernel/git/stable/linux.git - Linux kernel stable tree

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

net/mlx5: Fix possible use-after-free in async command interface - kernel/git/stable/linux.git - Linux kernel stable tree

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

net/mlx5: Fix possible use-after-free in async command interface - kernel/git/stable/linux.git - Linux kernel stable tree

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

net/mlx5: Fix possible use-after-free in async command interface - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/69dd3ad406c49aa69ce4852c15231ac56af8caf9
generic

net/mlx5: Fix possible use-after-free in async command interface - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0aa3ee1e4e5c9ed5dda11249450d609c3072c54e

Vendor Advisories for CVE-2022-50726(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-477.10.1.el8_82023-05-16redhat
redhatkernel-0:5.14.0-284.11.1.el9_22023-05-09redhat
linuxKernel @ 5.4.223—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 ... 5.10.92-2 (22 versions)5.10.158-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux—6.0.7-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux—6.0.7-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux—6.0.7-1—

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2022-50726?
CVE-2022-50726 is a high vulnerability published on December 24, 2025. In the Linux kernel, the following vulnerability has been resolved: net/mlx5: Fix possible use-after-free in async command interface mlx5cmdcleanupasyncctx should return only after all its callback handlers were completed. Before this patch, the below race between mlx5cmdcleanupasyncctx and…
When was CVE-2022-50726 disclosed?
CVE-2022-50726 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-50726 actively exploited?
CVE-2022-50726 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 91.2% of all scored CVEs.
What is the CVSS score of CVE-2022-50726?
CVE-2022-50726 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2022-50726?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-50726, 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-50726

Explore →

Is Your Infrastructure Affected by CVE-2022-50726?

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

Start Free Scan →Browse All CVEs