CVE-2022-49670

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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

linux/dim: Fix divide by 0 in RDMA DIM

Fix a divide 0 error in rdma_dim_stats_compare() when prev->cpe_ratio ==

  • CallTrace:
Hardware name: H3C R4900 G3/RS33M2C9S, BIOS 2.00.37P21 03/12/2020 task: ffff880194b78000 task.stack: ffffc90006714000 RIP: 0010:backport_rdma_dim+0x10e/0x240 [mlx_compat] RSP: 0018:ffff880c10e83ec0 EFLAGS: 00010202 RAX: 0000000000002710 RBX: ffff88096cd7f780 RCX: 0000000000000064 RDX: 0000000000000000 RSI: 0000000000000002 RDI: 0000000000000001 RBP: 0000000000000001 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000000 R12: 000000001d7c6c09 R13: ffff88096cd7f780 R14: ffff880b174fe800 R15: 0000000000000000 FS: 0000000000000000(0000) GS:ffff880c10e80000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00000000a0965b00 CR3: 000000000200a003 CR4: 00000000007606e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 PKRU: 55555554 Call Trace: ib_poll_handler+0x43/0x80 [ib_core] irq_poll_softirq+0xae/0x110 __do_softirq+0xd1/0x28c irq_exit+0xde/0xf0 do_IRQ+0x54/0xe0 common_interrupt+0x8f/0x8f ? cpuidle_enter_state+0xd9/0x2a0 ? cpuidle_enter_state+0xc7/0x2a0 ? do_idle+0x170/0x1d0 ? cpu_startup_entry+0x6f/0x80 ? start_secondary+0x1b9/0x210 ? secondary_startup_64+0xa5/0xb0 Code: 0f 87 e1 00 00 00 8b 4c 24 14 44 8b 43 14 89 c8 4d 63 c8 44 29 c0 99 31 d0 29 d0 31 d2 48 98 48 8d 04 80 48 8d 04 80 48 c1 e0 02 <49> f7 f1 48 83 f8 0a 0f 86 c1 00 00 00 44 39 c1 7f 10 48 89 df RIP: backport_rdma_dim+0x10e/0x240 [mlx_compat] RSP: ffff880c10e83ec0

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
25(Track)
EG Risk 25/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
Severity55% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
52%
KEV
Not listed

Published

February 26, 2025

Last Modified

August 5, 2026

Vendor Advisories for CVE-2022-49670(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 / EcosystemFixed in / PatchReleasedSource
redhatkernel-0:5.14.0-611.5.1.el9_72025-11-11redhat
linuxKernel @ 5.4.204osv

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 (17 versions)5.10.136-1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux5.18.14-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux5.18.14-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux5.18.14-1

Weakness Classification(1)

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

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2022-49670?
CVE-2022-49670 is a medium vulnerability published on February 26, 2025. In the Linux kernel, the following vulnerability has been resolved: linux/dim: Fix divide by 0 in RDMA DIM Fix a divide 0 error in rdmadimstatscompare() when prev->cperatio == 0. CallTrace: Hardware name: H3C R4900 G3/RS33M2C9S, BIOS 2.00.37P21 03/12/2020 task: ffff880194b78000 task.stack:…
When was CVE-2022-49670 disclosed?
CVE-2022-49670 was first published in the National Vulnerability Database on February 26, 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-49670 actively exploited?
CVE-2022-49670 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 47.7% of all scored CVEs.
What is the CVSS score of CVE-2022-49670?
CVE-2022-49670 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2022-49670?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-49670, 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-49670

Explore →

Is Your Infrastructure Affected by CVE-2022-49670?

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