# CVE-2025-29951: Memory corruption in AMD Athlon™ 3000 Series Mobile Processors with Radeon™ Graphics

> A buffer overflow in the AMD Secure Processor bootloader allows attackers to overwrite memory, leading to privilege escalation and arbitrary code execution.

- **Severity:** High 7.3 (`CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **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:** 10 Feb 2026
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-hgfv-23wv-7h57

## What is CVE-2025-29951?

CVE-2025-29951 is a high-severity memory corruption vulnerability in AMD Athlon™ 3000 Series Mobile Processors with Radeon™ Graphics, published on 10 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A buffer overflow in the AMD Secure Processor (ASP) bootloader could allow an attacker to overwrite memory, potentially resulting in privilege escalation and arbitrary code execution.

Weakness: CWE-121 (Stack-based Buffer Overflow)

## Which versions are affected by CVE-2025-29951?


## How do I fix CVE-2025-29951?

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

## Is CVE-2025-29951 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-29951 and fix it if it is affected.

What it is: CVE-2025-29951 is a high-severity memory corruption vulnerability in AMD Athlon™ 3000 Series Mobile Processors with Radeon™ Graphics, published on 10 Feb 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-2025-29951 in the wild and no public exploit code.

Affected product: AMD Athlon™ 3000 Series Mobile 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-2025-29951/ (Markdown: https://insights.sbomify.com/CVE-2025-29951/index.md)
```

## Sources

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

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