CVE-2023-46842

MEDIUMNVD 6.56.5
EchelonGraph scoreMEDIUM confidence

Score 6.5 from GitHub Security Advisory published 2024-05-16. NVD baseline CVSS 6.5; sources differ by 0.0.

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

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

Unlike 32-bit PV guests, HVM guests may switch freely between 64-bit and other modes. This in particular means that they may set registers used to pass 32-bit-mode hypercall arguments to values outside of the range 32-bit code would be able to set them to.

When processing of hypercalls takes a considerable amount of time, the hypervisor may choose to invoke a hypercall continuation. Doing so involves putting (perhaps updated) hypercall arguments in respective registers. For guests not running in 64-bit mode this further involves a certain amount of translation of the values.

Unfortunately internal sanity checking of these translated values assumes high halves of registers to always be clear when invoking a hypercall. When this is found not to be the case, it triggers a consistency check in the hypervisor and causes a crash.

CVSS v3
6.5
EG Score
6.5(medium)
EG Risk
33(Track)
EG Risk 33/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
Severity65% × 45%
Exploitation9% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
9%
EPSS %ILE
95%
KEV
Not listed

Published

May 16, 2024

Last Modified

January 5, 2026

Affected Packages

(13 across 13 ecosystems)
Alpine:v3.16(1)
PackageVulnerable rangeFixed inDependents
xen4.16.6-r0
Alpine:v3.17(1)
PackageVulnerable rangeFixed inDependents
xen4.16.6-r0
Alpine:v3.18(1)
PackageVulnerable rangeFixed inDependents
xen4.17.4-r0
Alpine:v3.19(1)
PackageVulnerable rangeFixed inDependents
xen4.18.2-r0
Alpine:v3.20(1)
PackageVulnerable rangeFixed inDependents
xen4.18.2-r0
Alpine:v3.21(1)
PackageVulnerable rangeFixed inDependents
xen4.18.2-r0
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
xen4.18.2-r0
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
xen4.18.2-r0
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
xen4.18.2-r0
Debian:11(1)
PackageVulnerable rangeFixed inDependents
xen4.14.2+25-gb6a8c4f72d-2 ... 4.20.3+127-gc42374a105-1 (46 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
xen4.17.1+2-gb773c48e36-1 ... 4.17.3+36-g54dacb5c02-1 (11 versions)4.17.5+23-ga4e5191dc0-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
xen4.19.1-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
xen4.19.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 / 31× 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 170 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2023-46842?
CVE-2023-46842 is a medium vulnerability published on May 16, 2024. Unlike 32-bit PV guests, HVM guests may switch freely between 64-bit and other modes. This in particular means that they may set registers used to pass 32-bit-mode hypercall arguments to values outside of the range 32-bit code would be able to set them to. When processing of hypercalls takes a…
When was CVE-2023-46842 disclosed?
CVE-2023-46842 was first published in the National Vulnerability Database on May 16, 2024, with the most recent update on January 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-46842 actively exploited?
CVE-2023-46842 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 9% probability of exploitation in the next 30 days, which ranks it in the top 5.2% of all scored CVEs.
What is the CVSS score of CVE-2023-46842?
CVE-2023-46842 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2023-46842?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-46842, 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-2023-46842

Explore →

Is Your Infrastructure Affected by CVE-2023-46842?

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