CVE-2023-20591Network attack vector

Hypervisor memory access via stale IOMMU configuration

Published Aug 13, 2024 · Updated Mar 13, 2025

Improper IOMMU initialization in AMD EPYC platform firmware allows remote attackers to read or modify hypervisor memory during DRTM. During a Dynamic Root of Trust for Measurement event, the IOMMU is not re-initialized, so an untrusted platform configuration remains active. Exploitation requires a network-reachable path to influence that configuration and high attack complexity; successful access can expose or alter hypervisor memory and interrupt service.

CVSS severity6.5
Medium
EPSS probability0.30%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Improper IOMMU initialization in AMD EPYC platform firmware allows remote attackers to read or modify hypervisor memory during DRTM. During a Dynamic Root of Trust for Measurement event, the IOMMU is not re-initialized, so an untrusted platform configuration remains active. Exploitation requires a network-reachable path to influence that configuration and high attack complexity; successful access can expose or alter hypervisor memory and interrupt service.

The record

CVE
CVE-2023-20591
Published
Aug 13, 2024
Updated
Mar 13, 2025
Vendor
Advanced Micro Devices, Inc.
Product
AMD EPYC 9754S Firmware
Classifications
CWE-665
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Aug 13, 2024CVE publishedPublication date reported by the CVE source.
  2. Mar 13, 2025Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=0 <genoapi_1.0.0.8

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Advanced Micro Devices, Inc. · AMD EPYC 9754S Firmwareversion=0 <genoapi_1.0.0.8
Advanced Micro Devices, Inc. · AMD EPYC Embedded 7003 Series ProcessorsAffected versions are unavailable in this record.
Advanced Micro Devices, Inc. · AMD EPYC Embedded 9003 Series ProcessorsAffected versions are unavailable in this record.
Advanced Micro Devices, Inc. · AMD EPYC 7773X Firmwareversion=0 <milanpi_1.0.0.b
Advanced Micro Devices, Inc. · AMD EPYC™ 9004 Series ProcessorsAffected versions are unavailable in this record.
Advanced Micro Devices, Inc. · AMD EPYC 7003 Firmwareversion=0 <milanpi_1.0.0.b
Advanced Micro Devices, Inc. · AMD EPYC™ 7003 Series ProcessorsAffected versions are unavailable in this record.

Published CVSS scores

6.5Advanced Micro Devices, Inc.CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:L

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-665Improper Initialization

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo