UEFI bypass leading to secure kernel compromise
Published Feb 11, 2025 · Updated Feb 13, 2026
Improper input validation in Microsoft Surface firmware allows adjacent attackers to bypass UEFI protections after user interaction. Microsoft has not disclosed which hypervisor or firmware input is insufficiently validated or how that input crosses the UEFI boundary. Exploitation requires specific hardware conditions and a user-initiated reboot, after which the hypervisor and secure kernel can be compromised.
Summary
What happened
Improper input validation in Microsoft Surface firmware allows adjacent attackers to bypass UEFI protections after user interaction. Microsoft has not disclosed which hypervisor or firmware input is insufficiently validated or how that input crosses the UEFI boundary. Exploitation requires specific hardware conditions and a user-initiated reboot, after which the hypervisor and secure kernel can be compromised.
The record
- CVE
- CVE-2025-21194
- Published
- Feb 11, 2025
- Updated
- Feb 13, 2026
- Vendor
- Microsoft
- Product
- Microsoft Surface Laptop Go
- Classifications
- CWE-20
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 11, 2025CVE publishedPublication date reported by the CVE source.
- Feb 13, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=-
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo