SMM code execution via unchecked communication-buffer size
Published Mar 2, 2022 · Updated Aug 3, 2024
SMM memory corruption in HP PC BIOS allows local users with kernel privileges to execute arbitrary code in System Management Mode. The child SW SMI handler checks whether communication data lies outside SMRAM but fails to validate the communication-buffer size before writing an eight-byte status value to a predictable address. Kernel-level access is required; successful exploitation corrupts SMRAM and can hijack S3-resume control flow for persistent firmware-level code execution.
Summary
What happened
SMM memory corruption in HP PC BIOS allows local users with kernel privileges to execute arbitrary code in System Management Mode. The child SW SMI handler checks whether communication data lies outside SMRAM but fails to validate the communication-buffer size before writing an eight-byte status value to a predictable address. Kernel-level access is required; successful exploitation corrupts SMRAM and can hijack S3-resume control flow for persistent firmware-level code execution.
The record
- CVE
- CVE-2022-23954
- Published
- Mar 2, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1542.001, T1068
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Mar 2, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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.
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