CVE-2025-3770 json
SMM IDT Privilege Escalation Vulnerability
published 2025-08-07 15 mo ago modified 2026-06-17 4 mo ago also EUVD-2025-23901
- cvss
- 7.0
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 7%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- edk2 Debian 13 2025.02-8+deb13u1
- edk2 Debian 14 2025.02-9
debian advisories DEBIAN-CVE-2025-3770
- edk2 Ubuntu 22.04 LTS 2022.02-3ubuntu0.22.04.4
- edk2 Ubuntu 24.04 LTS 2024.02-2ubuntu0.6
- edk2 Ubuntu 26.04 LTS, Ubuntu 25.10 2025.02-8ubuntu3
ubuntu advisories UBUNTU-CVE-2025-3770
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- edk2 Azure Linux 3.0 20240524git3e722403cd16-9
- edk2 CBL-Mariner 2.0 20230301gitf80f052277c8-43
- hvloader CBL-Mariner 2.0 1.0.1-14
azure linux advisories AZL-66108AZL-66119AZL-66122
Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 15 mo ago
Exploit prediction
0.18% chance of exploitation in the next 30 days, higher than 7% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.0 | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected products
- TianoCore EDK2
Classification
- Weakness
-
- CWE-693 Protection Mechanism Failure
References
Sources
- CVE List CVE-2025-3770
- NVD CVE-2025-3770
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.