dbcve.org
Ryzen 5300g FirmwareOperating system · Amd

CVE-2021-46759

MEDIUM · 6.1 CVSS v3.1 Published 2023-05-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
66/100
Remediation priority · Elevated
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Improper syscall input validation in AMD's Trusted Execution Environment (TEE) allows an attacker with physical access and control of a Uapp running under the bootloader to dump ASP (AMD Secure Processor) bootloader memory contents to a serial port, potentially compromising system integrity.

MitigationApply AMD-provided firmware updates for the TEE; restrict physical access to affected systems and limit control of Uapps running under the bootloader as compensating controls until the patch is applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Ryzen 5300g FirmwareOperating system
Affected:= cezannepi-fp6_1.0.0.8= comboam4v2_pi_1.2.0.5
Ryzen 5300ge FirmwareOperating system
Affected:= cezannepi-fp6_1.0.0.8= comboam4v2_pi_1.2.0.5
Ryzen 5500 FirmwareOperating system
Affected:= cezannepi-fp6_1.0.0.8= comboam4v2_pi_1.2.0.5
Ryzen 5600 FirmwareOperating system
Affected:= cezannepi-fp6_1.0.0.8= comboam4v2_pi_1.2.0.5
Ryzen 5600g FirmwareOperating system
Affected:= cezannepi-fp6_1.0.0.8= comboam4v2_pi_1.2.0.5
Ryzen 5600ge FirmwareOperating system
Affected:= cezannepi-fp6_1.0.0.8= comboam4v2_pi_1.2.0.5
Ryzen 5600x FirmwareOperating system
Affected:= cezannepi-fp6_1.0.0.8= comboam4v2_pi_1.2.0.5
Ryzen 5700g FirmwareOperating system
Affected:= cezannepi-fp6_1.0.0.8= comboam4v2_pi_1.2.0.5

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Physical
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the processor model
    Run 'wmic cpu get name' (Windows) or 'cat /proc/cpuinfo' (Linux) and look for Ryzen 5300g, 5300ge, 5500, 5600, 5600g, 5600ge, 5600x, or 5700g
    Affected if The processor is any of these eight models and the ASP firmware version matches the affected versions
  2. Check the BIOS/UEFI firmware version
    Run 'wmic bios get smbiosbiosversion' (Windows) or 'dmidecode -s bios-version' (Linux). AMD ASP firmware updates are typically delivered through BIOS updates.
    Affected if The BIOS version corresponds to a release that includes the older unpatched ASP firmware versions (cezannepi-fp6_1.0.0.8 or comboam4v2_pi_1.2.0.5)
  3. Query the AMD Secure Processor firmware version
    Use AMD Ryzen Master software or a system information tool that reports AMD SP (Secure Processor) or PSP firmware version. On Linux, check 'cat /sys/devices/platform/amd_pipsppinfo/fw_version' if available.
    Affected if The reported ASP/PSP firmware version is exactly cezannepi-fp6_1.0.0.8 or comboam4v2_pi_1.2.0.5
  4. Verify physical access exposure
    Assess whether the system is in a location where an attacker could gain physical access and connect to a serial port header on the motherboard.
    Affected if The system is physically accessible to untrusted individuals
  5. Determine if Uapps run under the bootloader
    Review any custom or third-party user applications (Uapps) that execute within the AMD TEE context under the bootloader. Check system documentation or AMD developer resources for loaded Uapps.
    Affected if Any Uapp with serial port output capability runs under the bootloader and could be controlled by an attacker

The system is affected if it uses one of the listed Ryzen processors, has ASP firmware version cezannepi-fp6_1.0.0.8 or comboam4v2_pi_1.2.0.5, and an attacker could physically access the system and control a Uapp running under the bootloader.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply AMD-provided firmware updates for the TEE; restrict physical access to affected systems and limit control of Uapps running under the bootloader as compensating controls until the patch is applied.

Fix this in Ryzen 5300g Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,416.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-46759 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-46759 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data