SMRAM code execution via improperly validated SMI
Published Oct 12, 2022 · Updated May 16, 2025
Improper input validation in Dell Client Platform BIOS allows local users to execute arbitrary code in SMRAM through a crafted SMI. Dell identifies the SMI-handling path but has not published the affected handler or the input field that lacks validation. Administrative local access and a high-complexity attack are required; successful exploitation crosses into protected SMRAM execution.
Summary
What happened
Improper input validation in Dell Client Platform BIOS allows local users to execute arbitrary code in SMRAM through a crafted SMI. Dell identifies the SMI-handling path but has not published the affected handler or the input field that lacks validation. Administrative local access and a high-complexity attack are required; successful exploitation crosses into protected SMRAM execution.
The record
- CVE
- CVE-2022-32485
- Published
- Oct 12, 2022
- Updated
- May 16, 2025
- Vendor
- Dell
- Product
- Dell Client Platform BIOS
- Classifications
- CWE-20, T1068
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Oct 12, 2022CVE publishedPublication date reported by the CVE source.
- May 16, 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=unspecified <2.3
What conditions does exploitation require?
What is affected?
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