CVE-2025-2296
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-12-09

Last updated on: 2025-12-09

Assigner: TianoCore.org

Description
EDK2 contains a vulnerability in BIOS where an attacker may cause “ Improper Input Validation” by local access. Successful exploitation of this vulnerability could alter control flow in unexpected ways, potentially allowing arbitrary command execution and impacting Confidentiality, Integrity, and Availability.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-12-09
Last Modified
2025-12-09
Generated
2026-06-16
AI Q&A
2025-12-09
EPSS Evaluated
2026-06-15
NVD
CVE-2025-2296
EUVD
EUVD-2025-201946
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
edk2 edk2 4.0
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-20 The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability in EDK2 BIOS involves improper input validation that can be exploited by an attacker with local access. Exploiting this flaw may allow the attacker to alter the control flow of the BIOS in unexpected ways, potentially enabling arbitrary command execution.

Impact Analysis

Successful exploitation of this vulnerability could impact the confidentiality, integrity, and availability of the affected system by allowing arbitrary command execution at the BIOS level.

Compliance Impact

The provided resources do not specify how this vulnerability affects compliance with common standards and regulations such as GDPR or HIPAA.

Detection Guidance

Detection involves verifying if the system is running a vulnerable version of the EDK2 firmware, specifically versions up to 202502, and if Secure Boot is enabled but bypassed due to fallback to the legacy loader in direct boot mode. There are no specific commands provided to detect this vulnerability directly. However, checking the firmware version and Secure Boot status can help identify exposure. For example, on Linux systems, you can check Secure Boot status with 'mokutil --sb-state' and inspect firmware versions via system firmware tools or vendor utilities. Additionally, reviewing boot logs for fallback loader usage might indicate exploitation attempts. [1]

Mitigation Strategies

The immediate mitigation step is to update the EDK2 firmware to version 202505 or later, where the patch addressing this fallback behavior has been applied. Ensuring Secure Boot is properly configured and that the allowed database (DB) contains the correct signatures can also help prevent fallback to the legacy loader. Disabling direct boot mode, if possible, may reduce exposure until the patch is applied. [1]

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2025-2296. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart