dbcve.org
Ryzen 7 5700g FirmwareOperating system · Amd

CVE-2023-20596

CRITICAL · 9.8 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 →
100/100
Remediation priority · Urgent
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
Improper input validation in the SMM Supervisor may allow an attacker with a compromised SMI handler to gain Ring0 access potentially leading to arbitrary code execution.

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

This is an AMD processor vulnerability in the SMM (System Management Mode) Supervisor involving improper input validation. An attacker who has already compromised an SMI (System Management Interrupt) handler can exploit this flaw to escape the constrained SMM environment, escalate to Ring0 privileges, and execute arbitrary code with the highest CPU privilege level.

MitigationApply AMD processor firmware/BIOS updates as provided by AMD for affected CPU models; audit and verify integrity of SMI handlers to detect any existing compromise.

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_1.2.0.b
Ryzen 7 5700ge FirmwareOperating system
Affected:< comboam4v2_1.2.0.b
Ryzen 5 5600g FirmwareOperating system
Affected:< comboam4v2_1.2.0.b
Ryzen 5 5600ge FirmwareOperating system
Affected:< comboam4v2_1.2.0.b
Ryzen 3 5300g FirmwareOperating system
Affected:< comboam4v2_1.2.0.b
Ryzen 3 5300ge FirmwareOperating system
Affected:< comboam4v2_1.2.0.b
Ryzen 9 7950x3d FirmwareOperating system
Affected:< comboam5pi_1.0.8.0
Ryzen 9 7950x FirmwareOperating system
Affected:< comboam5pi_1.0.8.0

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 Ryzen processor model
    Use system information tools such as 'wmic cpu get name' on Windows, 'cat /proc/cpuinfo' on Linux, or check the BIOS setup screen to determine the exact CPU model number
    Affected if The CPU is any of these models: Ryzen 7 5700g, Ryzen 7 5700ge, Ryzen 5 5600g, Ryzen 5 5600ge, Ryzen 3 5300g, Ryzen 3 5300ge, Ryzen 9 7950x3d, or Ryzen 9 7950x
  2. Determine your BIOS/firmware version
    Check the BIOS version using 'dmidecode -s bios-version' on Linux, 'wmic bios get smbiosbiosversion' on Windows, or access the BIOS setup and look for the BIOS revision or firmware version information
    Affected if The BIOS/firmware version cannot be determined or is visible for comparison against the thresholds
  3. Compare firmware version against affected thresholds
    For Ryzen 5000g-series (5700g, 5700ge, 5600g, 5600ge, 5300g, 5300ge): compare your firmware version to comboam4v2_1.2.0.b. For Ryzen 7000-series (7950x3d, 7950x): compare your firmware version to comboam5pi_1.0.8.0
    Affected if Your firmware version is lower than the threshold for your specific CPU model (comboam4v2_1.2.0.b for 5000g-series or comboam5pi_1.0.8.0 for 7000-series)

You are affected if you own one of the listed AMD Ryzen CPU models and your BIOS/firmware version is below the specified threshold for that processor family.

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 processor firmware/BIOS updates as provided by AMD for affected CPU models; audit and verify integrity of SMI handlers to detect any existing compromise.

Recommended fix High confidence

BIOS/firmware update to comboam4v2_1.2.0.b (AM4) or comboam5pi_1.0.8.0 (AM5)

  1. Identify your specific AMD Ryzen processor model and determine if it uses AM4 or AM5 platform
  2. Check current BIOS/firmware version installed on the system
  3. Visit the official AMD support website and navigate to the drivers and support page for your specific processor/model
  4. Download the BIOS/firmware update that contains the fix: comboam4v2_1.2.0.b for AM4 platforms (Ryzen 5000G series) or comboam5pi_1.0.8.0 for AM5 platforms (Ryzen 7000 series)
  5. Follow AMD's recommended firmware update process, which typically involves either using the AMD Ryzen Master utility or creating a USB-based BIOS update flash drive
  6. Reboot the system and verify the firmware has been successfully updated to the fixed version
  7. Confirm the new firmware version is comboam4v2_1.2.0.b or higher for AM4, or comboam5pi_1.0.8.0 or higher for AM5
Caveat Firmware updates carry inherent risk of system damage if interrupted; ensure stable power and follow update instructions precisely; some older hardware configurations may not be compatible with newer firmware

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

Fix this in Ryzen 7 5700g Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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