CVE-2022-36648

CRITICALNVD 10.010.0—
EchelonGraph scoreMEDIUM confidence

Score 10.0 from GitHub Security Advisory (severity: CRITICAL) published 2023-08-22. NVD baseline CVSS 10.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
10.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 2%CVSS: 10.0Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

The hardware emulation in the of_dpa_cmd_add_l2_flood of rocker device model in QEMU, as used in 7.0.0 and earlier, allows remote attackers to crash the host qemu and potentially execute code on the host via execute a malformed program in the guest OS. Note: This has been disputed by multiple third parties as not a valid vulnerability due to the rocker device not falling within the virtualization use case.

CVSS v3
10.0
EG Score
10.0(medium)
EG Risk
61(Track)
EG Risk 61/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
Severity100% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
2%
EPSS %ILE
77%
KEV
Not listed

Published

August 22, 2023

Last Modified

November 21, 2024

Advisory Details (2)

Auto-updated Sep 19, 2026
No patch confirmed yet.
generic

NetApp Product Security

https://security.netapp.com/advisory/ntap-20231006-0004/
generic

[PATCH] hw/net/rocker: avoid NULL pointer dereference in of_dpa_cmd_add_

https://lists.nongnu.org/archive/html/qemu-devel/2022-06/msg04469.html

Vendor Advisories for CVE-2022-36648(1)

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

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
qemu1:10.0.0+ds-1 ... 1:9.2.2+ds-1~bpo12+1 (225 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
qemu1:10.0.0+ds-1 ... 1:9.2.2+ds-1~bpo12+1 (199 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
qemu1:10.0.10+ds-0+deb13u1 ... 1:11.1.1+ds-1 (65 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
qemu1:10.0.2+ds-2 ... 1:11.1.1+ds-1 (56 versions)——

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 26× 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 175 total refreshes for this CVE.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2022-36648?
CVE-2022-36648 is a critical vulnerability published on August 22, 2023. The hardware emulation in the ofdpacmdaddl2_flood of rocker device model in QEMU, as used in 7.0.0 and earlier, allows remote attackers to crash the host qemu and potentially execute code on the host via execute a malformed program in the guest OS. Note: This has been disputed by multiple third…
When was CVE-2022-36648 disclosed?
CVE-2022-36648 was first published in the National Vulnerability Database on August 22, 2023, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-36648 actively exploited?
CVE-2022-36648 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2% probability of exploitation in the next 30 days, which ranks it in the top 23.3% of all scored CVEs.
What is the CVSS score of CVE-2022-36648?
CVE-2022-36648 has a CVSS v3 base score of 10.0 (NVD).
How do I remediate CVE-2022-36648?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-36648, 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-36648

Explore →

Is Your Infrastructure Affected by CVE-2022-36648?

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

Book a Demo →Browse All CVEs