CVE-2025-7027: GIGABYTE UEFI-GenericComponentSmmEntry · Untrusted Pointer Dereference
Affects GIGABYTE UEFI-GenericComponentSmmEntrySource CVE Database V5
Not known to be exploited · CVSS 8.2 High.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 11 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| GIGABYTE UEFI-GenericComponentSmmEntry | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2025-7027, organizations should implement the following specific measures: 1) Restrict local administrative access strictly to trusted personnel and enforce the principle of least privilege to reduce the risk of local exploitation. 2) Monitor and audit changes to UEFI NVRAM variables, especially SetupXtuBufferAddress, to detect unauthorized modifications that could indicate exploitation attempts. 3) Employ hardware-based firmware protection features such as BIOS write protection and Secure Boot to limit unauthorized firmware modifications. 4) Use endpoint detection and response (EDR) tools capable of detecting anomalous SMM-related activities or unusual system management interrupts. 5) Coordinate with GIGABYTE for timely firmware updates or patches addressing this vulnerability; prioritize testing and deployment once available. 6) Consider implementing runtime integrity verification tools that can detect unauthorized changes in SMRAM or firmware code. 7) In environments where patching is delayed, isolate affected systems from untrusted users and networks to minimize attack surface. 8) Educate system administrators about the risks of firmware vulnerabilities and the importance of secure firmware management practices. These targeted actions go beyond generic advice by focusing on the unique aspects of SMM and UEFI firmware security.
Description
A vulnerability in the Software SMI handler (SwSmiInputValue 0xB2) allows a local attacker to control both the read and write addresses used by the CommandRcx1 function. The write target is derived from an unvalidated UEFI NVRAM variable (SetupXtuBufferAddress), while the write content is read from an attacker-controlled pointer based on the RBX register. This dual-pointer dereference enables arbitrary memory writes within System Management RAM (SMRAM), leading to potential SMM privilege escalation and firmware compromise.