# CVE-2025-7029: SMM Arbitrary Write via Unchecked OcHeader Buffer in Platform Configuration Handler

> Local attackers can corrupt SMRAM and escalate privileges via unchecked buffer writes in GIGABYTE UEFI firmware.

- **Severity:** High 8.2 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Jul 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-35m5-23fr-x9rq

## What is CVE-2025-7029?

CVE-2025-7029 is a high-severity memory corruption vulnerability in GIGABYTE UEFI-OverClockSmiHandler, 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 0xB2) allows a local attacker to control the RBX register, which is used to derive pointers (OcHeader, OcData) passed into power and thermal configuration logic. These buffers are not validated before performing multiple structured memory writes based on OcSetup NVRAM values, enabling arbitrary SMRAM corruption and potential SMM privilege escalation.

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


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

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

## Is CVE-2025-7029 being exploited?

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

Public exploit code:

- First public analysis of SoftLanding UEFI bootkit: Ring -2 implant, CVE-2025-7029, 240+ Gigabyte boards, GPU AI evasion, dual C2. YARA + Sigma + Suricata included. (github_poc): https://github.com/ARES-SYS/uefi_bootkit_softlanding

## Fix prompt for AI coding agents

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

What it is: CVE-2025-7029 is a high-severity memory corruption vulnerability in GIGABYTE UEFI-OverClockSmiHandler, 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-7029 in the wild and no public exploit code.

Affected product: GIGABYTE UEFI-OverClockSmiHandler. 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-7029/ (Markdown: https://insights.sbomify.com/CVE-2025-7029/index.md)
```

## Sources

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

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