CVE-2025-7771: Arbitrary Physical Memory Access in TechPowerUp ThrottleStop Driver
CVE-2025-7771 is an arbitrary physical memory access vulnerability in the signed TechPowerUp ThrottleStop Windows kernel driver. Two exposed IOCTL interfaces use MmMapIoSpace to provide user-mode applications with arbitrary physical memory read and write capabilities. Attackers can abuse these primitives to modify the running Windows kernel and invoke arbitrary kernel functions with ring-0 privileges. Driver version 3.0.0.0 is affected; other versions may also be vulnerable. The flaw has been exploited in bring-your-own-vulnerable-driver attacks to suppress endpoint security before ransomware deployment.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation compromises kernel confidentiality and integrity and enables arbitrary code execution in kernel context. Attackers can elevate privileges, manipulate kernel memory, bypass kernel-level protections, and terminate protected security processes. Observed abuse includes disabling antivirus and EDR protections to facilitate subsequent ransomware execution.
Mitigation
If you can’t patch tonight, do this now.
Use Microsoft's vulnerable-driver blocklist and appropriately configured WDAC or App Control policies to prevent vulnerable driver loading. Enable compatible Core Isolation Memory Integrity protections and the Microsoft Defender ASR rule against abuse of vulnerable signed drivers. Restrict administrative privileges and driver-service installation. Inventory legitimate ThrottleStop deployments and monitor unexpected driver staging, loading, and associated security-process termination.
Remediation
Patch, then assume compromise.
Apply the vendor's security update according to its instructions when available. A verified fixed version is not identified in the available information. Remove or replace vulnerable driver installations where an update is unavailable, and prevent vulnerable copies from being reintroduced.
Exploits
16 exploits validated by Mallory's analysis. Hidden: 1 rejected by Mallory's analysis as not a working exploit; 1 not yet analyzed, such as Exploit-DB entries.
References
Frequently asked questions
- Is CVE-2025-7771 exploited in the wild?
- Yes. As of Nov 16, 2026, Mallory has reports of exploitation in the wild.
- Is there a public exploit for CVE-2025-7771?
- Yes. Mallory tracks 16 public exploits or proofs of concept for CVE-2025-7771, the earliest disclosed Aug 18, 2025.
- Is there a patch for CVE-2025-7771?
- Apply the vendor's security update according to its instructions when available. A verified fixed version is not identified in the available information.
- How severe is CVE-2025-7771?
- CVE-2025-7771 has a CVSS v4 score of 8.7 (High) and an EPSS score of 6.8% (94th percentile) as of Nov 16, 2026.
Recent activity
31 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.