# CVE-2023-31351: Other in AMD EPYC™ 7003 Series Processors

> A malicious hypervisor can access guest private memory due to improper IOMMU restrictions, compromising integrity on AMD EPYC processors.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Sep 2025
- **Updated:** 8 Sep 2025
- **Also known as:** GHSA-x676-jq8m-r576

## What is CVE-2023-31351?

CVE-2023-31351 is a medium-severity vulnerability in AMD EPYC™ 7003 Series Processors, published on 6 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper restriction of operations in the IOMMU could allow a malicious hypervisor to access guest private memory resulting in loss of integrity.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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


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

No fix has been published for CVE-2023-31351 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-31351 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-31351 is a medium-severity vulnerability in AMD EPYC™ 7003 Series Processors, published on 6 Sep 2025. 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-31351 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-31351/ (Markdown: https://insights.sbomify.com/CVE-2023-31351/index.md)
```

## Sources

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

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