CVE-2023-46835

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2024-01-05. 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%CVSS: 5.5Exploit: None knownExposed: 0

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

The current setup of the quarantine page tables assumes that the quarantine domain (dom_io) has been initialized with an address width of DEFAULT_DOMAIN_ADDRESS_WIDTH (48) and hence 4 page table levels.

However dom_io being a PV domain gets the AMD-Vi IOMMU page tables levels based on the maximum (hot pluggable) RAM address, and hence on systems with no RAM above the 512GB mark only 3 page-table levels are configured in the IOMMU.

On systems without RAM above the 512GB boundary amd_iommu_quarantine_init() will setup page tables for the scratch page with 4 levels, while the IOMMU will be configured to use 3 levels only, resulting in the last page table directory (PDE) effectively becoming a page table entry (PTE), and hence a device in quarantine mode gaining write access to the page destined to be a PDE.

Due to this page table level mismatch, the sink page the device gets read/write access to is no longer cleared between device assignment, possibly leading to data leaks.

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

Published

January 5, 2024

Last Modified

June 17, 2026

References (3)

Affected Packages

(14 across 14 ecosystems)
Alpine:v3.15(1)
PackageVulnerable rangeFixed inDependents
xen—4.15.5-r3—
Alpine:v3.16(1)
PackageVulnerable rangeFixed inDependents
xen—4.16.5-r4—
Alpine:v3.17(1)
PackageVulnerable rangeFixed inDependents
xen—4.16.5-r4—
Alpine:v3.18(1)
PackageVulnerable rangeFixed inDependents
xen—4.17.2-r4—
Alpine:v3.19(1)
PackageVulnerable rangeFixed inDependents
xen—4.17.2-r4—
Alpine:v3.20(1)
PackageVulnerable rangeFixed inDependents
xen—4.17.2-r4—
Alpine:v3.21(1)
PackageVulnerable rangeFixed inDependents
xen—4.17.2-r4—
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
xen—4.17.2-r4—
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
xen—4.17.2-r4—
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
xen—4.17.2-r4—
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.2+55-g0b56bed864-1, 4.17.2-14.17.2+76-ge1f9cb16e2-1~deb12u1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
xen—4.17.2+76-ge1f9cb16e2-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
xen—4.17.2+76-ge1f9cb16e2-1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 33× 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 179 total refreshes for this CVE.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2023-46835?
CVE-2023-46835 is a medium vulnerability published on January 5, 2024. The current setup of the quarantine page tables assumes that the quarantine domain (dom_io) has been initialized with an address width of DEFAULTDOMAINADDRESS_WIDTH (48) and hence 4 page table levels. However dom_io being a PV domain gets the AMD-Vi IOMMU page tables levels based on the maximum…
When was CVE-2023-46835 disclosed?
CVE-2023-46835 was first published in the National Vulnerability Database on January 5, 2024, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-46835 actively exploited?
CVE-2023-46835 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 81.5% of all scored CVEs.
What is the CVSS score of CVE-2023-46835?
CVE-2023-46835 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2023-46835?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-46835, 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-46835

Explore →

Is Your Infrastructure Affected by CVE-2023-46835?

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

Book a Demo →Browse All CVEs