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

> A privileged attacker can exploit improper input validation in the SMM handler to overwrite SMRAM, enabling arbitrary code execution on AMD processors.

- **Severity:** High 7.5 (`CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **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:** 11 Feb 2025
- **Updated:** 23 Sep 2025
- **Also known as:** GHSA-9mx7-6mvp-m4h2

## What is CVE-2023-31343?

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

### Official description

Improper input validation in the SMM handler may allow a privileged attacker to overwrite SMRAM, potentially leading to arbitrary code execution.

Weakness: CWE-1220 (Insufficient Granularity of Access Control)

## Which versions are affected by CVE-2023-31343?


## How do I fix CVE-2023-31343?

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

## Is CVE-2023-31343 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-31343 and fix it if it is affected.

What it is: CVE-2023-31343 is a high-severity memory corruption vulnerability in AMD Athlon™ 3000 Series Desktop Processors with Radeon™ Graphics, published on 11 Feb 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-2023-31343 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-2023-31343/ (Markdown: https://insights.sbomify.com/CVE-2023-31343/index.md)
```

## Sources

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

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