dbcve.org
Epyc 7003 FirmwareOperating system · Amd

CVE-2021-26335

HIGH · 7.8 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 →
80/100
Remediation priority · High
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
Improper input and range checking in the AMD Secure Processor (ASP) boot loader image header may allow an attacker to use attacker-controlled values prior to signature validation potentially resulting in arbitrary code execution.

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 vulnerability exists in the AMD Secure Processor (ASP) boot loader image header where improper input and range checking allows attacker-controlled values to be used before cryptographic signature validation, potentially enabling arbitrary code execution at the firmware level.

MitigationApply AMD-provided firmware updates for the Secure Processor to remediate this vulnerability; verify that affected systems receive the patch through standard patch management or firmware update processes.

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 AMD Epyc processor model
    Run `dmidecode -t processor` or `lscpu | grep 'Model name'` to confirm the processor is an AMD Epyc 7001, 7002, 7003, 72f3, 7313, 7313p, 7343, or 73f3
    Affected if Processor model matches any of the affected Epyc series listed in the CVE (7001, 7002, 7003, 72f3, 7313, 7313p, 7343, 73f3)
  2. Locate AMD Secure Processor firmware version
    Access the system BIOS/UEFI setup utility and navigate to the AMD Secure Processor configuration section, or use `dmidecode -t bios` to look for ASP firmware information if exposed
    Affected if The ASP firmware version is visible and can be compared against the affected versions
  3. Compare ASP firmware version to affected ranges
    Check the firmware version string against the vulnerable versions: milanpi-sp3 versions < 1.0.0.4, romepi-sp3 versions < 1.0.0.c, naplespi-sp3 versions < 1.0.0.g. Match the firmware variant to your processor generation (milanpi for 7003/72f3/73f3/7313 series, romepi for 7002, naplespi for 7001)
    Affected if The installed ASP firmware version is lower than the specified minimum version for your processor's firmware family

A system is affected if it contains an AMD Epyc 7001, 7002, 7003, 72f3, 7313, 7313p, 7343, or 73f3 processor with AMD Secure Processor firmware below the specified version thresholds (1.0.0.4, 1.0.0.c, or 1.0.0.g depending on the firmware 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 firmware updates for the Secure Processor to remediate this vulnerability; verify that affected systems receive the patch through standard patch management or firmware update processes.

Recommended fix High confidence

milanpi-sp3_1.0.0.4 (Epyc 7003/72f3/7313/7313p/7343/73f3), romepi-sp3_1.0.0.c (Epyc 7002), or naplespi-sp3_1.0.0.g (Epyc 7001)

  1. 1. Identify the specific AMD Epyc processor model in the affected system (7001/Naples, 7002/Rome, or 7003/Milan family)
  2. 2. Check the current firmware version by accessing the BIOS/UEFI settings or using system management tools like IPMI, iLO, or AMD's firmware update utilities
  3. 3. Download the appropriate firmware update from the AMD website (www.amd.com) for the specific Epyc model
  4. 4. Apply the firmware update following AMD's standard firmware update procedure, typically through BIOS flash, AMDs UpdateGA firmware update tool, or via BMC/IPMI interface
  5. 5. Verify the firmware was successfully updated to the fixed version (milanpi-sp3_1.0.0.4 for Epyc 7003/72f3/7313/7313p/7343/73f3, romepi-sp3_1.0.0.c for Epyc 7002, or naplespi-sp3_1.0.0.g for Epyc 7001)
Caveat Firmware updates carry inherent risks; ensure stable power during flash process and have a recovery plan in case of failure

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

Fix this in Epyc 7003 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-26335 — 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-26335 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