# CVE-2025-7028: SMM Arbitrary Memory Access via Flash Handler with Unchecked FuncBlock Pointer

> A local attacker can exploit an unchecked pointer in the UEFI SMM handler to achieve arbitrary memory access, enabling firmware corruption or persistent implants.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Jul 2025
- **Updated:** 3 Nov 2025
- **Also known as:** GHSA-g4hc-h3h3-22rv

## What is CVE-2025-7028?

CVE-2025-7028 is a high-severity memory corruption vulnerability in GIGABYTE UEFI-SmiFlash, published on 11 Jul 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2025-7028?


## How do I fix CVE-2025-7028?

No fix has been published for CVE-2025-7028 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-7028 being exploited?

There is no known exploitation of CVE-2025-7028 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-7028 and fix it if it is affected.

What it is: CVE-2025-7028 is a high-severity memory corruption vulnerability in GIGABYTE UEFI-SmiFlash, published on 11 Jul 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-7028 in the wild and no public exploit code.

Affected product: GIGABYTE UEFI-SmiFlash. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-7028/ (Markdown: https://insights.sbomify.com/CVE-2025-7028/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-7028
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-7028
- OSV: https://osv.dev/vulnerability/CVE-2025-7028

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-7028/
Summaries are generated and may contain mistakes; the official description above is the record.