# CVE-2024-21970: Memory corruption in AMD Athlon™ 3000 Series Desktop Processors with Radeon™ Graphics

> A privileged attacker can corrupt AGESA memory via improper array index validation in AMD power management firmware, compromising system integrity.

- **Severity:** Medium 4.4 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/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:** 6 Sep 2025
- **Updated:** 8 Sep 2025
- **Also known as:** GHSA-wph7-6jhm-2x56

## What is CVE-2024-21970?

CVE-2024-21970 is a medium-severity memory corruption vulnerability in AMD Athlon™ 3000 Series Desktop Processors with Radeon™ Graphics, 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 validation of an array index in the AND power Management Firmware could allow a privileged attacker to corrupt AGESA memory potentially leading to a loss of integrity.

Weakness: CWE-129 (Improper Validation of Array Index)

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


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

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

## Is CVE-2024-21970 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-21970 is a medium-severity memory corruption vulnerability in AMD Athlon™ 3000 Series Desktop Processors with Radeon™ Graphics, 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-21970 in the wild and no public exploit code.

Affected product: AMD Athlon™ 3000 Series Desktop Processors with Radeon™ Graphics. 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-21970/ (Markdown: https://insights.sbomify.com/CVE-2024-21970/index.md)
```

## Sources

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

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