Privilege escalation via unset SMI lock
Published Nov 11, 2025 · Updated Nov 11, 2025
Protection mechanism failure in Intel Slim Bootloader allows local users with existing privileges to escalate through UEFI firmware. The Idaville Stage2 BoardInit ReadyToBoot path leaves the SMI_LOCK bit unset instead of locking system-management interrupts before OSLoader starts. Exploitation requires high complexity and additional attack requirements but no user interaction, and grants control over the vulnerable system's confidentiality, integrity, and availability.
Summary
What happened
Protection mechanism failure in Intel Slim Bootloader allows local users with existing privileges to escalate through UEFI firmware. The Idaville Stage2 BoardInit ReadyToBoot path leaves the SMI_LOCK bit unset instead of locking system-management interrupts before OSLoader starts. Exploitation requires high complexity and additional attack requirements but no user interaction, and grants control over the vulnerable system's confidentiality, integrity, and availability.
The record
- CVE
- CVE-2025-35968
- Published
- Nov 11, 2025
- Updated
- Nov 11, 2025
- Vendor
- Topcon Positioning Systems, Inc.
- Product
- Slim Bootloader
- Classifications
- CWE-693, T1068
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Nov 11, 2025CVE publishedPublication date reported by the CVE source.
- Nov 11, 2025Record 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=See references
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