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

> Attackers with malicious Uapp or ABL can overwrite ASP sensor fusion hub data structures, compromising confidentiality and integrity on AMD processors.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 May 2023
- **Updated:** 28 Jan 2025
- **Also known as:** GHSA-m9pv-pmcx-jf3f

## What is CVE-2021-46753?

CVE-2021-46753 is a critical memory corruption vulnerability in AMD Athlon™ 3000 Series Mobile Processors with Radeon™ Graphics   “Pollock”, published on 9 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Failure to validate the length fields of the ASP
(AMD Secure Processor) sensor fusion hub headers may allow an attacker with a
malicious Uapp or ABL to map the ASP sensor fusion hub region and overwrite
data structures leading to a potential loss of confidentiality and integrity.

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

It affects 66 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 46 more.

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

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

## Is CVE-2021-46753 being exploited?

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

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

- [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)
- [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-2021-46753 and fix it if it is affected.

What it is: CVE-2021-46753 is a critical memory corruption vulnerability in AMD Athlon™ 3000 Series Mobile Processors with Radeon™ Graphics   “Pollock”, published on 9 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-46753 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-46753/ (Markdown: https://insights.sbomify.com/CVE-2021-46753/index.md)
```

## Sources

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

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