CVE-2022-26357

HIGHNVD 7.07.0—
EchelonGraph scoreMEDIUM confidence

Score 7.0 from GitHub Security Advisory (severity: HIGH) published 2022-04-06. NVD baseline CVSS 7.0; sources differ by 0.0.

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

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

race in VT-d domain ID cleanup Xen domain IDs are up to 15 bits wide. VT-d hardware may allow for only less than 15 bits to hold a domain ID associating a physical device with a particular domain. Therefore internally Xen domain IDs are mapped to the smaller value range. The cleaning up of the housekeeping structures has a race, allowing for VT-d domain IDs to be leaked and flushes to be bypassed.

CVSS v3
7.0
EG Score
7.0(medium)
EG Risk
36(Track)
EG Risk 36/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
Severity70% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
17%
KEV
Not listed

Published

April 5, 2022

Last Modified

November 21, 2024

References (14)

Affected Packages

(17 across 17 ecosystems)
Alpine:v3.12(1)
PackageVulnerable rangeFixed inDependents
xen—4.13.4-r3—
Alpine:v3.13(1)
PackageVulnerable rangeFixed inDependents
xen—4.14.5-r0—
Alpine:v3.14(1)
PackageVulnerable rangeFixed inDependents
xen—4.15.2-r2—
Alpine:v3.15(1)
PackageVulnerable rangeFixed inDependents
xen—4.15.2-r2—
Alpine:v3.16(1)
PackageVulnerable rangeFixed inDependents
xen—4.16.1-r0—
Alpine:v3.17(1)
PackageVulnerable rangeFixed inDependents
xen—4.16.1-r0—
Alpine:v3.18(1)
PackageVulnerable rangeFixed inDependents
xen—4.16.1-r0—
Alpine:v3.19(1)
PackageVulnerable rangeFixed inDependents
xen—4.16.1-r0—
Alpine:v3.20(1)
PackageVulnerable rangeFixed inDependents
xen—4.16.1-r0—
Alpine:v3.21(1)
PackageVulnerable rangeFixed inDependents
xen—4.16.1-r0—
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
xen—4.16.1-r0—
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
xen—4.16.1-r0—
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
xen—4.16.1-r0—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
xen4.14.2+25-gb6a8c4f72d-2, 4.14.3+32-g9de3671772-1, 4.14.3+32-g9de3671772-1~deb11u1, 4.14.3-1, 4.14.3-1~deb11u14.14.4+74-gd7b22226b5-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
xen—4.16.1-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
xen—4.16.1-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
xen—4.16.1-1—

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 145 total refreshes for this CVE.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2022-26357?
CVE-2022-26357 is a high vulnerability published on April 5, 2022. race in VT-d domain ID cleanup Xen domain IDs are up to 15 bits wide. VT-d hardware may allow for only less than 15 bits to hold a domain ID associating a physical device with a particular domain. Therefore internally Xen domain IDs are mapped to the smaller value range. The cleaning up of the…
When was CVE-2022-26357 disclosed?
CVE-2022-26357 was first published in the National Vulnerability Database on April 5, 2022, 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-26357 actively exploited?
CVE-2022-26357 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 82.7% of all scored CVEs.
What is the CVSS score of CVE-2022-26357?
CVE-2022-26357 has a CVSS v3 base score of 7.0 (NVD).
How do I remediate CVE-2022-26357?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-26357, 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-26357

Explore →

Is Your Infrastructure Affected by CVE-2022-26357?

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

Start Free Scan →Browse All CVEs