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

> An attacker can exploit improper bounds checking in AMD APCB firmware to perform an out-of-bounds write, potentially leading to arbitrary code execution.

- **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:** 13 Aug 2024
- **Updated:** 18 Mar 2025
- **Also known as:** GHSA-cjjq-cwpw-fx4q

## What is CVE-2022-23815?

CVE-2022-23815 is a high-severity memory corruption vulnerability in AMD Athlon™ 3000 Series Desktop Processors with Radeon™ Graphics, published on 13 Aug 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper bounds checking in APCB firmware may allow an attacker to perform an out of bounds write, corrupting the APCB entry, potentially leading to arbitrary code execution.

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

## Which versions are affected by CVE-2022-23815?

It affects 16 products.


Products: Amd Athlon Gold 3150g Firmware, Amd Athlon Gold 3150u Firmware, Amd Athlon Gold Pro 3150g Firmware, Amd Athlon Gold Pro 3150ge Firmware, Amd Athlon Pro 300ge Firmware, Amd Athlon Silver 3050u Firmware, Amd Ryzen 3 3200u Firmware, Amd Ryzen 3 3250u Firmware, Amd Ryzen 3 3300u Firmware, Amd Ryzen 5 3500u Firmware, Amd Ryzen 5 3550h Firmware, Amd Ryzen 5 3580u Firmware, Amd Ryzen 7 3700u Firmware, Amd Ryzen 7 3750h Firmware, Amd Ryzen 7 3780u Firmware, Amd Ryzen 7 Pro 3700u Firmware.

## How do I fix CVE-2022-23815?

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

## Is CVE-2022-23815 being exploited?

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

## Other vulnerabilities in AMD Athlon™ 3000 Series Desktop Processors with Radeon™ Graphics

- [CVE-2021-46753](https://insights.sbomify.com/CVE-2021-46753/): Memory corruption in Athlon™ 3000 Series Mobile Processors with Radeon™ Graphics “Pollock” (critical 9.1)
- [CVE-2021-46754](https://insights.sbomify.com/CVE-2021-46754/): Information disclosure in AMD Ryzen™ Embedded R1000 (critical 9.1)
- [CVE-2021-46749](https://insights.sbomify.com/CVE-2021-46749/): Denial of service in 3rd Gen AMD Ryzen™ Threadripper™ Processors “Castle Peak” HEDT (high 7.5)
- [CVE-2021-46794](https://insights.sbomify.com/CVE-2021-46794/): Denial of service in 3rd Gen AMD Ryzen™ Threadripper™ Processors “Castle Peak” HEDT (high 7.5)
- [CVE-2021-46759](https://insights.sbomify.com/CVE-2021-46759/): Memory corruption in Athlon™ 3000 Series Mobile Processors with Radeon™ Graphics “Pollock” (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-23815 and fix it if it is affected.

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

## Sources

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

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