# CVE-2025-7771: Code Execution / Escalation of Privileges in ThrottleStop

> Local attackers can exploit insecure IOCTLs in the ThrottleStop driver to read/write physical memory, enabling arbitrary kernel code execution and privilege escalation.

- **Severity:** High 8.7 (`CVSS:4.0/AV:L/AC:H/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA: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:** 6 Aug 2025
- **Updated:** 6 Aug 2025
- **Also known as:** GHSA-f8p7-vvxp-hcxv

## What is CVE-2025-7771?

CVE-2025-7771 is a high-severity vulnerability in TechPowerUp ThrottleStop, published on 6 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

ThrottleStop.sys, a legitimate driver, exposes two IOCTL interfaces that allow arbitrary read and write access to physical memory via the MmMapIoSpace function. This insecure implementation can be exploited by a malicious user-mode application to patch the running Windows kernel and invoke arbitrary kernel functions with ring-0 privileges. The vulnerability enables local attackers to execute arbitrary code in kernel context, resulting in privilege escalation and potential follow-on attacks, such as disabling security software or bypassing kernel-level protections. ThrottleStop.sys version 3.0.0.0 and possibly others are affected. Apply updates per vendor instructions.

Weakness: CWE-782 (Exposed IOCTL with Insufficient Access Control)

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


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

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

## Is CVE-2025-7771 being exploited?

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

Public exploit code:

- Advanced PoC & Research for CVE-2026-0828 (Safetica) and CVE-2025-7771 (ThrottleStop). Analysis of BYOVD (Bring Your Own Vulnerable Driver) TTPs for Ring 0 process termination and physical memory R/W. Researching EDR-Killer patterns, PPL bypasses, and kernel-mode primitives used by MedusaLocker and other threat actors. (github_poc): https://github.com/DeathShotXD/0xKern3lCrush
- ThrottleStop.sys Arbitrary Physical Memory R/W (github_poc): https://github.com/enessakircolak/CVE-2025-7771
- CVE-2025-7771: Arbitrary physical memory and I/O port read/write via ThrottleStop driver (github_poc): https://github.com/wqsv/ThrottleStopPoC
- Arbitrary physical memory read/write exploitation using ThrottleStop.sys (CVE-2025-7771) with superfetch address translation - Windows kernel security research (github_poc): https://github.com/AmrHuss/throttlestop-exploit-rw
- Escalating privilege in the system from unsigned driver using throttlestop vulnerability (github_poc): https://github.com/D4rkks/CVE-2025-7771-Vulnerability-Exploration
- CVE-2025-7771 ThrottleStop.sys privilege escalation exploit - unrestricted IOCTL access to physical memory via MmMapIoSpace (github_poc): https://github.com/Demoo1337/ThrottleStop

## Fix prompt for AI coding agents

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

What it is: CVE-2025-7771 is a high-severity vulnerability in TechPowerUp ThrottleStop, published on 6 Aug 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-7771 in the wild and no public exploit code.

Affected product: TechPowerUp ThrottleStop. 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-7771/ (Markdown: https://insights.sbomify.com/CVE-2025-7771/index.md)
```

## Sources

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

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