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

> An out-of-bounds write in AMD graphics drivers allows attackers to potentially execute code or cause denial of service.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 6 Sep 2025
- **Updated:** 8 Sep 2025
- **Also known as:** GHSA-8hgc-v7h6-7v8j

## What is CVE-2025-0010?

CVE-2025-0010 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, and only if a user opens a file or follows a link.

### Official description

An out of bounds write in the Linux graphics driver could allow an attacker to overflow the buffer potentially resulting in loss of confidentiality, integrity, or availability.

Weakness: CWE-787 (Out-of-bounds Write)

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


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

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

## Is CVE-2025-0010 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-0010 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, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-0010 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-2025-0010/ (Markdown: https://insights.sbomify.com/CVE-2025-0010/index.md)
```

## Sources

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

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