Firmware resource exhaustion via SmiFlash race condition
Published Aug 12, 2025 · Updated Aug 12, 2025
Race condition in the SmiFlash BIOS component in AMI Aptio V 5.0 through 5.040 allows local users to exhaust firmware resources. AMI identifies SmiFlash and improper synchronization but has not disclosed the shared resource, competing operations, or trigger sequence. Exploitation requires high local privileges, active user interaction, and particular system conditions, and can compromise firmware confidentiality, integrity, and availability.
Summary
What happened
Race condition in the SmiFlash BIOS component in AMI Aptio V 5.0 through 5.040 allows local users to exhaust firmware resources. AMI identifies SmiFlash and improper synchronization but has not disclosed the shared resource, competing operations, or trigger sequence. Exploitation requires high local privileges, active user interaction, and particular system conditions, and can compromise firmware confidentiality, integrity, and availability.
The record
- CVE
- CVE-2025-22830
- Published
- Aug 12, 2025
- Updated
- Aug 12, 2025
- Vendor
- American Megatrends International
- Product
- Aptio V
- Classifications
- CWE-362, T1499
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Aug 12, 2025CVE publishedPublication date reported by the CVE source.
- Aug 12, 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=AptioV_5.0 <=AptioV_5.040
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