dbcve.org
Epyc 7763 FirmwareOperating system · Amd

CVE-2021-26349

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
Failure to assign a new report ID to an imported guest may potentially result in an SEV-SNP guest VM being tricked into trusting a dishonest Migration Agent (MA).

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 is an AMD SEV-SNP vulnerability where the guest import process fails to assign a new report ID to an imported guest. In SEV-SNP, report IDs are used for attestation and trust verification between the guest VM and the Migration Agent (MA). When importing a guest, if a new unique report ID is not assigned, a malicious or compromised MA could potentially impersonate a trusted agent, causing the guest to trust a dishonest migration infrastructure.

MitigationApply AMD-provided firmware/hypervisor updates that address SEV-SNP guest import handling to ensure proper report ID assignment. Verify that migration agent implementations correctly handle report ID lifecycle during guest import operations.

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 7763 FirmwareOperating system
Affected:< milanpi-sp3_1.0.0.7
Epyc 7713p FirmwareOperating system
Affected:< milanpi-sp3_1.0.0.7
Epyc 7713 FirmwareOperating system
Affected:< milanpi-sp3_1.0.0.7
Epyc 7663 FirmwareOperating system
Affected:< milanpi-sp3_1.0.0.7
Epyc 7643 FirmwareOperating system
Affected:< milanpi-sp3_1.0.0.7
Epyc 75f3 FirmwareOperating system
Affected:< milanpi-sp3_1.0.0.7
Epyc 7543p FirmwareOperating system
Affected:< milanpi-sp3_1.0.0.7
Epyc 7543 FirmwareOperating system
Affected:< milanpi-sp3_1.0.0.7

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

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 'dmidecode -t processor' or check /proc/cpuinfo to confirm the CPU model is one of: Epyc 7763, 7713p, 7713, 7663, 7643, 75f3, 7543p, or 7543
    Affected if The processor model matches one of the affected Epyc variants listed in the CVE
  2. Check the processor firmware version
    Retrieve the current firmware version using platform-specific tools such as dmidecode, amd-smc-ctl, or through the hypervisor management interface. Compare the installed version against 'milanpi-sp3_1.0.0.7'
    Affected if The firmware version is lower than milanpi-sp3_1.0.0.7
  3. Verify SEV-SNP is enabled
    Check hypervisor or platform configuration for SEV-SNP capability status. On Linux, this may involve checking kvm-intel/sev modules or hypervisor-specific flags via 'cat /sys/module/kvm_amd/parameters/sev_snp' or equivalent hypervisor queries
    Affected if SEV-SNP is enabled and actively in use on the platform
  4. Determine if guest migration or import is used
    Review the hypervisor or cloud infrastructure configuration to determine whether guest VM import or migration operations are performed, as this is the attack vector for the vulnerability
    Affected if Guest import or migration operations are performed on the SEV-SNP-enabled platform

You are affected if your system uses one of the listed AMD Epyc processors with firmware below milanpi-sp3_1.0.0.7, has SEV-SNP enabled, and performs guest import or migration operations.

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/hypervisor updates that address SEV-SNP guest import handling to ensure proper report ID assignment. Verify that migration agent implementations correctly handle report ID lifecycle during guest import operations.

Recommended fix Moderate confidence

milanpi-sp3_1.0.0.7 or later

  1. Contact your AMD Epyc system manufacturer or OEM vendor to obtain the firmware update with version milanpi-sp3_1.0.0.7 or later
  2. Follow the vendor-specific firmware update procedure for your server platform
  3. After updating firmware, verify the SEV-SNP firmware version is milanpi-sp3_1.0.0.7 or later using AMD's provided tools or platform management interfaces
Caveat Firmware updates may require server downtime; ensure proper planning and backup procedures are followed

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

Fix this in Epyc 7763 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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