dbcve.org
Epyc 8024pn FirmwareOperating system · Amd

CVE-2023-20584

MEDIUM · 6.0 CVSS v3.1 Published 2024-08-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
IOMMU improperly handles certain special address ranges with invalid device table entries (DTEs), which may allow an attacker with privileges and a compromised Hypervisor to induce DTE faults to bypass RMP checks in SEV-SNP, potentially leading to a loss of guest integrity.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This AMD SEV-SNP vulnerability in the IOMMU allows improper handling of special address ranges with invalid Device Table Entries (DTEs). An attacker with privileges and a compromised hypervisor can induce DTE faults to bypass Reverse Memory Protection (RMP) checks, potentially compromising guest VM integrity.

MitigationEnsure hypervisor integrity is maintained and apply AMD-provided IOMMU firmware microcode updates for SEV-SNP-capable systems. Review and validate SEV-SNP deployment configurations per AMD guidance.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Epyc 8024pn FirmwareOperating system
Affected:< genoapi_1.0.0.b
Epyc 8024p FirmwareOperating system
Affected:< genoapi_1.0.0.b
Epyc 8124pn FirmwareOperating system
Affected:< genoapi_1.0.0.b
Epyc 8124p FirmwareOperating system
Affected:< genoapi_1.0.0.b
Epyc 8224pn FirmwareOperating system
Affected:< genoapi_1.0.0.b
Epyc 8224p FirmwareOperating system
Affected:< genoapi_1.0.0.b
Epyc 8324pn FirmwareOperating system
Affected:< genoapi_1.0.0.b
Epyc 8324p FirmwareOperating system
Affected:< genoapi_1.0.0.b

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
High
User interaction
None
Scope
Changed
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:N/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the processor model
    Use system information commands (such as 'lscpu' or hypervisor inventory) to determine if the CPU is an AMD Epyc 8024p, 8024pn, 8124p, 8124pn, 8224p, 8224pn, 8324p, or 8324pn model.
    Affected if The installed processor matches any of the listed affected Epyc model numbers.
  2. Check the IOMMU firmware version
    Query the system BIOS/firmware management interface or use AMD's firmware versioning tools to retrieve the genoapi version. Compare it to the threshold 'genoapi_1.0.0.b'.
    Affected if The installed IOMMU firmware version is earlier than genoapi_1.0.0.b on an affected processor.
  3. Determine if SEV-SNP is enabled
    Check the hypervisor or boot configuration for SEV-SNP (Secure Encrypted Virtualization-Secure Nested Paging) enablement status. This may be visible in hypervisor logs, guest configuration, or SEV-SNP capability queries.
    Affected if SEV-SNP is actively enabled and running on the affected hardware.
  4. Verify the hypervisor environment
    Confirm that the system is functioning as a hypervisor host or a guest VM in a virtualized environment where IOMMU passthrough or device assignment is in use.
    Affected if The system runs a hypervisor with IOMMU device assignment and SEV-SNP protection is in use.

A system is affected if it uses any of the listed AMD Epyc processor models with IOMMU firmware below genoapi_1.0.0.b while running SEV-SNP-protected virtual machines in a hypervisor environment.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Ensure hypervisor integrity is maintained and apply AMD-provided IOMMU firmware microcode updates for SEV-SNP-capable systems. Review and validate SEV-SNP deployment configurations per AMD guidance.

Recommended fix Moderate confidence

genoapi_1.0.0.b or later

  1. 1. Identify the specific Epyc processor model (8024pn, 8024p, 8124pn, 8124p, 8224pn, 8224p, 8324pn, or 8324p) in your environment
  2. 2. Check the current firmware version by querying the system's BMC or using AMD's system management tools
  3. 3. Obtain the updated firmware version genoapi_1.0.0.b or later from AMD's support portal or your system vendor
  4. 4. Apply the firmware update following AMD's standard firmware update procedures for the specific processor model
  5. 5. After update, verify the firmware version has been successfully applied and matches genoapi_1.0.0.b or later
  6. 6. For SEV-SNP deployments, validate that the IOMMU firmware update is properly integrated with the hypervisor and that RMP checks are functioning correctly

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Epyc 8024pn Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-20584 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-20584 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data