CVE-2022-50726

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

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: the CNA's CVSS, EPSS, GitHub Security Advisory
Trending — 4 sources updated this week

Also known asEUVD-2022-55763 (ENISA EUVD) · GHSA-gjhx-8fr4-rcc6 (GitHub Security Advisories)Source: ENISA EUVD

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

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.8HIGHmedium confidence
EG Risk
35
EG Risk 35/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)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 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 BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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.2%
EPSS %ILE
8th
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.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). 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 (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” 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

August 5, 2026

Advisory Details (5)

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

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
Web page

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
Web page

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
Web page

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
Web page

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 / EcosystemFix (by version range) / 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 (fixes >=5.1.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 ... 5.10.92-2 (22 versions)
  • every version up to 5.10.158-1: fixed in 5.10.158-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.0.7-1: fixed in 6.0.7-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.0.7-1: fixed in 6.0.7-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.0.7-1: fixed in 6.0.7-1
—

Data Freshness Timeline

(refreshed 10× in last 7d / 40× 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 255 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 156 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2022-50726?
CVE-2022-50726 is a high-severity vulnerability; its CVE record was 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 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…
When was the CVE record for CVE-2022-50726 published?
The CVE record for CVE-2022-50726 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 August 5, 2026; the record at its source may have been updated since.
Is CVE-2022-50726 actively exploited?
CVE-2022-50726 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (8th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-50726?
CVE-2022-50726 has a CVSS base score of 7.8 (the CNA's own assessment, by linux; NVD's own analysis pending).
How do I remediate CVE-2022-50726?
A fix for CVE-2022-50726 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2022-50726 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-50726

Explore →

Is Your Infrastructure Affected by CVE-2022-50726?

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

Book a Demo →Browse All CVEs