dbcve.org
Epyc 7h12 FirmwareOperating system · Amd

CVE-2023-20532

MEDIUM · 5.3 CVSS v3.1 Published 2023-01-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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 input validation in the SMU may allow an attacker to improperly lock resources, potentially resulting in a 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

This is an input validation vulnerability in AMD's System Management Unit (SMU) firmware. The insufficient input validation allows an attacker to improperly lock system resources through the SMU interface, causing a denial of service condition.

MitigationApply AMD-provided firmware/BIOS updates that address the SMU input validation flaw. Verify SMU resource locking behavior functions normally after patching.

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
Epyc 7h12 FirmwareOperating system
Affected:< romepi_1.0.0.c
Epyc 7f72 FirmwareOperating system
Affected:< romepi_1.0.0.c
Epyc 7f52 FirmwareOperating system
Affected:< romepi_1.0.0.c
Epyc 7f32 FirmwareOperating system
Affected:< romepi_1.0.0.c
Epyc 7742 FirmwareOperating system
Affected:< romepi_1.0.0.c
Epyc 7702p FirmwareOperating system
Affected:< romepi_1.0.0.c
Epyc 7702 FirmwareOperating system
Affected:< romepi_1.0.0.c
Epyc 7662 FirmwareOperating system
Affected:< romepi_1.0.0.c

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
Low

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

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 Epyc processor model
    Run 'dmidecode -t processor' or check /proc/cpuinfo to list the installed CPU model. Look for model numbers matching the affected list: 7h12, 7f72, 7f52, 7f32, 7742, 7702p, 7702, or 7662.
    Affected if The installed processor is any of these Epyc models.
  2. Determine the SMU firmware version
    Access the server's BMC/IPMI interface or BIOS setup. Under the BIOS or firmware information section, look for the SMU firmware version string. On AMD servers, this may appear as 'romepi' version or similar SMU firmware identifier. Alternatively, use vendor-specific tools such as 'amdsmu' or IPMI commands like 'ipmitool raw' to query SMU version if available.
    Affected if The SMU firmware version string is visible and can be compared.
  3. Compare firmware version against the affected range
    If you obtained the SMU firmware version (typically a string containing 'romepi' and a version number), compare it to the threshold version 'romepi_1.0.0.c'. Any version less than this (for example, romepi_0.x.x or earlier builds) is in the affected range.
    Affected if The SMU firmware version is < romepi_1.0.0.c.
  4. Check for abnormal SMU resource behavior
    Monitor system management traffic through the BMC. Look for signs of SMU resource locks: unexpected throttling, fan speed anomalies, power capping failures, or inability to change voltage/frequency settings via the SMU interface. Review system event logs for SMU-related errors or lock warnings.
    Affected if The system exhibits unexplained resource locking or SMU interface errors.

You are affected if you have an AMD Epyc 7h12, 7f72, 7f52, 7f32, 7742, 7702p, 7702, or 7662 processor with SMU firmware version older than romepi_1.0.0.c.

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/BIOS updates that address the SMU input validation flaw. Verify SMU resource locking behavior functions normally after patching.

Recommended fix High confidence

romepi_1.0.0.c or later firmware version

  1. 1. Identify the exact Epyc processor model in the system using BIOS or system inventory tools
  2. 2. Download the latest BIOS/firmware update from AMD's support website for the specific processor model
  3. 3. Apply the firmware update using the vendor's recommended method (typically via BIOS flash utility, BMC update, or AMD's firmware update tools)
  4. 4. Verify the SMU firmware has been updated to version romepi_1.0.0.c or later
  5. 5. Reboot the system to ensure the new firmware is properly initialized
Caveat Firmware updates carry inherent risks; ensure backups are in place and follow AMD's recommended update procedure for your specific platform

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

Fix this in Epyc 7h12 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
17.0 hours of engineering $3,020
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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