GIGABYTE UEFI-GenericComponentSmmEntry 1.0.0 Software SMI SwSmiInputValue untrusted pointer dereference

Summaryinfo

A vulnerability has been found in GIGABYTE UEFI-GenericComponentSmmEntry 1.0.0 and classified as critical. The affected element is the function SwSmiInputValue of the component Software SMI Handler. Performing a manipulation results in untrusted pointer dereference. This vulnerability is cataloged as CVE-2025-7027. The attack must be initiated from a local position. There is no exploit available.

Detailsinfo

A vulnerability classified as critical has been found in GIGABYTE UEFI-GenericComponentSmmEntry 1.0.0. This affects the function SwSmiInputValue of the component Software SMI Handler. The manipulation with an unknown input leads to a untrusted pointer dereference vulnerability. CWE is classifying the issue as CWE-822. The product obtains a value from an untrusted source, converts this value to a pointer, and dereferences the resulting pointer. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

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.

It is possible to read the advisory at gigabyte.com. This vulnerability is uniquely identified as CVE-2025-7027 since 07/02/2025. The exploitability is told to be easy. Attacking locally is a requirement. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 07/12/2025).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-21141). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Vendor

• GIGABYTE

Name

• UEFI-GenericComponentSmmEntry

Version

• 1.0.0

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion