dbcve.org
Epyc 7003 FirmwareOperating system · Amd

CVE-2021-26315

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
When the AMD Platform Security Processor (PSP) boot rom loads, authenticates, and subsequently decrypts an encrypted FW, due to insufficient verification of the integrity of decrypted image, arbitrary code may be executed in the PSP when encrypted firmware images are used.

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

AMD Platform Security Processor (PSP) boot rom has an integrity verification flaw during encrypted firmware loading. The boot rom decrypts encrypted firmware images but performs insufficient validation of the decrypted image's integrity before execution, allowing arbitrary code execution within the highly privileged PSP security processor.

MitigationApply AMD-provided firmware/BIOS updates that address the PSP boot rom integrity verification vulnerability. Contact AMD or original equipment manufacturers for applicable microcode and firmware patches.

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 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
Epyc 7413 FirmwareOperating system
Affected:< milanpi-sp3_1.0.0.4
Epyc 7443 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 your AMD Epyc processor model
    Run 'dmidecode -t processor' or check system BIOS/UEFI information to confirm the CPU model number (e.g., Epyc 7313, Epyc 7443)
    Affected if The processor is any of these models: 7003, 72f3, 7313, 7313p, 7343, 73f3, 7413, or 7443
  2. Locate PSP firmware version information
    Access the system BIOS/UEFI setup (typically press Delete/F2 during boot) and look under 'PSP Firmware Version', 'Security', or 'Platform Security Processor' sections; alternatively, use 'dmidecode' if it exposes PSP version data, or consult your system vendor's management interface
    Affected if The PSP firmware version is exposed and can be read from the system
  3. Compare installed PSP firmware version against the fixed version
    Note the displayed PSP firmware version string (format: milanpi-sp3_X.X.X.X) and compare numerically to milanpi-sp3_1.0.0.4
    Affected if The installed version is milanpi-sp3_1.0.0.3 or lower, or the version string is missing/blank indicating an unpatched PSP boot rom

You are affected if you run any of the listed AMD Epyc 7003 series processors AND your PSP firmware version is below milanpi-sp3_1.0.0.4.

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/BIOS updates that address the PSP boot rom integrity verification vulnerability. Contact AMD or original equipment manufacturers for applicable microcode and firmware patches.

Recommended fix High confidence

milanpi-sp3_1.0.0.4

  1. Identify the exact Epyc processor model in the system using manufacturer documentation or system utilities
  2. Check the current PSP firmware version using AMD-provided tools or BMC/IPMI interfaces
  3. Obtain the updated firmware version milanpi-sp3_1.0.0.4 (or later) from AMD's official support website or your system manufacturer
  4. Follow standard firmware update procedures - this typically involves flashing via BMC/IPMI, AMD's PSP firmware update tools, or through system manufacturer provided update utilities
  5. Verify the firmware update was successful by checking the new PSP firmware version
  6. Reboot the system as required by the firmware update process
Caveat Firmware updates carry inherent risk and should be performed following AMD or system manufacturer guidelines; ensure backup and uninterruptible power before proceeding

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

Fix this in Epyc 7003 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,360
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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