CVE-2024-0179
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 · uneditedSMM Callout vulnerability within the AmdCpmDisplayFeatureSMM driver could allow locally authenticated attackers to overwrite SMRAM, potentially resulting in arbitrary code execution.
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 confidenceThis is an SMM (System Management Mode) callout vulnerability in the AmdCpmDisplayFeatureSMM driver. SMM is a high-privilege CPU mode used for firmware power management, and SMRAM is a protected memory region accessible only in SMM. The vulnerability allows a locally authenticated attacker to overwrite SMRAM, potentially executing arbitrary code at the highest privilege level (ring -2, below SMM).
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/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 checksWork through these to decide whether this CVE applies to you.
-
Verify AMD platform usageIdentify if the system uses an AMD processor or AMD-based platform (e.g., check system information, dmidecode output, or BIOS vendor information). This vulnerability affects only AMD-specific firmware components.Affected if System does not use AMD hardware - the AmdCpmDisplayFeatureSMM driver is AMD-specific and would not be present on non-AMD platforms.
-
Check BIOS/UEFI firmware versionRetrieve the current BIOS/UEFI firmware version from the system (via dmidecode, BIOS setup, or vendor tools). Compare this version against the AMD security advisory for CVE-2024-0179 to determine if the patch has been applied.Affected if The installed BIOS/UEFI firmware version is older than the version that includes the CVE-2024-0179 patch for the AmdCpmDisplayFeatureSMM driver.
-
Verify AmdCpmDisplayFeatureSMM driver presenceCheck firmware or system documentation for the presence of the AmdCpmDisplayFeatureSMM driver in the UEFI/BIOS image. This may be visible in firmware dumps, UEFI shell, or by reviewing the installed firmware components.Affected if The AmdCpmDisplayFeatureSMM driver is present in the system firmware and has not been patched to the fixed version.
-
Check SMRAM lock statusInspect the System Management RAM (SMRAM) configuration status. On systems with TCG/Intel VT-d or AMD-Vi, verify whether SMRAM is properly locked (using tools like dmidecode, or reading SMRAM control registers). The vulnerability allows SMRAM overwrite if not properly protected.Affected if SMRAM is not locked or is accessible from the operating system, indicating the SMM isolation may be compromised or the driver vulnerability could be exploitable.
A user is affected if they are running AMD hardware with a BIOS/UEFI firmware version lacking the CVE-2024-0179 patch, where the AmdCpmDisplayFeatureSMM driver is present and SMRAM is not securely locked.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataApply the vendor-supplied BIOS/UEFI firmware update from AMD that patches the AmdCpmDisplayFeatureSMM driver. Restrict local administrative access to prevent exploitation.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-0179 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-0179 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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