CVE-2024-21925
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 · uneditedImproper input validation within the AmdPspP2CmboxV2 driver may allow a privileged attacker to overwrite SMRAM, leading to 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 · high confidenceThe AmdPspP2CmboxV2 AMD driver contains an improper input validation vulnerability that allows a privileged attacker to overwrite SMRAM (Security Mode RAM), which is protected memory used by AMD's Platform Security Processor. This memory corruption in SMRAM can lead to arbitrary code execution at the firmware level.
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.
-
Identify if AmdPspP2CmboxV2 driver is presentOn Windows, run 'driverquery /v | findstr AmdPspP2CmboxV2' or check C:\Windows\System32\drivers\ for the driver file. On Linux, check /lib/modules/$(uname -r)/kernel/drivers/firmware/ or use 'lsmod | grep psp'Affected if The driver file AmdPspP2CmboxV2.sys (Windows) or equivalent driver module exists on the system
-
Check the installed driver versionRight-click the driver file, select Properties, then Details to view File Version. On Linux, use 'modinfo' on the PSP driver module if foundAffected if Any version of the AmdPspP2CmboxV2 driver is installed; compare against any vendor-released fixed versions when available
-
Verify the driver is loaded or activeOn Windows, check Device Manager under System devices for AMD Platform Security Processor driver status. On Linux, check 'dmesg | grep -i psp' or 'lsmod | grep psp' for loaded PSP modulesAffected if The AMD PSP driver is loaded and active on the system
-
Confirm system uses an affected AMD platformCheck system information (msinfo32 on Windows, 'cat /proc/cpuinfo' on Linux) for AMD processor model and chipset. Research the specific CPU/firmware lineage against AMD security advisoriesAffected if The system runs an AMD processor and firmware that falls within the affected product scope described in AMD advisory
-
Check SMRAM protection status in firmware/BIOSAccess BIOS/UEFI setup during boot and look for SMM Lock or SMRAM protection settings under Security or Advanced menus. On Linux, tools like 'dmidecode' may expose some firmware configurationsAffected if SMRAM protection is not properly configured or can be bypassed, allowing the vulnerability to be exploited
The user is affected if the AmdPspP2CmboxV2 driver is present and loaded on an AMD system within the affected product range, and the system has not received the vendor firmware/driver update that addresses the input validation flaw.
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 vendor-provided firmware/driver updates from AMD that address the input validation flaw in the AmdPspP2CmboxV2 driver. Until a patch is available, restrict administrative access and monitor for privilege escalation attempts.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-21925 — 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-21925 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