dbcve.org
Epyc 9654p FirmwareOperating system · Amd

CVE-2022-23830

MEDIUM · 5.3 CVSS v3.1 Published 2023-11-14
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
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
SMM configuration may not be immutable, as intended, when SNP is enabled resulting in a potential limited loss of 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

AMD SEV-SNP (Secure Encrypted Virtualization with Secure Nested Pouting) contains a vulnerability where SMM (System Management Mode) configuration is not properly protected as immutable when SNP is enabled. This can potentially allow limited guest memory integrity violations through the SMM configuration being modifiable when it should be restricted.

MitigationApply AMD firmware/microcode updates that address the SMM immutability issue in SEV-SNP implementations. Verify SNP attestation confirms proper SMM protection after patching.

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 9654p FirmwareOperating system
Affected:< genoapi_1.0.0.1
Epyc 9654 FirmwareOperating system
Affected:< genoapi_1.0.0.1
Epyc 9634 FirmwareOperating system
Affected:< genoapi_1.0.0.1
Epyc 9554p FirmwareOperating system
Affected:< genoapi_1.0.0.1
Epyc 9554 FirmwareOperating system
Affected:< genoapi_1.0.0.1
Epyc 9534 FirmwareOperating system
Affected:< genoapi_1.0.0.1
Epyc 9474f FirmwareOperating system
Affected:< genoapi_1.0.0.1
Epyc 9454p FirmwareOperating system
Affected:< genoapi_1.0.0.1

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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 -t processor | grep -E "(Manufacturer|Version|Family)"' or check /proc/cpuinfo for the CPU model name
    Affected if The processor is not one of the listed affected Epyc models (9654p, 9654, 9634, 9554p, 9554, 9534, 9474f, 9454p)
  2. Verify SEV-SNP is enabled
    Check the SEV-SNP status by examining /sys/kernel/security/sev_status or running 'kvm_stat -1' if available, or check the hypervisor configuration for SEV-SNP enablement
    Affected if SEV-SNP is actively enabled and running for virtual machines on this host
  3. Retrieve the processor firmware version
    Use 'dmidecode -t bios' to check firmware version, or use the platform-specific tool such as 'amd_ksctl' or the BMC/IPMI interface to query the SNP firmware version labeled as genoapi
    Affected if The firmware version string contains a version lower than genoapi_1.0.0.1, or the version cannot be determined and SEV-SNP is enabled
  4. Cross-reference firmware version against affected range
    Compare the retrieved genoapi firmware version number to the threshold genoapi_1.0.0.1
    Affected if The installed genoapi version is less than 1.0.0.1 (for example, 1.0.0.0 or any earlier build)

A user is affected if they run an AMD Epyc processor from the listed models with SEV-SNP enabled and firmware version below genoapi_1.0.0.1.

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 firmware/microcode updates that address the SMM immutability issue in SEV-SNP implementations. Verify SNP attestation confirms proper SMM protection after patching.

Recommended fix Moderate confidence

genoapi_1.0.0.1 or later firmware version

  1. Identify the specific AMD Epyc processor model from the affected list (9654p, 9654, 9634, 9554p, 9554, 9534, 9474f, or 9454p)
  2. Check the current firmware version on the affected system
  3. Download the updated firmware (genoapi_1.0.0.1 or later) from AMD's official support website for the specific Epyc model
  4. Apply the firmware update following AMD's standard firmware update procedures for Epyc processors
  5. Verify the firmware has been successfully applied and the system is functioning correctly
Caveat Firmware updates carry inherent risks and should be tested in a non-production environment first; ensure proper backup and downtime planning

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

Fix this in Epyc 9654p Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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