# CVE-2023-31323: Memory corruption in AMD Instinct™ MI210

> Type confusion in AMD Secure Processor allows attackers to cause memory safety violations, impacting confidentiality, integrity, and availability of AMD GPUs.

- **Severity:** High 8.4 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:L/SC:L/SI:H/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Feb 2026
- **Updated:** 12 Feb 2026
- **Also known as:** GHSA-9w8m-7cg3-7mh9

## What is CVE-2023-31323?

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

### Official description

Type confusion in the AMD Secure Processor (ASP) could allow an attacker to pass a malformed argument to the External Global Memory Interconnect Trusted Agent (XGMI TA) leading to a memory safety violation potentially resulting in loss of confidentiality, integrity, or availability.

Weakness: CWE-843 (Access of Resource Using Incompatible Type)

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


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

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

## Is CVE-2023-31323 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-31323 is a high-severity memory corruption vulnerability in AMD Instinct™ MI210, published on 12 Feb 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-31323 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-31323/ (Markdown: https://insights.sbomify.com/CVE-2023-31323/index.md)
```

## Sources

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

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