dbcve.org
Epyc 7763 FirmwareOperating system · Amd

CVE-2021-46771

HIGH · 7.8 CVSS v3.1 Published 2022-05-10
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
Insufficient validation of addresses in AMD Secure Processor (ASP) firmware system call may potentially lead to arbitrary code execution by a compromised user application.

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

The AMD Secure Processor (ASP) firmware contains a vulnerability in its system call handler where addresses are insufficiently validated. This allows a compromised user application to potentially execute arbitrary code by passing malicious addresses to the ASP firmware through system calls.

MitigationApply the AMD-provided firmware update for the Secure Processor when available. This is a vendor-supplied patch; contact AMD for the specific firmware version addressing CVE-2021-46771.

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.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
Epyc 7543 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 the AMD Epyc processor model
    Run 'dmidecode -t processor' or check /proc/cpuinfo to identify the processor model number
    Affected if The processor is one of the following: Epyc 7763, 7713p, 7713, 7663, 7643, 75f3, 7543p, or 7543
  2. Check the AMD Secure Processor firmware version
    Use the AMD PSP firmware tool or check the BIOS/UEFI firmware version via 'dmidecode -t bios' or the system management interface. The ASP firmware version is typically reported in the system firmware/BIOS information.
    Affected if The ASP firmware version is earlier than milanpi-sp3_1.0.0.4 (the version number will appear in the firmware or BIOS version string)
  3. Verify the system firmware version matches the processor
    Confirm the system firmware (BIOS/UEFI) version installed on the server. In many AMD Epyc systems, the Secure Processor firmware is bundled with the system BIOS/UEFI update.
    Affected if The system firmware version corresponds to a build earlier than the milanpi-sp3_1.0.0.4 release for the affected processor

The system is affected if it uses an AMD Epyc processor from the affected list AND the AMD Secure Processor firmware version is earlier than 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 the AMD-provided firmware update for the Secure Processor when available. This is a vendor-supplied patch; contact AMD for the specific firmware version addressing CVE-2021-46771.

Recommended fix Moderate confidence

milanpi-sp3_1.0.0.4 or later

  1. Identify the exact AMD Epyc processor model in the system using manufacturer documentation or system information tools
  2. Check the current firmware version of the AMD Secure Processor (ASP) using AMD's firmware management tools or system BIOS utilities
  3. Navigate to the AMD website (www.amd.com) and locate the security advisory for CVE-2021-46771
  4. Download the firmware update package (milanpi-sp3_1.0.0.4 or later) specifically for your Epyc processor model
  5. Follow AMD's documented firmware update procedure, which typically involves: running the firmware update utility, ensuring stable power during the update process, and rebooting the system as instructed
  6. After updating, verify the firmware version has been successfully updated to milanpi-sp3_1.0.0.4 or later

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

Fix this in Epyc 7763 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,440
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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