dbcve.org
Ryzen 5300g FirmwareOperating system · Amd

CVE-2021-46794

HIGH · 7.5 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 →
84/100
Remediation priority · High
Remotely reachable 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
Insufficient bounds checking in ASP (AMD Secure Processor) may allow for an out of bounds read in SMI (System Management Interface) mailbox checksum calculation triggering a data abort, resulting in a potential denial of service.

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 · high confidence

Insufficient bounds checking in the AMD Secure Processor (ASP) firmware allows an out-of-bounds read during SMI (System Management Interface) mailbox checksum calculation. This triggers a data abort exception, causing a denial of service condition. The vulnerability exists in the firmware-level SMI handler and does not require elevated privileges to trigger.

MitigationApply the AMD Secure Processor firmware update provided by AMD through their vendor advisories. System administrators should verify the ASP firmware version and apply patches in accordance with AMD's guidance.

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.6
Ryzen 5300ge FirmwareOperating system
Affected:= cezannepi-fp6_1.0.0.6
Ryzen 5500 FirmwareOperating system
Affected:= cezannepi-fp6_1.0.0.6
Ryzen 5600 FirmwareOperating system
Affected:= cezannepi-fp6_1.0.0.6
Ryzen 5600g FirmwareOperating system
Affected:= cezannepi-fp6_1.0.0.6
Ryzen 5600ge FirmwareOperating system
Affected:= cezannepi-fp6_1.0.0.6
Ryzen 5600x FirmwareOperating system
Affected:= cezannepi-fp6_1.0.0.6
Ryzen 5700g FirmwareOperating system
Affected:= cezannepi-fp6_1.0.0.6

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

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 AMD processor model
    Use system information tools (e.g., 'lscpu' on Linux or 'wmic cpu get name' on Windows) to confirm the CPU is one of the following: Ryzen 5300g, 5300ge, 5500, 5600, 5600g, 5600ge, 5600x, or 5700g.
    Affected if The processor model matches one of the listed affected Ryzen models.
  2. Locate the AMD Secure Processor firmware version
    Check the ASP firmware version using available tools. On Linux, try 'cat /sys/devices/system/cpu/cpu0/cpuidle' or consult AMD's diagnostics. On Windows, access BIOS/UEFI settings or use AMD's System Monitoring utility. Some systems expose PSP version via 'dmidecode -t processor' or AMD's PSP driver information.
    Affected if The ASP firmware version cannot be retrieved or is different from the affected version.
  3. Compare the installed ASP firmware version
    Verify the firmware version reads exactly: cezannepi-fp6_1.0.0.6
    Affected if The installed ASP firmware version equals cezannepi-fp6_1.0.0.6.
  4. Confirm the vulnerability trigger condition
    The flaw occurs during SMI (System Management Interface) mailbox checksum calculation in the firmware-level SMI handler. This is not a configurable setting - it is a code defect that triggers when SMI operations involving the mailbox occur.
    Affected if The system has the affected firmware version AND performs SMI operations (this is inherent to normal system function on affected hardware).

The system is affected if it uses any of the listed Ryzen processors (5300g through 5700g) AND has ASP firmware version cezannepi-fp6_1.0.0.6 installed.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the AMD Secure Processor firmware update provided by AMD through their vendor advisories. System administrators should verify the ASP firmware version and apply patches in accordance with AMD's guidance.

Recommended fix Moderate confidence

BIOS/UEFI update from motherboard vendor containing AMD PSP firmware revision later than cezannepi-fp6_1.0.0.6 (contact AMD or motherboard vendor for exact fixed revision number)

  1. 1. Identify your exact motherboard model from the system vendor (e.g., ASUS, MSI, Gigabyte).
  2. 2. Visit the motherboard vendor's support page for your specific model.
  3. 3. Download the latest BIOS/UEFI firmware update that includes the AMD PSP (Platform Security Processor) firmware patch.
  4. 4. Follow the vendor's instructions to flash the BIOS - typically this requires either: a) Using the vendor's BIOS flashing utility from within Windows/Linux, or b) Creating a USB flash drive with the BIOS file and entering the BIOS/UEFI setup to perform the update.
  5. 5. After the BIOS update completes, verify the ASP/PSP firmware version has been updated from cezannepi-fp6_1.0.0.6 to a newer version.
  6. 6. Alternatively, check AMD's website (www.amd.com) for any standalone AMD PSP/SMU firmware update tools or security bulletins related to CVE-2021-46794.
Caveat Firmware updates carry a small risk of bricking the system if interrupted; ensure stable power and follow vendor flashing instructions exactly. Some BIOS updates may reset configuration settings to defaults.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ryzen 5300g Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-46794 — 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-46794 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