Local privilege escalation via control-flow mismanagement
Published May 13, 2025 · Updated Feb 26, 2026
Insufficient control flow management in Intel Xeon 6 E-Core firmware allows local users with privileged access to escalate privileges. Intel identifies the locus as the Alias Checking Trusted Module but has not disclosed the specific control-flow operation or input that is mishandled. Exploitation requires privileged local access and high complexity, affecting confidentiality and integrity without a reported availability impact.
Summary
What happened
Insufficient control flow management in Intel Xeon 6 E-Core firmware allows local users with privileged access to escalate privileges. Intel identifies the locus as the Alias Checking Trusted Module but has not disclosed the specific control-flow operation or input that is mishandled. Exploitation requires privileged local access and high complexity, affecting confidentiality and integrity without a reported availability impact.
The record
- CVE
- CVE-2025-20004
- Published
- May 13, 2025
- Updated
- Feb 26, 2026
- Vendor
- Topcon Positioning Systems, Inc.
- Product
- Intel Xeon 6 Processors
- Classifications
- CWE-691, T1068
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- May 13, 2025CVE publishedPublication date reported by the CVE source.
- Feb 26, 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=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