# CVE-2021-46759: Memory corruption in Athlon™ 3000 Series Mobile Processors with Radeon™ Graphics “Pollock”

> An attacker with physical access can exploit improper input validation in the AMD TEE to reveal secure bootloader memory contents via serial port.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 May 2023
- **Updated:** 27 Jan 2025
- **Also known as:** GHSA-gp8r-64c4-ggqw

## What is CVE-2021-46759?

CVE-2021-46759 is a medium-severity memory corruption vulnerability in AMD Athlon™ 3000 Series Mobile Processors with Radeon™ Graphics   “Pollock”, published on 9 May 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper syscall input validation in AMD TEE
(Trusted Execution Environment) may allow an attacker with physical access and
control of a Uapp that runs under the bootloader to reveal the contents of the
ASP (AMD Secure Processor) bootloader accessible memory to a serial port,
resulting in a potential loss of integrity.

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

## Which versions are affected by CVE-2021-46759?

It affects 56 products.


Products: Amd Athlon Gold 3150g Firmware, Amd Athlon Gold 3150ge Firmware, Amd Athlon Silver 3050ge Firmware, Amd Ryzen 1200 \(Af\) Firmware, Amd Ryzen 1600 \(Af\) Firmware, Amd Ryzen 2200g Firmware, Amd Ryzen 2200ge Firmware, Amd Ryzen 2300x Firmware, Amd Ryzen 2400g Firmware, Amd Ryzen 2400ge Firmware, Amd Ryzen 2500x Firmware, Amd Ryzen 2600 Firmware, Amd Ryzen 2600e Firmware, Amd Ryzen 2600x Firmware, Amd Ryzen 2700 Firmware, Amd Ryzen 2700e Firmware, Amd Ryzen 2700x Firmware, Amd Ryzen 2920x Firmware, Amd Ryzen 2950x Firmware, Amd Ryzen 2970wx Firmware and 36 more.

## How do I fix CVE-2021-46759?

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

## Is CVE-2021-46759 being exploited?

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

## Other vulnerabilities in AMD Athlon™ 3000 Series Mobile Processors with Radeon™ Graphics   “Pollock”

- [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-2022-23815](https://insights.sbomify.com/CVE-2022-23815/): Memory corruption in AMD Athlon™ 3000 Series Desktop Processors with Radeon™ Graphics (high 7.5)
- [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)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-46759 and fix it if it is affected.

What it is: CVE-2021-46759 is a medium-severity memory corruption vulnerability in AMD Athlon™ 3000 Series Mobile Processors with Radeon™ Graphics   “Pollock”, published on 9 May 2023. 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-2021-46759 in the wild and no public exploit code.

Affected product: AMD Athlon™ 3000 Series Mobile Processors with Radeon™ Graphics   “Pollock”. 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-2021-46759/ (Markdown: https://insights.sbomify.com/CVE-2021-46759/index.md)
```

## Sources

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

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