CVE-2022-2962

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2022-09-14. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 0

A fix is available — apply it.

A DMA reentrancy issue was found in the Tulip device emulation in QEMU. When Tulip reads or writes to the rx/tx descriptor or copies the rx/tx frame, it doesn't check whether the destination address is its own MMIO address. This can cause the device to trigger MMIO handlers multiple times, possibly leading to a stack or heap overflow. A malicious guest could use this flaw to crash the QEMU process on the host, resulting in a denial of service condition.

CVSS v3
7.8
EG Score
7.8(medium)
EPSS
30.5%
KEV
Not listed

Published

September 13, 2022

Last Modified

April 23, 2025

References (4)

Vendor Advisories for CVE-2022-2962(1)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuqemu-system-mips (1:2.5+dfsg-5ubuntu10.51+esm1) @ xenial2026-05-25ubuntu

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.

Weakness Classification(3)

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

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 13× in last 7d / 48× 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.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2022-2962?
CVE-2022-2962 is a high vulnerability published on September 13, 2022. A DMA reentrancy issue was found in the Tulip device emulation in QEMU. When Tulip reads or writes to the rx/tx descriptor or copies the rx/tx frame, it doesn't check whether the destination address is its own MMIO address. This can cause the device to trigger MMIO handlers multiple times, possibly…
When was CVE-2022-2962 disclosed?
CVE-2022-2962 was first published in the National Vulnerability Database on September 13, 2022, with the most recent update on April 23, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-2962 actively exploited?
CVE-2022-2962 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 30.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2022-2962?
CVE-2022-2962 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2022-2962?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-2962, 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

Explore the affected products and dependency analysis for CVE-2022-2962

Explore →

Is Your Infrastructure Affected by CVE-2022-2962?

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

Start Free Scan →Browse All CVEs