dbcve.org
Epyc 7773x FirmwareOperating system · Amd

CVE-2023-31346

MEDIUM · 6.0 CVSS v3.1 Published 2024-02-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/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 initialize memory in SEV Firmware may allow a privileged attacker to access stale data from other guests.

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

A memory initialization failure in AMD SEV (Secure Encrypted Virtualization) firmware allows a privileged attacker to access stale data remaining in memory from previous guest VMs. This cross-tenant data leakage occurs because memory pages are not properly zeroed before being allocated to new guests.

MitigationApply AMD-provided SEV firmware updates to affected hosts. Review and re-encrypt sensitive guest VMs after patching to ensure no stale data remains accessible.

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 7773x FirmwareOperating system
Affected:< milanpi_1.0.0.c
Epyc 7763 FirmwareOperating system
Affected:< milanpi_1.0.0.c
Epyc 7713 FirmwareOperating system
Affected:< milanpi_1.0.0.c
Epyc 7713p FirmwareOperating system
Affected:< milanpi_1.0.0.c
Epyc 7663 FirmwareOperating system
Affected:< milanpi_1.0.0.c
Epyc 7663p FirmwareOperating system
Affected:< milanpi_1.0.0.c
Epyc 7643 FirmwareOperating system
Affected:< milanpi_1.0.0.c
Epyc 7643p FirmwareOperating system
Affected:< milanpi_1.0.0.c

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
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:N/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
    Run 'cat /proc/cpuinfo | grep 'model name' or use 'dmidecode -s processor-version' to confirm the CPU is one of the affected models: Epyc 7773x, 7763, 7713, 7713p, 7663, 7663p, 7643, or 7643p
    Affected if The processor is NOT one of these eight Epyc model numbers, as only those specific Milan-generation processors are affected
  2. Check the SEV firmware version
    Read the SEV firmware version from the AMD SEV interface. On a Linux host with SEV enabled, check the file /sys/firmware/amd/sev or use 'cat /sys/firmware/amd/sev/hardware_id' if available. Alternatively, use the 'amd-sev' tool or check the BIOS/UEFI firmware version information for the 'milanpi' firmware build string
    Affected if The SEV firmware version is earlier than milanpi_1.0.0.c, meaning the build string shows a version less than 1.0.0.c
  3. Confirm SEV is enabled and in use
    Check if SEV is actively enabled on the host. On KVM hosts, verify by checking 'cat /sys/module/kvm_amd/parameters/sev' returns 1, or verify guest VM definitions include SEV encryption (virsh dumpxml for each guest should show '<os><loader>...</loader></os>' with sev elements)
    Affected if SEV is NOT enabled or no guests are using SEV encryption, as the flaw only affects memory pages allocated to SEV-encrypted virtual machines

You are affected if your host runs one of the eight listed AMD Epyc Milan processors, has SEV firmware version earlier than milanpi_1.0.0.c, and has SEV-encrypted guest VMs running or planned, as the unzeroed memory pages could leak data from previous guest tenants.

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 SEV firmware updates to affected hosts. Review and re-encrypt sensitive guest VMs after patching to ensure no stale data remains accessible.

Recommended fix Moderate confidence

milanpi_1.0.0.c or later firmware version

  1. Obtain the latest AMD Epyc firmware update from the AMD website or your server hardware vendor (e.g., Dell, HPE, Lenovo)
  2. Verify the current firmware version of the affected Epyc processor using the system management interface (BMC/iLO/IPMI)
  3. Download the firmware update package specific to your server model and Epyc processor generation (Milan)
  4. Follow the vendor's recommended firmware update procedure, typically via BMC web interface or command-line tools
  5. Apply the firmware update ensuring stable power throughout the process
  6. Verify the updated firmware version matches or exceeds milanpi_1.0.0.c after the update completes
Caveat Firmware updates carry risk of system unavailability; ensure backups and maintenance windows are planned; verify vendor compatibility before applying

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

Fix this in Epyc 7773x 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-2023-31346 — 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-2023-31346 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