CVE-2025-3770 | SMM IDT Privilege Escalation Vulnerability

EDK2 contains a vulnerability in BIOS where an attacker may cause “Protection Mechanism Failure” by local access. Successful exploitation of this vulnerability will lead to arbitrary code execution and impact Confidentiality, Integrity, and Availability.

Published: 2025-08-07 Last update: 2026-04-15 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2025-3770 is rated Low Risk (29/100): CVSS High severity, with low exploitation likelihood (EPSS 0.02%). 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-2025-3770

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 2025-08-07 0.02%

Full EPSS history (1 record total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-3770

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.0 3.1 HIGH
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H 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:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
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:H)
Could take the service down hard or make it unusable for people who depend on it.
1.0 5.9 [email protected]

Weakness enumeration for CVE-2025-3770

OS Trackers for CVE-2025-3770

vendor priority summary link
debian not yet assigned CVE-2025-3770 not yet assigned priority: Debian including 1 source packages (edk2), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 3, open 2. https://security-tracker.debian.org/tracker/CVE-2025-3770
suse high CVE-2025-3770 severity important: SUSE including 24 source package names (qemu, qemu-arm, …), 97 product×package rows across 7 product lines (SUSE Linux Enterprise Server 12 SP2-LTSS, SUSE Linux Enterprise Server 12 SP4-LTSS, … (7 product lines)): Known Not Affected 97. https://www.suse.com/security/cve/CVE-2025-3770/
ubuntu medium CVE-2025-3770 medium priority: Ubuntu including 1 source packages (edk2), 8 status rows across 8 suites (bionic, focal, jammy, noble, plucky, questing, upstream, xenial): released 5, needs-triage 3. https://ubuntu.com/security/CVE-2025-3770

Affected software / configurations for CVE-2025-3770

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2025-3770

cvelogic Threat Intelligence