dbcve.org
Epyc 7232p FirmwareOperating system · Amd

CVE-2021-26372

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 related to PCIE in the System Management Unit (SMU) may result in access to an invalid address space that could result in 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 checks in the System Management Unit (SMU) related to PCIE operations allow an attacker to trigger access to invalid address spaces, potentially causing the system to crash or become unresponsive (denial of service). This is a firmware-level vulnerability in the SMU, which manages power and performance features.

MitigationApply vendor-supplied firmware/BIOS updates from the hardware manufacturer (typically AMD for SMU firmware). This may require updating the System Management Unit firmware through the BIOS/UEFI or vendor-specific update utilities.

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 AMD Epyc processor model
    Run `dmidecode -t processor` or `cat /proc/cpuinfo | grep 'model name'` to confirm the CPU is one of the affected models: 7232p, 7302p, 7402p, 7502p, 7702p, 7252, 7262, or 7272
    Affected if The installed CPU model matches one of the listed affected Epyc processors
  2. Retrieve the SMU firmware version
    Use `dmidecode -t bios` to read the BIOS firmware version, or use vendor-specific tools such as AMD's firmware update utility (e.g., `amd_smu_info` or IPMI commands) to query the System Management Unit firmware version directly. The version string typically appears as a build identifier like 'romepi-sp3_x.x.x.x'
    Affected if The SMU firmware version cannot be retrieved or shows a version string below 'romepi-sp3_1.0.0.d'
  3. Compare firmware version against the affected threshold
    If the SMU firmware version is readable, compare the full version string numerically or lexicographically against 'romepi-sp3_1.0.0.d'. Ensure the comparison accounts for the full build identifier including any suffix letters
    Affected if The displayed firmware version is older than romepi-sp3_1.0.0.d (e.g., romepi-sp3_0.9.x or any earlier build)
  4. Check for vendor BIOS/UEFI updates
    Consult the system BIOS/UEFI setup (accessible via boot-time key such as F2 or Delete) or use the server management interface (BMC/IPMI) to review the current firmware revision strings listed under the SMU or System Firmware section
    Affected if The BMC/BIOS firmware revision log shows an SMU version prior to romepi-sp3_1.0.0.d

A system is affected if it runs any of the listed AMD Epyc models with SMU firmware versions earlier than romepi-sp3_1.0.0.d.

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 firmware/BIOS updates from the hardware manufacturer (typically AMD for SMU firmware). This may require updating the System Management Unit firmware through the BIOS/UEFI or vendor-specific update utilities.

Recommended fix High confidence

romepi-sp3_1.0.0.d or later

  1. 1. Identify the exact AMD Epyc processor model in the system using CPU-Z or system inventory tools
  2. 2. Navigate to the AMD support website and locate the firmware download section for the specific Epyc processor model
  3. 3. Download the System Management Unit (SMU) firmware version romepi-sp3_1.0.0.d or later
  4. 4. Follow AMD's documented firmware update procedure, which typically requires accessing the BMC/IPMI interface or using AMD's firmware update utilities
  5. 5. Verify the firmware version has been successfully applied after the update process completes
Caveat Firmware updates may require system downtime and should be tested in a staging environment before production deployment

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

Fix this in Epyc 7232p Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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