CVE-2022-49753

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2025-03-27. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2022-55170 (ENISA EUVD) · GHSA-c6c6-6xm6-jhp9 (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:

dmaengine: Fix double increment of client_count in dma_chan_get()

The first time dma_chan_get() is called for a channel the channel client_count is incorrectly incremented twice for public channels, first in balance_ref_count(), and again prior to returning. This results in an incorrect client count which will lead to the channel resources not being freed when they should be. A simple test of repeated module load and unload of async_tx on a Dell Power Edge R7425 also shows this resulting in a kref underflow warning.

[ 124.329662] async_tx: api initialized (async) [ 129.000627] async_tx: api initialized (async) [ 130.047839] ------------[ cut here ]------------ [ 130.052472] refcount_t: underflow; use-after-free. [ 130.057279] WARNING: CPU: 3 PID: 19364 at lib/refcount.c:28 refcount_warn_saturate+0xba/0x110 [ 130.065811] Modules linked in: async_tx(-) rfkill intel_rapl_msr intel_rapl_common amd64_edac edac_mce_amd ipmi_ssif kvm_amd dcdbas kvm mgag200 drm_shmem_helper acpi_ipmi irqbypass drm_kms_helper ipmi_si syscopyarea sysfillrect rapl pcspkr ipmi_devintf sysimgblt fb_sys_fops k10temp i2c_piix4 ipmi_msghandler acpi_power_meter acpi_cpufreq vfat fat drm fuse xfs libcrc32c sd_mod t10_pi sg ahci crct10dif_pclmul libahci crc32_pclmul crc32c_intel ghash_clmulni_intel igb megaraid_sas i40e libata i2c_algo_bit ccp sp5100_tco dca dm_mirror dm_region_hash dm_log dm_mod [last unloaded: async_tx] [ 130.117361] CPU: 3 PID: 19364 Comm: modprobe Kdump: loaded Not tainted 5.14.0-185.el9.x86_64 #1 [ 130.126091] Hardware name: Dell Inc. PowerEdge R7425/02MJ3T, BIOS 1.18.0 01/17/2022 [ 130.133806] RIP: 0010:refcount_warn_saturate+0xba/0x110 [ 130.139041] Code: 01 01 e8 6d bd 55 00 0f 0b e9 72 9d 8a 00 80 3d 26 18 9c 01 00 75 85 48 c7 c7 f8 a3 03 9d c6 05 16 18 9c 01 01 e8 4a bd 55 00 <0f> 0b e9 4f 9d 8a 00 80 3d 01 18 9c 01 00 0f 85 5e ff ff ff 48 c7 [ 130.157807] RSP: 0018:ffffbf98898afe68 EFLAGS: 00010286 [ 130.163036] RAX: 0000000000000000 RBX: ffff9da06028e598 RCX: 0000000000000000 [ 130.170172] RDX: ffff9daf9de26480 RSI: ffff9daf9de198a0 RDI: ffff9daf9de198a0 [ 130.177316] RBP: ffff9da7cddf3970 R08: 0000000000000000 R09: 00000000ffff7fff [ 130.184459] R10: ffffbf98898afd00 R11: ffffffff9d9e8c28 R12: ffff9da7cddf1970 [ 130.191596] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 [ 130.198739] FS: 00007f646435c740(0000) GS:ffff9daf9de00000(0000) knlGS:0000000000000000 [ 130.206832] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 130.212586] CR2: 00007f6463b214f0 CR3: 00000008ab98c000 CR4: 00000000003506e0 [ 130.219729] Call Trace: [ 130.222192] [ 130.224305] dma_chan_put+0x10d/0x110 [ 130.227988] dmaengine_put+0x7a/0xa0 [ 130.231575] __do_sys_delete_module.constprop.0+0x178/0x280 [ 130.237157] ? syscall_trace_enter.constprop.0+0x145/0x1d0 [ 130.242652] do_syscall_64+0x5c/0x90 [ 130.246240] ? exc_page_fault+0x62/0x150 [ 130.250178] entry_SYSCALL_64_after_hwframe+0x63/0xcd [ 130.255243] RIP: 0033:0x7f6463a3f5ab [ 130.258830] Code: 73 01 c3 48 8b 0d 75 a8 1b 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa b8 b0 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 45 a8 1b 00 f7 d8 64 89 01 48 [ 130.277591] RSP: 002b:00007fff22f972c8 EFLAGS: 00000206 ORIG_RAX: 00000000000000b0 [ 130.285164] RAX: ffffffffffffffda RBX: 000055b6786edd40 RCX: 00007f6463a3f5ab [ 130.292303] RDX: 0000000000000000 RSI: 0000000000000800 RDI: 000055b6786edda8 [ 130.299443] RBP: 000055b6786edd40 R08: 0000000000000000 R09: 0000000000000000 [ 130.306584] R10: 00007f6463b9eac0 R11: 0000000000000206 R12: 000055b6786edda8 [ 130.313731] R13: 0000000000000000 R14: 000055b6786edda8 R15: 00007fff22f995f8 [ 130.320875] [ 130.323081] ---[ end trace eff7156d56b5cf25 ]---

cat /sys/class/dma/dma0chan*/in_use would get the wrong result. 2 2 2

Test-by: Jie Hai

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 SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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.2%
EPSS %ILE
14th
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-28). 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 (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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)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 Vulnrichment) · Technical impact total (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

March 27, 2025

Last Modified

April 1, 2025

Advisory Details (7)

Auto-updated Oct 12, 2026
Patch available.
Web page

dmaengine: Fix double increment of client_count in dma_chan_get() - kernel/git/stable/linux.git - Linux kernel stable tree

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

dmaengine: Fix double increment of client_count in dma_chan_get() - kernel/git/stable/linux.git - Linux kernel stable tree

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

dmaengine: Fix double increment of client_count in dma_chan_get() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/71c601965532c38030133535f7cd93c1efa75af1
Web page

dmaengine: Fix double increment of client_count in dma_chan_get() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/42ecd72f02cd657b00b559621e7ef7d2c4d3e5f1
Web page

dmaengine: Fix double increment of client_count in dma_chan_get() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1b409e14b4b7af034e0450f95c165b6c5c87dbc1
Web page

dmaengine: Fix double increment of client_count in dma_chan_get() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/18dd3b30d4c7e8440c63118c7a7b687372b9567f
Web page

dmaengine: Fix double increment of client_count in dma_chan_get() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/142d644fd2cc059ffa042fbfb68e766433ef3afd

Vendor Advisories for CVE-2022-49753(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatkernel-0:5.14.0-284.11.1.el9_22023-05-09redhat
linuxKernel @ 4.14.305 (fixes >=4.0.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 (25 versions)
  • every version up to 5.10.178-1: fixed in 5.10.178-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.1.11-1: fixed in 6.1.11-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.1.11-1: fixed in 6.1.11-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.1.11-1: fixed in 6.1.11-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

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

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2022-49753?
CVE-2022-49753 is a high-severity vulnerability; its CVE record was published on March 27, 2025. In the Linux kernel, the following vulnerability has been resolved: dmaengine: Fix double increment of client_count in dma_chan_get() The first time dma_chan_get() is called for a channel the channel client_count is incorrectly incremented twice for public channels, first in balance_ref_count(),…
When was the CVE record for CVE-2022-49753 published?
The CVE record for CVE-2022-49753 was published on March 27, 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 April 1, 2025; the record at its source may have been updated since.
Is CVE-2022-49753 actively exploited?
CVE-2022-49753 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (14th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-49753?
CVE-2022-49753 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2022-49753?
A fix for CVE-2022-49753 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2022-49753 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-49753

Explore →

Is Your Infrastructure Affected by CVE-2022-49753?

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

Book a Demo →Browse All CVEs