# CVE-2023-31316: Other in AMD Instinct™ MI210

> An attacker with write access outside trusted memory can alter VCN firmware execution flow, compromising confidentiality, integrity, and availability of AMD hardware.

- **Severity:** High 7.1 (`CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:N/VC:L/VI:H/VA:L/SC:L/SI:H/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 May 2026
- **Updated:** 15 May 2026
- **Also known as:** GHSA-xm8p-xfwc-w7p6

## What is CVE-2023-31316?

CVE-2023-31316 is a high-severity vulnerability in AMD Instinct™ MI210, published on 15 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improperly preserved integrity of hardware configuration state during a power save/restore operation in the AMD Secure Processor (ASP) could allow an attacker with the ability to write outside the trusted memory range (TMR) to change the execution flow of the Video Core Next (VCN) firmware potentially impacting confidentiality, integrity, or availability.

Weakness: CWE-1304 (Improperly Preserved Integrity of Hardware Configuration State During a Power Save/Restore Operation)

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


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

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

## Is CVE-2023-31316 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-31316 is a high-severity vulnerability in AMD Instinct™ MI210, published on 15 May 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-31316 in the wild and no public exploit code.

Affected product: AMD Instinct™ MI210. 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-31316/ (Markdown: https://insights.sbomify.com/CVE-2023-31316/index.md)
```

## Sources

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

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