Firmware interruption via caller-controlled buffer bounds
Published May 15, 2025 · Updated May 16, 2025
Buffer over-read in InsydeH2O kernel 5.2 through 5.7 releases allows local users with high privileges to interrupt firmware services. VariableRuntimeDxe's SecureBootHandler trusts caller-supplied DataSize and VariableNameSize values when checking whether variable data and names fit within the input buffer. Exploitation requires local high privileges; the bounded effect is availability loss, with no vendor-reported data disclosure or modification.
Summary
What happened
Buffer over-read in InsydeH2O kernel 5.2 through 5.7 releases allows local users with high privileges to interrupt firmware services. VariableRuntimeDxe's SecureBootHandler trusts caller-supplied DataSize and VariableNameSize values when checking whether variable data and names fit within the input buffer. Exploitation requires local high privileges; the bounded effect is availability loss, with no vendor-reported data disclosure or modification.
The record
- CVE
- CVE-2024-52880
- Published
- May 15, 2025
- Updated
- May 16, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-349, CWE-20, T1499
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- May 15, 2025CVE 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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