# CVE-2023-20585: Memory corruption in AMD EPYC™ 7003 Series Processors

> A compromised hypervisor can trigger out-of-bounds memory access in AMD EPYC IOMMU, compromising confidential guest integrity.

- **Severity:** Medium 5.6 (`CVSS:4.0/AV:L/AC:H/AT:N/PR:H/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Apr 2026
- **Updated:** 16 Apr 2026
- **Also known as:** GHSA-c43c-pr38-m5g2, ROOT-OS-UBUNTU-2404-CVE-2023-20585, UBUNTU-CVE-2023-20585

## What is CVE-2023-20585?

CVE-2023-20585 is a medium-severity memory corruption vulnerability in AMD EPYC™ 7003 Series Processors, published on 16 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Insufficient checks of the RMP on host buffer access in IOMMU may allow an attacker with privileges and a compromised hypervisor to trigger an out of bounds condition without RMP checks, resulting in a potential loss of confidential guest integrity.

Weakness: CWE-788 (Access of Memory Location After End of Buffer)

## Which versions are affected by CVE-2023-20585?


## How do I fix CVE-2023-20585?

Apply the vendor's patch.

## Is CVE-2023-20585 being exploited?

There is no known exploitation of CVE-2023-20585 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-20585 and fix it if it is affected.

What it is: CVE-2023-20585 is a medium-severity memory corruption vulnerability in AMD EPYC™ 7003 Series Processors, published on 16 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-20585 in the wild and no public exploit code.

Affected product: AMD EPYC™ 7003 Series Processors. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-20585/ (Markdown: https://insights.sbomify.com/CVE-2023-20585/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-20585
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-20585
- OSV: https://osv.dev/vulnerability/CVE-2023-20585

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-20585/
Summaries are generated and may contain mistakes; the official description above is the record.