# CVE-2026-0427: Information disclosure in AMD Instinct™ MI210

> An admin-privileged attacker in a guest VM can access shared GPU resources from another VM, compromising confidentiality, integrity, and availability.

- **Severity:** Medium 4.6 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:L/SC:L/SI:L/SA:L`)
- **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:** 15 May 2026
- **Updated:** 15 May 2026
- **Also known as:** GHSA-j384-fpqm-4mmh

## What is CVE-2026-0427?

CVE-2026-0427 is a medium-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

Improper cleanup of shared register resources in GPU firmware could allow an admin-privileged attacker from a Guest Virtual machine (VM) to access these shared resources from another Guest VM, potentially resulting in the loss of confidentiality, integrity, or availability.

Weakness: CWE-459 (Incomplete Cleanup)

## Which versions are affected by CVE-2026-0427?


## How do I fix CVE-2026-0427?

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

## Is CVE-2026-0427 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-0427 and fix it if it is affected.

What it is: CVE-2026-0427 is a medium-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-2026-0427 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-2026-0427/ (Markdown: https://insights.sbomify.com/CVE-2026-0427/index.md)
```

## Sources

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

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