CVE-2020-25600

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2022-05-24. 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: 0.4%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

An issue was discovered in Xen through 4.14.x. Out of bounds event channels are available to 32-bit x86 domains. The so called 2-level event channel model imposes different limits on the number of usable event channels for 32-bit x86 domains vs 64-bit or Arm (either bitness) ones. 32-bit x86 domains can use only 1023 channels, due to limited space in their shared (between guest and Xen) information structure, whereas all other domains can use up to 4095 in this model. The recording of the respective limit during domain initialization, however, has occurred at a time where domains are still deemed to be 64-bit ones, prior to actually honoring respective domain properties. At the point domains get recognized as 32-bit ones, the limit didn't get updated accordingly. Due to this misbehavior in Xen, 32-bit domains (including Domain 0) servicing other domains may observe event channel allocations to succeed when they should really fail. Subsequent use of such event channels would then possibly lead to corruption of other parts of the shared info structure. An unprivileged guest may cause another domain, in particular Domain 0, to misbehave. This may lead to a Denial of Service (DoS) for the entire system. All Xen versions from 4.4 onwards are vulnerable. Xen versions 4.3 and earlier are not vulnerable. Only x86 32-bit domains servicing other domains are vulnerable. Arm systems, as well as x86 64-bit domains, are not vulnerable.

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
29
EG Risk 29/100CISA SSVC

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%
Exploitation0% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
34th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 23, 2020

Last Modified

November 21, 2024

References (14)

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntuxen-system-armhf (4.11.3+24-g14b62ab3e5-1ubuntu2.3) @ focal2026-05-23ubuntu

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

(21 across 21 ecosystems)
Alpine:v3.10(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • 4.4.0 up to 4.12.3-r4: fixed in 4.12.3-r4
—
Alpine:v3.11(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • 4.4.0 up to 4.13.1-r4: fixed in 4.13.1-r4
—
Alpine:v3.12(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • 4.4.0 up to 4.13.1-r4: fixed in 4.13.1-r4
—
Alpine:v3.13(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • 4.4.0 up to 4.14.0-r1: fixed in 4.14.0-r1
—
Alpine:v3.14(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • 4.4.0 up to 4.14.0-r1: fixed in 4.14.0-r1
—
Alpine:v3.15(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • 4.4.0 up to 4.14.0-r1: fixed in 4.14.0-r1
—
Alpine:v3.16(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • 4.4.0 up to 4.14.0-r1: fixed in 4.14.0-r1
—
Alpine:v3.17(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • 4.4.0 up to 4.14.0-r1: fixed in 4.14.0-r1
—
Alpine:v3.18(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • 4.4.0 up to 4.14.0-r1: fixed in 4.14.0-r1
—
Alpine:v3.19(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • 4.4.0 up to 4.14.0-r1: fixed in 4.14.0-r1
—
Alpine:v3.20(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • 4.4.0 up to 4.14.0-r1: fixed in 4.14.0-r1
—
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • 4.4.0 up to 4.14.0-r1: fixed in 4.14.0-r1
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • 4.4.0 up to 4.14.0-r1: fixed in 4.14.0-r1
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • 4.4.0 up to 4.14.0-r1: fixed in 4.14.0-r1
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • 4.4.0 up to 4.14.0-r1: fixed in 4.14.0-r1
—
Alpine:v3.9(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • 4.4.0 up to 4.11.4-r2: fixed in 4.11.4-r2
—
Debian:10(1)
PackageVulnerable rangeFix by version rangeDependents
xen4.11.1+92-g6c33308a8d-2 ... 4.11.4-1 (6 versions)
  • every version up to 4.11.4+37-g3263f257ca-1: fixed in 4.11.4+37-g3263f257ca-1
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • every version up to 4.14.0+80-gd101b417b7-1: fixed in 4.14.0+80-gd101b417b7-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • every version up to 4.14.0+80-gd101b417b7-1: fixed in 4.14.0+80-gd101b417b7-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • every version up to 4.14.0+80-gd101b417b7-1: fixed in 4.14.0+80-gd101b417b7-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • every version up to 4.14.0+80-gd101b417b7-1: fixed in 4.14.0+80-gd101b417b7-1
—

Weakness Classification(2)

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

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2020-25600?
CVE-2020-25600 is a medium vulnerability published on September 23, 2020. An issue was discovered in Xen through 4.14.x. Out of bounds event channels are available to 32-bit x86 domains. The so called 2-level event channel model imposes different limits on the number of usable event channels for 32-bit x86 domains vs 64-bit or Arm (either bitness) ones. 32-bit x86…
When was CVE-2020-25600 disclosed?
CVE-2020-25600 was first published on September 23, 2020, 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-2020-25600 actively exploited?
CVE-2020-25600 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (34th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2020-25600?
CVE-2020-25600 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2020-25600?
A fix for CVE-2020-25600 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2020-25600

Explore →

Is Your Infrastructure Affected by CVE-2020-25600?

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