dbcve.org
Epyc 7232p FirmwareOperating system · Amd

CVE-2021-26325

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
Insufficient input validation in the SNP_GUEST_REQUEST command may lead to a potential data abort error and a 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

This vulnerability exists in AMD's SEV-SNP (Secure Nested Pages) virtualization technology. The SNP_GUEST_REQUEST hypervisor command lacks proper input validation, allowing potentially malformed requests to trigger a data abort error, which can cause the hypervisor to crash and result in a denial of service.

MitigationApply AMD-provided firmware/microcode updates that address this vulnerability. Affected systems should be identified and updated during planned maintenance windows, with particular attention to hypervisors using SEV-SNP features.

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.c
Epyc 7763 FirmwareOperating system
Affected:< milanpi-sp3_1.0.0.4
Epyc 7713p FirmwareOperating system
Affected:< milanpi-sp3_1.0.0.4
Epyc 7713 FirmwareOperating system
Affected:< milanpi-sp3_1.0.0.4
Epyc 7663 FirmwareOperating system
Affected:< milanpi-sp3_1.0.0.4
Epyc 7643 FirmwareOperating system
Affected:< milanpi-sp3_1.0.0.4
Epyc 75f3 FirmwareOperating system
Affected:< milanpi-sp3_1.0.0.4
Epyc 7543p 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
    Run 'lscpu' or 'cat /proc/cpuinfo' and look for the processor name in the 'Model name' field
    Affected if The processor is one of the affected models: Epyc 7232p, 7763, 7713p, 7713, 7663, 7643, 75f3, or 7543p
  2. Verify SEV-SNP is enabled in the hypervisor
    Check hypervisor configuration (e.g., for KVM: look for SEV-SNP or SEV related flags in /sys/module/kvm_amd/parameters/, or check if 'sev' or 'sev-snp' appears in hypervisor boot options)
    Affected if SEV-SNP feature is enabled or loaded on the system
  3. Check the current firmware version
    Use 'dmidecode -s bios-version' or vendor-specific tools (such as AMD's firmware update utilities) to retrieve the firmware version string
    Affected if The firmware version is lower than 'romepi-sp3_1.0.0.c' for Epyc 7232p or lower than 'milanpi-sp3_1.0.0.4' for Milan-based processors (7763, 7713p, 7713, 7663, 7643, 75f3, 7543p)
  4. Confirm hypervisor platform type
    Verify the system is running as a hypervisor (e.g., check for hypervisor brand via 'systemd-detect-virt' or 'lscpu' under 'Hypervisor' field)
    Affected if The system is a hypervisor hosting VMs and uses AMD SEV-SNP

A system is affected if it runs an AMD Epyc processor from the affected list, has SEV-SNP enabled in the hypervisor, and has firmware version below the specified thresholds.

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 that address this vulnerability. Affected systems should be identified and updated during planned maintenance windows, with particular attention to hypervisors using SEV-SNP features.

Recommended fix Moderate confidence

milanpi-sp3_1.0.0.4 (or romepi-sp3_1.0.0.c for Epyc 7232p)

  1. 1. Identify the exact AMD Epyc processor model in your system using system inventory or BIOS information
  2. 2. Navigate to the AMD support website (www.amd.com) and locate the firmware download page for your specific Epyc processor model
  3. 3. Download the appropriate firmware update: For Epyc 7232p, obtain version romepi-sp3_1.0.0.c or later; For Epyc 7763, 7713p, 7713, 7663, 7643, 75f3, or 7543p, obtain version milanpi-sp3_1.0.0.4 or later
  4. 4. Review the firmware update release notes for any prerequisites or specific update instructions
  5. 5. Apply the firmware update following the vendor's recommended procedure, which typically involves using the AMD firmware update utility or your server manufacturer's management interface (BMC/IPMI)
  6. 6. After updating, verify the firmware version has been correctly applied and reboot the system if required
Caveat Firmware updates may require system downtime and should be tested in a non-production environment first; ensure proper backup and rollback procedures are in place

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
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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