SMM arbitrary write via dual-controlled pointers
Published Jul 11, 2025 · Updated Feb 26, 2026
Memory corruption in GIGABYTE UEFI GenericComponentSmmEntry 1.0.0 allows local users to write arbitrary SMRAM content through an SMI handler. CommandRcx1 takes its write destination from the unvalidated SetupXtuBufferAddress NVRAM variable and its write content from an RBX-derived pointer. Administrative access is required; successful exploitation executes code in Ring -2 and can establish persistent firmware control.
Summary
What happened
Memory corruption in GIGABYTE UEFI GenericComponentSmmEntry 1.0.0 allows local users to write arbitrary SMRAM content through an SMI handler. CommandRcx1 takes its write destination from the unvalidated SetupXtuBufferAddress NVRAM variable and its write content from an RBX-derived pointer. Administrative access is required; successful exploitation executes code in Ring -2 and can establish persistent firmware control.
The record
- CVE
- CVE-2025-7027
- Published
- Jul 11, 2025
- Updated
- Feb 26, 2026
- Vendor
- GIGA-BYTE Technology Co., Ltd.
- Product
- UEFI GenericComponentSmmEntry
- Classifications
- T1542.001
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Jul 11, 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=1.0.0
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