dbcve.org
Ryzen 7 5700g FirmwareOperating system · Amd

CVE-2021-46758

MEDIUM · 6.1 CVSS v3.1 Published 2023-11-14
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
Insufficient validation of SPI flash addresses in the ASP (AMD Secure Processor) bootloader may allow an attacker to read data in memory mapped beyond SPI flash resulting in a potential loss of availability and 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

Insufficient validation of SPI flash addresses in the AMD Secure Processor (ASP) bootloader allows an attacker to read data from memory regions mapped beyond the SPI flash boundary. This out-of-bounds read vulnerability in the firmware could lead to exposure of sensitive data and compromise of system integrity.

MitigationApply AMD-provided firmware updates for the Secure Processor through BIOS updates from the system manufacturer, and verify that the ASP bootloader has been patched to the latest version.

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 7 5700g FirmwareOperating system
Affected:< comboam4v2_pi_1.2.0.8
Ryzen 7 5700ge FirmwareOperating system
Affected:< comboam4v2_pi_1.2.0.8
Ryzen 5 5600g FirmwareOperating system
Affected:< comboam4v2_pi_1.2.0.8
Ryzen 5 5600ge FirmwareOperating system
Affected:< comboam4v2_pi_1.2.0.8
Ryzen 3 5300g FirmwareOperating system
Affected:< comboam4v2_pi_1.2.0.8
Ryzen 3 5300ge FirmwareOperating system
Affected:< comboam4v2_pi_1.2.0.8
Ryzen 9 7950x3d FirmwareOperating system
Affected:< comboam5_1.0.0.1
Ryzen 9 7900x3d FirmwareOperating system
Affected:< comboam5_1.0.0.1

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
None
Integrity
High
Availability
High

CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 your AMD processor model
    Run 'wmic cpu get name' or check system documentation to confirm the exact Ryzen model (e.g., Ryzen 7 5700G, Ryzen 9 7950X3D)
    Affected if The processor is any of: Ryzen 7 5700G, Ryzen 7 5700GE, Ryzen 5 5600G, Ryzen 5 5600GE, Ryzen 3 5300G, Ryzen 3 5300GE, Ryzen 9 7950X3D, Ryzen 9 7900X3D
  2. Determine the firmware version for your platform
    Access the BIOS/UEFI setup during boot and look for the AMD Secure Processor (ASP) or Platform Security Processor (PSP) firmware version, or use 'dmidecode -s bios-version' to check the system BIOS version
    Affected if The displayed version is lower than comboam4v2_pi_1.2.0.8 for AM4 processors (Ryzen 5000G series), or lower than comboam5_1.0.0.1 for AM5 processors (Ryzen 7000X3D series)
  3. Confirm the vulnerability scope
    Verify that the system uses SPI flash memory for the AMD Secure Processor bootloader - this is the default configuration for affected systems
    Affected if SPI flash is used and the ASP bootloader version has not been patched to the fixed releases

You are affected if your system uses an AMD Ryzen processor from the affected list and the AMD Secure Processor bootloader firmware version is below comboam4v2_pi_1.2.0.8 (for 5000G series) or below comboam5_1.0.0.1 (for 7000X3D series).

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 AMD-provided firmware updates for the Secure Processor through BIOS updates from the system manufacturer, and verify that the ASP bootloader has been patched to the latest version.

Recommended fix High confidence

comboam4v2_pi_1.2.0.8 (AM4 - Ryzen 5000G series) or comboam5_1.0.0.1 (AM5 - Ryzen 7000X3D series)

  1. Identify your exact motherboard model from the system manufacturer or the motherboard itself
  2. Visit the AMD website (www.amd.com) or your system/motherboard manufacturer's support page
  3. Download the latest BIOS/UEFI firmware update for your specific model
  4. Verify the firmware version includes 'comboam4v2_pi_1.2.0.8' or newer for AM4 processors (Ryzen 5000G series)
  5. Verify the firmware version includes 'comboam5_1.0.0.1' or newer for AM5 processors (Ryzen 7000X3D series)
  6. Follow the manufacturer's instructions to update the BIOS/UEFI - typically via a USB flash drive or through the manufacturer's update utility
  7. Ensure the system has stable power during the update process to prevent bricked firmware
  8. After updating, verify the new firmware version matches or exceeds the required fixed version
Caveat BIOS updates carry a small risk of system unavailability if interrupted or if an incorrect version is applied; ensure you download the exact firmware for your specific motherboard model

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

Fix this in Ryzen 7 5700g Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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