Skip to main content
VulnerabilityPublished Updated

CVE-2025-7026: GIGABYTE UEFI-GenericComponentSmmEntry · Untrusted Pointer Dereference

Affects GIGABYTE UEFI-GenericComponentSmmEntrySource CVE Database V5

0

Not known to be exploited · CVSS 8.2 High.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
8.2High
How severe the flaw is on the 0–10 CVSS scale.
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: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 26 Oct 2026.

What to do

Affected software

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

AI-suggested

Organizations should implement the following specific mitigations: 1) Monitor GIGABYTE's official channels for firmware updates or patches addressing CVE-2025-7026 and apply them promptly once available. 2) Restrict local administrative access strictly to trusted personnel and enforce least privilege principles to reduce the risk of local exploitation. 3) Employ hardware-based security features such as Intel Boot Guard or AMD equivalent to protect firmware integrity and prevent unauthorized firmware modifications. 4) Use Endpoint Detection and Response (EDR) tools capable of detecting anomalous SMM activity or unusual system management interrupts. 5) Regularly audit and monitor system logs for suspicious local privilege escalation attempts or abnormal SMI handler invocations. 6) Implement physical security controls to prevent unauthorized physical access to systems, as local access is required. 7) Consider deploying firmware integrity verification tools that can detect unauthorized changes to SMRAM or UEFI components. 8) Educate system administrators about the risks of firmware-level attacks and the importance of timely patching and access control.

Description

A vulnerability in the Software SMI handler (SwSmiInputValue 0xB2) allows a local attacker to control the RBX register, which is used as an unchecked pointer in the CommandRcx0 function. If the contents at RBX match certain expected values (e.g., '$DB$' or '2DB$'), the function performs arbitrary writes to System Management RAM (SMRAM), leading to potential privilege escalation to System Management Mode (SMM) and persistent firmware compromise.

References

Community reviews

Loading reviews…