dbcve.org
Epyc 72f3 FirmwareOperating system · Amd

CVE-2022-23818

HIGH · 7.5 CVSS v3.1 Published 2023-05-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 on the model specific register: VM_HSAVE_PA may potentially lead to loss of SEV-SNP guest memory integrity.

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

Insufficient input validation on AMD's VM_HSAVE_PA model-specific register in SEV-SNP enabled processors could allow an attacker to corrupt or manipulate the register value, potentially compromising the memory integrity protection of SEV-SNP encrypted virtual machines.

MitigationApply AMD processor microcode/firmware updates and ensure hypervisor software is updated to include proper input validation for VM_HSAVE_PA before enabling SEV-SNP protection for virtual machines.

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 72f3 FirmwareOperating system
Affected:= milanpi_1.0.0.9
Epyc 7313 FirmwareOperating system
Affected:= milanpi_1.0.0.9
Epyc 7313p FirmwareOperating system
Affected:= milanpi_1.0.0.9
Epyc 7343 FirmwareOperating system
Affected:= milanpi_1.0.0.9
Epyc 7373x FirmwareOperating system
Affected:= milanpi_1.0.0.9
Epyc 73f3 FirmwareOperating system
Affected:= milanpi_1.0.0.9
Epyc 7413 FirmwareOperating system
Affected:= milanpi_1.0.0.9
Epyc 7443 FirmwareOperating system
Affected:= milanpi_1.0.0.9

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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
    Run 'dmidecode -s processor-version' or check /proc/cpuinfo to identify the exact AMD Epyc processor model (e.g., 72f3, 7313, 7313p, 7343, 7373x, 73f3, 7413, 7443)
    Affected if The processor is one of the listed affected models (72f3, 7313, 7313p, 7343, 7373x, 73f3, 7413, 7443)
  2. Check the firmware version
    Query the system firmware or BIOS/UEFI information for the milanpi firmware version. On Linux, this may be available via 'dmidecode' or vendor-specific tools. The affected version is milanpi_1.0.0.9
    Affected if The installed firmware version matches milanpi_1.0.0.9 exactly
  3. Verify SEV-SNP is enabled
    Check the hypervisor or system configuration for SEV-SNP (Secure Encrypted Virtualization-Secure Nested Paging) enablement status. On Linux, this may be visible via 'cat /sys/kernel/debug/x86/sev_status' or through hypervisor-specific controls (e.g., KVM, Hyper-V)
    Affected if SEV-SNP is actively enabled for virtual machines on the system

A system is affected if it runs an AMD Epyc 72f3, 7313, 7313p, 7343, 7373x, 73f3, 7413, or 7443 processor with milanpi_1.0.0.9 firmware and has SEV-SNP enabled for virtual machines.

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 processor microcode/firmware updates and ensure hypervisor software is updated to include proper input validation for VM_HSAVE_PA before enabling SEV-SNP protection for virtual machines.

Recommended fix Moderate confidence

AMD Epyc 7003 series (Milan) firmware version newer than milanpi_1.0.0.9 (obtain exact version from AMD security advisory)

  1. 1. Identify the specific AMD Epyc processor model in your system using `dmidecode -t processor | grep -i 'Version'` or checking the system BIOS/UEFI information.
  2. 2. Navigate to the AMD official support website (www.amd.com) and locate the security advisories or firmware download section for AMD Epyc 7003 series (Milan) processors.
  3. 3. Search for the security advisory related to CVE-2022-23818 to obtain the specific fixed firmware version.
  4. 4. Download the updated firmware package (milanpi) that addresses the VM_HSAVE_PA input validation vulnerability.
  5. 5. Apply the firmware update through the system's BMC (Baseboard Management Controller) interface (e.g., IPMI, Redfish, or vendor-specific management tools) or via BIOS/UEFI update utility following AMD's documented firmware update procedure.
  6. 6. After updating, verify the firmware version has been successfully applied using `ipmitool raw` commands or through the BMC web interface.
  7. 7. Restart the system as required by the firmware update process to ensure the fix takes effect.
Caveat Firmware updates may require system downtime; ensure proper backup and maintenance window planning before applying the update

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

Fix this in Epyc 72f3 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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