# CVE-2021-46795: Race condition in Ryzen 3000 Series

> A compromised BIOS can trigger a TOCTOU race condition in the TEE OS, leading to out-of-bounds memory reads and potential denial of service.

- **Severity:** Medium 4.7 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/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:** 10 Jan 2023
- **Updated:** 9 Apr 2025
- **Also known as:** GHSA-wfj9-288h-5mpm

## What is CVE-2021-46795?

CVE-2021-46795 is a medium-severity vulnerability in Ryzen 3000 Series , published on 10 Jan 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A TOCTOU (time-of-check to time-of-use) vulnerability exists where an attacker may use a compromised BIOS to cause the TEE OS to read memory out of bounds that could potentially result in a denial of service.

Weakness: CWE-367 (Time-of-check Time-of-use (TOCTOU) Race Condition)

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

It affects 3 products.


Products: Amd Cezannepi-Fp6 Firmware, Amd Comboam4v2 Pi Firmware, Amd Renoirpi-Fp6 Firmware.

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

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

## Is CVE-2021-46795 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2021-46795 is a medium-severity vulnerability in Ryzen 3000 Series , published on 10 Jan 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-46795 in the wild and no public exploit code.

Affected product: Ryzen 3000 Series . 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-46795/ (Markdown: https://insights.sbomify.com/CVE-2021-46795/index.md)
```

## Sources

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

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