CVE-2024-56161

Improper signature verification in AMD CPU ROM microcode patch loader may allow an attacker with local administrator privilege to load malicious CPU microcode resulting in loss of confidentiality and integrity of a confidential guest running under AMD SEV-SNP.

Published: 2025-02-03 Last update: 2026-04-15 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2024-56161 is rated Low Risk (37/100): CVSS High severity, with low exploitation likelihood (EPSS 0.08%). Mandatory action: Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2024-56161

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-03-14 0.01% 0.08% +0.07%
2 2025-03-30 0.10% 0.01% -0.09%
3 2025-03-29 0.10%

Full EPSS history (8 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-56161

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.2 3.1 HIGH
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:N Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:H)
They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
0.8 5.8 [email protected]

Weakness enumeration for CVE-2024-56161

OS Trackers for CVE-2024-56161

vendor priority summary link
debian not yet assigned CVE-2024-56161 not yet assigned priority: Debian including 1 source packages (amd64-microcode), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2024-56161
redhat high https://access.redhat.com/security/cve/CVE-2024-56161
suse high https://www.suse.com/security/cve/CVE-2024-56161/
ubuntu medium CVE-2024-56161 medium priority: Ubuntu including 1 source packages (amd64-microcode), 9 status rows across 9 suites (bionic, focal, jammy, noble, oracular, plucky, trusty, upstream, xenial): not-affected 5, released 4. https://ubuntu.com/security/CVE-2024-56161

Affected software / configurations for CVE-2024-56161

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2024-56161

cvelogic Threat Intelligence