dbcve.org
Epyc 7003 FirmwareOperating system · Amd

CVE-2021-26330

MEDIUM · 5.5 CVSS v3.1 Published 2021-11-16
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
AMD System Management Unit (SMU) may experience a heap-based overflow which may result in a loss of resources.

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

AMD System Management Unit (SMU) firmware contains a heap-based buffer overflow vulnerability. The SMU is a microcontroller within AMD processors that handles power management and system management tasks. A heap overflow could allow an attacker to corrupt adjacent memory structures, potentially leading to loss of resources or denial of service.

MitigationApply AMD-provided BIOS/firmware updates that address this vulnerability. In enterprise environments, test updates in controlled settings before deploying broadly due to the critical nature of SMU firmware.

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 7003 FirmwareOperating system
Affected:< milanpi-sp3_1.0.0.4
Epyc 7002 FirmwareOperating system
Affected:< romepi-sp3_1.0.0.c
Epyc 7001 FirmwareOperating system
Affected:< naplespi-sp3_1.0.0.g
Epyc 72f3 FirmwareOperating system
Affected:< milanpi-sp3_1.0.0.4
Epyc 7313 FirmwareOperating system
Affected:< milanpi-sp3_1.0.0.4
Epyc 7313p FirmwareOperating system
Affected:< milanpi-sp3_1.0.0.4
Epyc 7343 FirmwareOperating system
Affected:< milanpi-sp3_1.0.0.4
Epyc 73f3 FirmwareOperating system
Affected:< milanpi-sp3_1.0.0.4

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
    Use the command 'dmidecode -t processor | grep -i "family"' or check BIOS/UEFI processor information to determine if the system uses an Epyc 7003, 7002, or 7001 series processor
    Affected if The processor is an AMD Epyc 7003, 7002, 7001, 72f3, 7313, 7313p, 7343, or 73f3 model
  2. Determine the installed SMU firmware version
    Access the BIOS/UEFI setup under the 'AMD CBS' or 'CPU Configuration' menu to locate the SMU firmware version, or use IPMI/BMC web interface under 'Firmware Inventory' if remote management is available
    Affected if The SMU firmware version is visible and can be compared to the affected version thresholds
  3. Compare firmware version against affected ranges
    For Epyc 7003/72f3/7313/7313p/7343/73f3: compare the installed version to milanpi-sp3_1.0.0.4. For Epyc 7002: compare to romepi-sp3_1.0.0.c. For Epyc 7001: compare to naplespi-sp3_1.0.0.g
    Affected if The installed firmware version is lower than the specified threshold for your processor model (for example, any version below milanpi-sp3_1.0.0.4 on Milan-based processors)
  4. Verify SMU firmware update availability
    Check AMD's product support pages or your server vendor's firmware download section for your specific Epyc model to see if a newer firmware version addressing this CVE is available
    Affected if A newer firmware version addressing the vulnerability is available but not yet applied

A system is affected if it runs an AMD Epyc 7003, 7002, or 7001 series processor with SMU firmware version lower than the threshold specific to 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-provided BIOS/firmware updates that address this vulnerability. In enterprise environments, test updates in controlled settings before deploying broadly due to the critical nature of SMU firmware.

Recommended fix High confidence

SMU firmware version milanpi-sp3_1.0.0.4 (Milan), romepi-sp3_1.0.0.c (Rome), or naplespi-sp3_1.0.0.g (Naples) depending on processor generation

  1. 1. Identify the exact AMD Epyc processor model in the system using standard system information tools (e.g., dmidecode, lscpu, or BIOS information).
  2. 2. Visit the AMD website (www.amd.com) and navigate to the AMD Epyc processor support or firmware download page.
  3. 3. Locate the appropriate System Management Unit (SMU) firmware for your specific Epyc generation: Milan (7003 series, 72f3, 7313, 7313p, 7343, 73f3), Rome (7002 series), or Naples (7001 series).
  4. 4. Download the specific firmware version that resolves the vulnerability: milanpi-sp3_1.0.0.4 for Milan-based processors, romepi-sp3_1.0.0.c for Rome-based processors, or naplespi-sp3_1.0.0.g for Naples-based processors.
  5. 5. Follow AMD's documented firmware update procedure, typically involving the AMD Update Tool or through BIOS/UEFI update mechanisms provided by the server manufacturer.
  6. 6. Verify the SMU firmware version has been successfully updated after the update process completes.
Caveat Firmware updates carry risk; an interrupted update could render the system non-functional - follow vendor instructions precisely and ensure stable power

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

Fix this in Epyc 7003 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA5.0 h
33.0 hours of engineering $5,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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