dbcve.org
Epyc 7232p FirmwareOperating system · Amd

CVE-2021-26373

MEDIUM · 5.5 CVSS v3.1 Published 2022-05-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
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 bound checks in the System Management Unit (SMU) may result in a system voltage malfunction that could result in denial of resources and/or possibly 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 · moderate confidence

Insufficient bound checking in AMD's System Management Unit (SMU) firmware allows malformed voltage requests to pass validation, potentially causing the SMU to set incorrect voltage levels. This voltage malfunction can destabilize the processor and connected components, leading to system resource unavailability or complete denial of service.

MitigationApply vendor-supplied SMU/firmware microcode updates from AMD. For systems where updates are unavailable, implement monitoring for voltage anomalies and consider system replacement if sustained stability is required. Test firmware updates in non-production environments before deployment.

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 7232p FirmwareOperating system
Affected:< romepi-sp3_1.0.0.d
Epyc 7302p FirmwareOperating system
Affected:< romepi-sp3_1.0.0.d
Epyc 7402p FirmwareOperating system
Affected:< romepi-sp3_1.0.0.d
Epyc 7502p FirmwareOperating system
Affected:< romepi-sp3_1.0.0.d
Epyc 7702p FirmwareOperating system
Affected:< romepi-sp3_1.0.0.d
Epyc 7252 FirmwareOperating system
Affected:< romepi-sp3_1.0.0.d
Epyc 7262 FirmwareOperating system
Affected:< romepi-sp3_1.0.0.d
Epyc 7272 FirmwareOperating system
Affected:< romepi-sp3_1.0.0.d

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

CVSS:3.1/AV:L/AC:L/PR:L/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 processor model
    Use 'dmidecode -t processor' or check system BIOS/UEFI information to confirm the installed CPU is one of these models: Epyc 7232p, 7302p, 7402p, 7502p, 7702p, 7252, 7262, or 7272
    Affected if The installed CPU matches any of these eight Epyc model numbers
  2. Retrieve the SMU firmware version
    Access the BMC/IPMI interface or use AMD-specific tools (such as 'ipmi' or vendor-provided firmware utilities) to query the System Management Unit firmware version. The version string typically appears as 'romepi-sp3_X.X.X.X' or similar
    Affected if The SMU firmware version cannot be determined or is not visible through standard interfaces
  3. Compare firmware version to the affected range
    If the SMU firmware version is obtained, compare it against 'romepi-sp3_1.0.0.d'. Versions numerically lower than this string (such as earlier 1.0.0.x releases) are considered vulnerable
    Affected if The installed firmware version string is less than 'romepi-sp3_1.0.0.d' (for example, romepi-sp3_1.0.0.c or earlier)
  4. Check for voltage management activity
    Monitor system voltage readings using IPMI sensors, BMC logs, or operating system tools (like 'ipmiutil sensor' or 'lm_sensors'). Look for any voltage anomalies or unexpected voltage values being reported by the SMU
    Affected if Sustained voltage irregularities are observed, which may indicate exploitation of the bound checking flaw

You are affected if you have any of the listed Epyc models (7232p through 7272) running SMU firmware versions earlier than romepi-sp3_1.0.0.d, with the vulnerability manifestable through the SMU voltage request mechanism.

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 vendor-supplied SMU/firmware microcode updates from AMD. For systems where updates are unavailable, implement monitoring for voltage anomalies and consider system replacement if sustained stability is required. Test firmware updates in non-production environments before deployment.

Recommended fix High confidence

romepi-sp3_1.0.0.d or later

  1. 1. Identify the exact AMD Epyc model number in the affected system using either BIOS information, system inventory, or physical label inspection.
  2. 2. Navigate to the AMD Epyc support page at www.amd.com and locate the firmware download section for the specific processor model.
  3. 3. Download the latest System Management Unit (SMU) firmware package (version romepi-sp3_1.0.0.d or later) compatible with the affected processor.
  4. 4. Follow AMD's standard firmware update procedure, which typically involves: a) Backup current system configuration, b) Run the firmware update utility, c) Allow the update process to complete without interruption, d) Reboot the system to apply the new firmware.
  5. 5. After reboot, verify the SMU firmware version has been updated to romepi-sp3_1.0.0.d or later using AMD's diagnostic tools or system management interfaces.

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

Fix this in Epyc 7232p Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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