# CVE-2021-46757: Memory corruption in AMD Ryzen™ Embedded 5000

> A malicious Trusted Application can exploit insufficient memory checks in AMD Secure OS to read or write kernel memory, leading to privilege escalation.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Feb 2024
- **Updated:** 7 May 2025
- **Also known as:** GHSA-5fqp-6xx2-943w

## What is CVE-2021-46757?

CVE-2021-46757 is a high-severity memory corruption vulnerability in AMD Ryzen™ Embedded 5000, published on 13 Feb 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Insufficient checking of memory buffer in ASP
Secure OS may allow an attacker with a malicious TA to read/write to the ASP
Secure OS kernel virtual address space potentially leading to privilege
escalation.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 10 products.


Products: Amd Ryzen Embedded 5600e Firmware, Amd Ryzen Embedded 5800e Firmware, Amd Ryzen Embedded 5900e Firmware, Amd Ryzen Embedded 5950e Firmware, Amd Ryzen Embedded R2312 Firmware, Amd Ryzen Embedded R2314 Firmware, Amd Ryzen Embedded V2516 Firmware, Amd Ryzen Embedded V2546 Firmware, Amd Ryzen Embedded V2718 Firmware, Amd Ryzen Embedded V2748 Firmware.

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

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

## Is CVE-2021-46757 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2021-46757 is a high-severity memory corruption vulnerability in AMD Ryzen™ Embedded 5000, published on 13 Feb 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-2021-46757 in the wild and no public exploit code.

Affected product: AMD Ryzen™ Embedded 5000. 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-46757/ (Markdown: https://insights.sbomify.com/CVE-2021-46757/index.md)
```

## Sources

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

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