CVE-2022-49338

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

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

Score 5.5 from GitHub Security Advisory published 2025-10-21. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2022-54890 (ENISA EUVD) · GHSA-h32p-fx4x-w3v5 (GitHub Security Advisories)Source: ENISA EUVD

5.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

net/mlx5e: CT: Fix cleanup of CT before cleanup of TC ct rules

CT cleanup assumes that all tc rules were deleted first, and so is free to delete the CT shared resources (e.g the dr_action fwd_action which is shared for all tuples). But currently for uplink, this is happens in reverse, causing the below trace.

CT cleanup is called from: mlx5e_cleanup_rep_tx()->mlx5e_cleanup_uplink_rep_tx()-> mlx5e_rep_tc_cleanup()->mlx5e_tc_esw_cleanup()-> mlx5_tc_ct_clean()

Only afterwards, tc cleanup is called from: mlx5e_cleanup_rep_tx()->mlx5e_tc_ht_cleanup() which would have deleted all the tc ct rules, and so delete all the offloaded tuples.

Fix this reversing the order of init and on cleanup, which will result in tc cleanup then ct cleanup.

[ 9443.593347] WARNING: CPU: 2 PID: 206774 at drivers/net/ethernet/mellanox/mlx5/core/steering/dr_action.c:1882 mlx5dr_action_destroy+0x188/0x1a0 [mlx5_core] [ 9443.593349] Modules linked in: act_ct nf_flow_table rdma_ucm(O) rdma_cm(O) iw_cm(O) ib_ipoib(O) ib_cm(O) ib_umad(O) mlx5_core(O-) mlxfw(O) mlxdevm(O) auxiliary(O) ib_uverbs(O) psample ib_core(O) mlx_compat(O) ip_gre gre ip_tunnel act_vlan bonding geneve esp6_offload esp6 esp4_offload esp4 act_tunnel_key vxlan ip6_udp_tunnel udp_tunnel act_mirred act_skbedit act_gact cls_flower sch_ingress nfnetlink_cttimeout nfnetlink xfrm_user xfrm_algo 8021q garp stp ipmi_devintf mrp ipmi_msghandler llc openvswitch nsh nf_conncount nf_nat mst_pciconf(O) dm_multipath sbsa_gwdt uio_pdrv_genirq uio mlxbf_pmc mlxbf_pka mlx_trio mlx_bootctl(O) bluefield_edac sch_fq_codel ip_tables ipv6 crc_ccitt btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq raid1 raid0 crct10dif_ce i2c_mlxbf gpio_mlxbf2 mlxbf_gige aes_neon_bs aes_neon_blk [last unloaded: mlx5_ib] [ 9443.593419] CPU: 2 PID: 206774 Comm: modprobe Tainted: G O 5.4.0-1023.24.gc14613d-bluefield #1 [ 9443.593422] Hardware name: https://www.mellanox.com BlueField SoC/BlueField SoC, BIOS BlueField:143ebaf Jan 11 2022 [ 9443.593424] pstate: 20000005 (nzCv daif -PAN -UAO) [ 9443.593489] pc : mlx5dr_action_destroy+0x188/0x1a0 [mlx5_core] [ 9443.593545] lr : mlx5_ct_fs_smfs_destroy+0x24/0x30 [mlx5_core] [ 9443.593546] sp : ffff8000135dbab0 [ 9443.593548] x29: ffff8000135dbab0 x28: ffff0003a6ab8e80 [ 9443.593550] x27: 0000000000000000 x26: ffff0003e07d7000 [ 9443.593552] x25: ffff800009609de0 x24: ffff000397fb2120 [ 9443.593554] x23: ffff0003975c0000 x22: 0000000000000000 [ 9443.593556] x21: ffff0003975f08c0 x20: ffff800009609de0 [ 9443.593558] x19: ffff0003c8a13380 x18: 0000000000000014 [ 9443.593560] x17: 0000000067f5f125 x16: 000000006529c620 [ 9443.593561] x15: 000000000000000b x14: 0000000000000000 [ 9443.593563] x13: 0000000000000002 x12: 0000000000000001 [ 9443.593565] x11: ffff800011108868 x10: 0000000000000000 [ 9443.593567] x9 : 0000000000000000 x8 : ffff8000117fb270 [ 9443.593569] x7 : ffff0003ebc01288 x6 : 0000000000000000 [ 9443.593571] x5 : ffff800009591ab8 x4 : fffffe000f6d9a20 [ 9443.593572] x3 : 0000000080040001 x2 : fffffe000f6d9a20 [ 9443.593574] x1 : ffff8000095901d8 x0 : 0000000000000025 [ 9443.593577] Call trace: [ 9443.593634] mlx5dr_action_destroy+0x188/0x1a0 [mlx5_core] [ 9443.593688] mlx5_ct_fs_smfs_destroy+0x24/0x30 [mlx5_core] [ 9443.593743] mlx5_tc_ct_clean+0x34/0xa8 [mlx5_core] [ 9443.593797] mlx5e_tc_esw_cleanup+0x58/0x88 [mlx5_core] [ 9443.593851] mlx5e_rep_tc_cleanup+0x24/0x30 [mlx5_core] [ 9443.593905] mlx5e_cleanup_rep_tx+0x6c/0x78 [mlx5_core] [ 9443.593959] mlx5e_detach_netdev+0x74/0x98 [mlx5_core] [ 9443.594013] mlx5e_netdev_change_profile+0x70/0x180 [mlx5_core] [ 9443.594067] mlx5e_netdev_attach_nic_profile+0x34/0x40 [mlx5_core] [ 9443.594122] mlx5e_vport_rep_unload+0x15c/0x1a8 [mlx5_core] [ 9443.594177] mlx5_eswitch_unregister_vport_reps+0x228/0x298 [mlx5_core] [ 9443.594231] mlx5e_rep_remove+0x2c/0x38 ---truncated---

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/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)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.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 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
12th
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 (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 MEDIUMCVSS-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-25). 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

February 26, 2025

Last Modified

October 21, 2025

References (2)

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
linuxKernel @ 5.18.4 (fixes >=5.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

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

Data Freshness Timeline

(refreshed 7× in last 7d / 36× 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 97 of 192 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. 3 repeat rows among the latest 100 are merged into the row they repeat. The 95 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2022-49338?
CVE-2022-49338 is a medium-severity vulnerability; its CVE record was published on February 26, 2025. In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: CT: Fix cleanup of CT before cleanup of TC ct rules CT cleanup assumes that all tc rules were deleted first, and so is free to delete the CT shared resources (e.g the dr_action fwd_action which is shared for all tuples).…
When was the CVE record for CVE-2022-49338 published?
The CVE record for CVE-2022-49338 was published on February 26, 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 21, 2025; the record at its source may have been updated since.
Is CVE-2022-49338 actively exploited?
CVE-2022-49338 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (12th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-49338?
CVE-2022-49338 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2022-49338?
A fix for CVE-2022-49338 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-49338

Explore →

Is Your Infrastructure Affected by CVE-2022-49338?

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

Book a Demo →Browse All CVEs