CVE-2025-3770: SMM IDT Privilege Escalation Vulnerability
Noroxi assessment
Priority: Monitor (action score 28/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: azl3 edk2 20240524git3e722403cd16-9 on Azure Linux 3.0 20240524git3e722403cd16-9; cbl2 edk2 20230301gitf80f052277c8-42 on CBL Mariner 2.0 20230301gitf80f052277c8-43; cbl2 edk2 20230301gitf80f052277c8-43 on CBL Mariner 2.0 20230301gitf80f052277c8-43.
Low priority for now. Upgrade to azl3 edk2 20240524git3e722403cd16-9 on Azure Linux 3.0 20240524git3e722403cd16-9; cbl2 edk2 20230301gitf80f052277c8-42 on CBL Mariner 2.0 20230301gitf80f052277c8-43; cbl2 edk2 20230301gitf80f052277c8-43 on CBL Mariner 2.0 20230301gitf80f052277c8-43 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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
- Aug 6, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- CWE-693
Report tools
Action score
28
Monitor
Low priority for now.
- CVSS
- 28 / 40 · 7.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · TianoCore
- 7.0
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (TianoCore). Independent of NVD's CPE analysis and usually ahead of it.
TianoCore EDK2
- up to and including edk2-stable202505affected · Custom
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | edk2 | from 0 | — |
| Debian:13 | edk2 | before 2025.02-8+deb13u1 | 2025.02-8+deb13u1 |
| Debian:14 | edk2 | before 2025.02-9 | 2025.02-9 |
Same product
tianocore: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-38578Existing CommBuffer checks in SmmEntryPoint will not catch underflow when computing BufferSize.39Monitor
- CVE-2026-97631Pre-boot RCE in EDK II PXE driver38Monitor
- CVE-2023-45235Buffer Overflow in EDK II Network Package35Monitor
Published before and after this one in the same product
- ← EarlierCVE-2025-2295Mar 14, 2025 · Potential iSCSI R2T PDU Vulnerability14Monitor
- ← EarlierCVE-2024-38797Apr 7, 2025 · Out-of-bounds Read in HashPeImageByType()18Monitor
- Later →CVE-2024-38805Aug 12, 2025 · iSCSI Remote Memory Corruption and Denial of Service25Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| azl3 edk2 20240524git3e722403cd16-9 on Azure Linux 3.0 | 20240524git3e722403cd16-9 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 edk2 20230301gitf80f052277c8-42 on CBL Mariner 2.0 | 20230301gitf80f052277c8-43 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 edk2 20230301gitf80f052277c8-43 on CBL Mariner 2.0 | 20230301gitf80f052277c8-43 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 hvloader 1.0.1-13 on CBL Mariner 2.0 | 1.0.1-14 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 hvloader 1.0.1-14 on CBL Mariner 2.0 | 1.0.1-14 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:edk2 | 2025.02-8+deb13u1 · Debian:13 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Christopher Domasfinder
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-693 · Protection Mechanism FailureCVSS vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Accessing Functionality Not Properly Constrained by ACLsCAPEC-1likelihood: High · High
- Cross Site TracingCAPEC-107likelihood: Medium · Very High
- Directory IndexingCAPEC-127likelihood: High · Medium
- Using Malicious FilesCAPEC-17likelihood: High · Very High
- Encryption Brute ForcingCAPEC-20likelihood: Low · Low
- Exploiting Trust in ClientCAPEC-22likelihood: High · High
- Escaping a Sandbox by Calling Code in Another LanguageCAPEC-237likelihood: Low · Very High
- Using Unpublished Interfaces or FunctionalityCAPEC-36likelihood: Medium · High
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.