# CVE-2024-21944: Memory corruption in AMD EPYC™ 7003 Series Processors

> An attacker with physical or privileged access can corrupt guest memory via improper DIMM SPD validation, compromising data integrity on AMD EPYC systems.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:N/I:H/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:** No
- **Published:** 10 Jun 2026
- **Updated:** 11 Jun 2026
- **Also known as:** GHSA-4c4q-g449-2566

## What is CVE-2024-21944?

CVE-2024-21944 is a medium-severity memory corruption vulnerability in AMD EPYC™ 7003 Series Processors, published on 10 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper input validation for DIMM serial presence detect (SPD) metadata could allow an attacker with physical access, ring0 access on a system with a non-compliant DIMM, or control over the Root of Trust for BIOS update, to potentially overwrite guest memory resulting in loss of guest data integrity.

Weakness: CWE-20 (Improper Input Validation)

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


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

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

## Is CVE-2024-21944 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-21944 is a medium-severity memory corruption vulnerability in AMD EPYC™ 7003 Series Processors, published on 10 Jun 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-21944 in the wild and no public exploit code.

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

## Sources

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

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