CVE-2025-61155: Arbitrary Process Termination in Tower of Fantasy GameDriverX64.sys
GameDriverX64.sys, the Tower of Fantasy anti-cheat kernel-mode driver, version 7.23.4.7 and earlier, contains an access control flaw in an IOCTL handler. A user-mode process can open a handle to the device object exposed by the driver and issue specially crafted IOCTL requests that are executed in kernel context without proper authentication or authorization checks. As described in the provided content, this allows an unprivileged local attacker to invoke driver functionality to terminate arbitrary processes, including security products and critical system services, from kernel mode.
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 allows a local unprivileged attacker to kill arbitrary processes in kernel context. In practice, this can be used to disable EDR, AV, and other security tooling, terminate critical Windows services, and materially weaken host defenses prior to follow-on activity such as credential theft, lateral movement, persistence, or ransomware deployment. The content specifically notes abuse in BYOVD scenarios to terminate security software before encryption.
Mitigation
If you can’t patch tonight, do this now.
Prevent untrusted or unnecessary kernel drivers from being loaded, including renamed copies of GameDriverX64.sys such as UpdateCheckerX64.sys noted in the content. Enable and enforce Microsoft vulnerable driver blocklist protections and HVCI/Memory Integrity where operationally feasible. Use application control/WDAC policies to restrict driver installation and loading, monitor for suspicious driver loads and device-handle access to the driver, and alert on attempts to terminate security processes from kernel context. Restrict local code execution opportunities for unprivileged users to reduce exploitability.
Remediation
Patch, then assume compromise.
Update or replace GameDriverX64.sys with a fixed version newer than 7.23.4.7 if available from the vendor. Remove the vulnerable driver from systems where it is not strictly required. Because the driver has been abused in BYOVD attacks, organizations should also block loading of the known vulnerable binary and any renamed copies, and ensure vulnerable-driver block policies are enforced where supported.
Exploits
2 exploits validated by Mallory's analysis. Hidden: 1 rejected by Mallory's analysis as not a working exploit.
Frequently asked questions
- Is CVE-2025-61155 exploited in the wild?
- Yes. As of Sep 25, 2026, Mallory has reports of exploitation in the wild.
- Is there a public exploit for CVE-2025-61155?
- Yes. Mallory tracks 2 public exploits or proofs of concept for CVE-2025-61155, the earliest disclosed Jun 25, 2026.
- Is there a patch for CVE-2025-61155?
- Update or replace GameDriverX64.sys with a fixed version newer than 7.23.4.7 if available from the vendor. Remove the vulnerable driver from systems where it is not strictly required.
- How severe is CVE-2025-61155?
- CVE-2025-61155 has a CVSS v3.1 score of 5.5 (Medium) and an EPSS score of 0.29% (21st percentile) as of Sep 25, 2026.
Recent activity
17 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.