Skip to main content
CVE-2025-7028VulnerabilityPublished Updated

CVE-2025-7028: GIGABYTE UEFI-SmiFlash · Untrusted Pointer Dereference

Affects GIGABYTE UEFI-SmiFlashSource CVE Database V5

0

Not known to be exploited · CVSS 7.8 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
7.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Jul 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
GIGABYTE UEFI-SmiFlashAffected
  • =1.0.0
Fixed in–

AI-suggested

1. Immediate mitigation requires applying firmware updates or patches from GIGABYTE once available; organizations should engage with GIGABYTE support channels to obtain updates or advisories. 2. Restrict local administrative access to systems with the affected firmware to trusted personnel only, minimizing the risk of local exploitation. 3. Implement strict endpoint security controls to detect and prevent unauthorized code execution or privilege escalation attempts that could lead to local access. 4. Employ hardware-based security features such as Intel Boot Guard or AMD equivalent to protect firmware integrity. 5. Monitor system logs and firmware integrity checks for anomalies indicative of SMRAM tampering or unusual flash memory operations. 6. Conduct regular firmware integrity validation using trusted tools and consider deploying runtime firmware protection solutions. 7. For critical environments, consider hardware inventory audits to identify systems running the vulnerable firmware version and prioritize remediation accordingly. 8. Educate IT and security teams about the risks of firmware vulnerabilities and the importance of layered defense strategies.

Description

A vulnerability in the Software SMI handler (SwSmiInputValue 0x20) allows a local attacker to supply a crafted pointer (FuncBlock) through RBX and RCX register values. This pointer is passed unchecked into multiple flash management functions (ReadFlash, WriteFlash, EraseFlash, and GetFlashInfo) that dereference both the structure and its nested members, such as BufAddr. This enables arbitrary read/write access to System Management RAM (SMRAM), allowing an attacker to corrupt firmware memory, exfiltrate SMRAM content via flash, or install persistent implants.

References

Community reviews

Loading reviews…