# CVE-2024-36323: Missing authorization in AMD Instinct™ MI300A

> A malicious guest VM can access other VMs' JPEG register space, allowing unauthorized read and write access to victim data.

- **Severity:** High 8.8 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **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:** 16 May 2026
- **Also known as:** GHSA-r92r-8g7f-hqj2

## What is CVE-2024-36323?

CVE-2024-36323 is a high-severity missing authorization vulnerability in AMD Instinct™ MI300A, 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 isolation of VCN-JPEG HW register space could allow a malicious Guest Virtual Machine (VM) or a process to perform unauthorized access to the register space of the JPEG cores assigned a victim VM/process, potentially gaining arbitrary read/write access to the victim VM/process data.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2024-36323?


## How do I fix CVE-2024-36323?

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

## Is CVE-2024-36323 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-36323 and fix it if it is affected.

What it is: CVE-2024-36323 is a high-severity missing authorization vulnerability in AMD Instinct™ MI300A, 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-2024-36323 in the wild and no public exploit code.

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

## Sources

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

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