dbcve.org
Epyc 7232p FirmwareOperating system · Amd

CVE-2021-26376

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 checks in System Management Unit (SMU) FeatureConfig may result in reenabling features potentially resulting in denial of resources and/or 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

Vulnerability in AMD's System Management Unit (SMU) FeatureConfig where insufficient validation checks allow features to be reenabled after being disabled, potentially causing denial of resources or denial of service. This is a firmware-level issue affecting AMD processors with SMU functionality.

MitigationApply AMD-provided firmware/microcode updates (BIOS/UEFI updates) that address this SMU vulnerability. Verify that affected systems receive the vendor patch and confirm successful application.

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
    Check the installed CPU by running `dmidecode -s processor-version` or by inspecting `/proc/cpuinfo` for the model name
    Affected if The processor is one of: Epyc 7232p, 7302p, 7402p, 7502p, 7702p, 7252, 7262, or 7272
  2. Retrieve the current system firmware version
    Check the BIOS/UEFI firmware version via `dmidecode -s bios-version` or through the BMC/IPMI interface if present, using `ipmitool -I lanplus -H <bmc_ip> -U <user> raw` command to query SMU firmware version
    Affected if The firmware version is listed as anything earlier than romepi-sp3_1.0.0.d, or the version string cannot be confirmed as romepi-sp3_1.0.0.d or later
  3. Locate the SMU FeatureConfig settings
    Access the BIOS/UEFI setup menu during boot and navigate to the System Management Unit or Feature Configuration settings section; alternatively, use AMD-specific tools like `amd_smu` or `amdcfg` if available for the platform
    Affected if FeatureConfig allows re-enabling of features after they have been disabled, indicating insufficient validation checks are present

The system is affected if it runs any of the listed AMD Epyc models with firmware versions earlier than romepi-sp3_1.0.0.d, where the SMU FeatureConfig permits features to be re-enabled after being disabled.

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/microcode updates (BIOS/UEFI updates) that address this SMU vulnerability. Verify that affected systems receive the vendor patch and confirm successful application.

Recommended fix High confidence

romepi-sp3_1.0.0.d or later

  1. Obtain the updated SMU firmware (romepi-sp3_1.0.0.d or later) from the official AMD website or your server manufacturer support portal
  2. Verify the firmware is compatible with your specific Epyc processor model
  3. Follow your server manufacturer's standard BIOS/ firmware update procedure, which typically involves either: a) Using the manufacturer's firmware update utility, or b) Flashing via BIOS interface if SMU firmware can be updated through BIOS settings
  4. Ensure stable power during the firmware update process to prevent update failure
  5. After updating, verify the firmware version has been applied successfully

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

Fix this in Epyc 7232p Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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