# CVE-2024-21980: Memory corruption in 3rd Gen AMD EPYC™ Processors

> A malicious hypervisor can overwrite guest memory or UMC seed in AMD EPYC firmware, compromising confidentiality and integrity.

- **Severity:** High 7.9 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/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:** 5 Aug 2024
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-q9j5-9g8p-5h5q

## What is CVE-2024-21980?

CVE-2024-21980 is a high-severity memory corruption vulnerability in Amd Epyc 72f3 Firmware, published on 5 Aug 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper restriction of write operations in SNP firmware could allow a malicious hypervisor to potentially overwrite a guest's memory or UMC seed resulting in loss of confidentiality and integrity.

Weakness: CWE-787 (Out-of-bounds Write), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 86 products.


Products: Amd Epyc 7203 Firmware, Amd Epyc 7203p Firmware, Amd Epyc 72f3 Firmware, Amd Epyc 7303 Firmware, Amd Epyc 7303p Firmware, Amd Epyc 7313 Firmware, Amd Epyc 7313p Firmware, Amd Epyc 7343 Firmware, Amd Epyc 7373x Firmware, Amd Epyc 73f3 Firmware, Amd Epyc 7413 Firmware, Amd Epyc 7443 Firmware, Amd Epyc 7443p Firmware, Amd Epyc 7453 Firmware, Amd Epyc 7473x Firmware, Amd Epyc 74f3 Firmware, Amd Epyc 7513 Firmware, Amd Epyc 7543 Firmware, Amd Epyc 7543p Firmware, Amd Epyc 7573x Firmware and 66 more.

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

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

## Is CVE-2024-21980 being exploited?

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

Public exploit code:

- https://github.com/Freax13/cve-2024-21980-poc (github_poc): https://github.com/Freax13/cve-2024-21980-poc

## Other vulnerabilities in Amd Epyc 72f3 Firmware

- [CVE-2023-20591](https://insights.sbomify.com/CVE-2023-20591/): Other in AMD EPYC™ 7003 Series Processors (medium 6.5)
- [CVE-2023-20533](https://insights.sbomify.com/CVE-2023-20533/): Denial of service in 2nd Gen AMD EPYC™ Processors (medium 6.1)
- [CVE-2023-31355](https://insights.sbomify.com/CVE-2023-31355/): Memory corruption in 3rd Gen AMD EPYC™ Processors (medium 6.0)
- [CVE-2024-21978](https://insights.sbomify.com/CVE-2024-21978/): Information disclosure in 3rd Gen AMD EPYC™ Processors (medium 6.0)
- [CVE-2023-31346](https://insights.sbomify.com/CVE-2023-31346/): Information disclosure in 3rd Gen AMD EPYC™ Processors (medium 6.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-21980 is a high-severity memory corruption vulnerability in Amd Epyc 72f3 Firmware, published on 5 Aug 2024. 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-21980 in the wild and no public exploit code.

Affected product: Amd Epyc 72f3 Firmware. 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-21980/ (Markdown: https://insights.sbomify.com/CVE-2024-21980/index.md)
```

## Sources

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

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