GIGABYTE UEFI-SmiFlash 1.0.0 Software SMI SwSmiInputValue untrusted pointer dereference
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.8 | $0-$5k | 0.00 |
Summary
A vulnerability was found in GIGABYTE UEFI-SmiFlash 1.0.0 and classified as critical. The impacted element is the function SwSmiInputValue of the component Software SMI Handler. Executing a manipulation can lead to untrusted pointer dereference.
This vulnerability is registered as CVE-2025-7028. The attack needs to be launched locally. No exploit is available.
Details
A vulnerability classified as critical was found in GIGABYTE UEFI-SmiFlash 1.0.0. This vulnerability affects the function SwSmiInputValue of the component Software SMI Handler. The manipulation with an unknown input leads to a untrusted pointer dereference vulnerability. The CWE definition for the vulnerability is CWE-822. The product obtains a value from an untrusted source, converts this value to a pointer, and dereferences the resulting pointer. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
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.
The advisory is shared for download at gigabyte.com. This vulnerability was named CVE-2025-7028 since 07/02/2025. The exploitation appears to be easy. The attack needs to be approached locally. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 07/11/2025).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Once again VulDB remains the best source for vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.8VulDB Meta Temp Score: 7.8
VulDB Base Score: 7.8
VulDB Temp Score: 7.8
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Untrusted pointer dereferenceCWE: CWE-822
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
07/02/2025 CVE reserved07/11/2025 Advisory disclosed
07/11/2025 VulDB entry created
07/11/2025 VulDB entry last update
Sources
Advisory: gigabyte.comStatus: Not defined
CVE: CVE-2025-7028 (🔒)
GCVE (CVE): GCVE-0-2025-7028
GCVE (VulDB): GCVE-100-316180
Entry
Created: 07/11/2025 20:35Changes: 07/11/2025 20:35 (53)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.