# CVE-2024-36331: Memory corruption in AMD EPYC™ 9004 Series Processors

> A privileged attacker with hypervisor access can overwrite SEV-SNP guest memory due to improper CPU cache initialization, compromising data integrity.

- **Severity:** Low 3.2 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:N/I:L/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:** Yes
- **Published:** 6 Sep 2025
- **Updated:** 3 Nov 2025
- **Also known as:** DEBIAN-CVE-2024-36331, GHSA-m44f-cvp5-f9xf, ROOT-OS-DEBIAN-11-CVE-2024-36331, ROOT-OS-DEBIAN-12-CVE-2024-36331, ROOT-OS-DEBIAN-13-CVE-2024-36331, ROOT-OS-UBUNTU-2204-CVE-2024-36331, ROOT-OS-UBUNTU-2404-CVE-2024-36331, UBUNTU-CVE-2024-36331

## What is CVE-2024-36331?

CVE-2024-36331 is a low-severity memory corruption vulnerability in AMD EPYC™ 9004 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 initialization of CPU cache memory could allow a privileged attacker with hypervisor access to overwrite SEV-SNP guest memory resulting in loss of data integrity.

Weakness: CWE-665 (Improper Initialization)

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


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

Apply the vendor's patch.

## Is CVE-2024-36331 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-36331 is a low-severity memory corruption vulnerability in AMD EPYC™ 9004 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-2024-36331 in the wild and no public exploit code.

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

## Sources

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

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