Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2025-61155: Arbitrary Process Termination in Tower of Fantasy GameDriverX64.sys

Published Oct 28, 2025 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS5.5Medium · v3.1
EPSS0.29%21st percentile
CISA KEVNoNot listed
In the wildReported13 exploitation records in Mallory
IdentifiersCVE-2025-61155CWE-284

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.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

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.

Public exploits

Exploits

2 exploits validated by Mallory's analysis. Hidden: 1 rejected by Mallory's analysis as not a working exploit.

View more in app →
CVE-2025-61155This repository is a real exploit/advisory package for CVE-2025-61155, a local Windows BYOVD vulnerability in the signed Tower of Fantasy anti-cheat driver GameDriverX64.sys (affected versions <= 7.23.4.7). The repo is not framework-based; its main executable artifact is poc/poc.cpp, while the rest of the repository is documentation, detection content, mitigation guidance, and IOC material. Repository structure: 16 files total. The only exploit code is poc/poc.cpp (C++). Detection content includes detection/cve-2025-61155.yar and detection/iocs.md. Extensive markdown documentation explains reverse engineering, exploitation, detection, mitigation, and in-the-wild abuse. The vulnerable driver binary itself is intentionally not included; sample/SAMPLE.md documents its hashes, signer, and provenance. Exploit capability: the PoC performs arbitrary local process termination by abusing the driver's weak access controls. It first loads DLLs named QmGUI.dll, QmGUI4.dll, and gameuirender.dll to satisfy the driver's filename-only IRP_MJ_CREATE verification. It then opens the device \\.\HtAntiCheatDriver and sends DeviceIoControl with IOCTL 0x222040 and an 8-byte structure containing magic 0xFA123456 and a target PID. According to the included reverse-engineering notes, the driver then calls ZwOpenProcess(GENERIC_ALL) and ZwTerminateProcess in kernel context, allowing termination of arbitrary processes, including PPL-protected AV/EDR services. The PoC defaults to targeting notepad.exe, but the primitive is clearly an EDR-killer when pointed at security products. Attack vector: strictly local. The exploit does not expose remote networking behavior and does not contact C2 or external services. Its success depends on the vulnerable driver already being installed/loaded on the host. The documentation also notes in-the-wild abuse where threat actors rename the driver to UpdateCheckerX64.sys and package it in tooling such as polers.dll. Notable fingerprintable artifacts extracted from the repo include the device paths \\.\HtAntiCheatDriver, \Device\HtAntiCheatDriver, and \??\HtAntiCheatDriver; the verification DLL names QmGUI.dll, QmGUI4.dll, and gameuirender.dll; the vulnerable driver names GameDriverX64.sys and UpdateCheckerX64.sys; the leaked PDB path E:\PWRD\AntiCheatGit\HtDriver2.0_maomx\output\x64_Release\PwrdDriver\app\PwrdDriver.pdb; the vulnerable IOCTL 0x222040; and the magic constant 0xFA123456. Overall, this is an operational PoC with a basic hardcoded payload rather than a fully weaponized framework.sf0rzin · Disclosed Jun 25, 2026 · cpp · yara · localOperationalCVE-2025-61155This repository is a real exploit-focused research repo for CVE-2025-61155, not just a README. It documents and demonstrates a local BYOVD-style abuse path in the signed Windows anti-cheat driver GameDriverX64.sys used by Tower of Fantasy. The core exploit capability is arbitrary process termination from kernel context: an unprivileged local process can satisfy the driver's weak create-time gate by loading any DLL named QmGUI.dll, QmGUI4.dll, or gameuirender.dll, then open the exposed device \\.\HtAntiCheatDriver and send IOCTL 0x222040 with an 8-byte buffer containing magic 0xFA123456 and a target PID. The driver then performs ZwOpenProcess(GENERIC_ALL) and ZwTerminateProcess in kernel mode, allowing termination of arbitrary processes including protected AV/EDR services. Repository structure is primarily documentation-heavy, with one actual PoC source file and one YARA detection ruleset. Key files are: poc/poc.cpp (minimal C++ PoC and main entry point), advisory.md (formal advisory), docs/01-technical-analysis.md (reverse-engineering teardown of the driver internals and exploit chain), docs/02-exploitation.md (walkthrough of the abuse flow), docs/03-detection.md and detection/* (YARA and IOC content), docs/04-mitigation.md (blocklist/WDAC guidance), and docs/05-in-the-wild.md (threat-actor usage context). The vulnerable driver binary itself is intentionally omitted; sample/SAMPLE.md provides hashes, signer, and provenance instead. The PoC is operational but basic rather than weaponized: it defaults to targeting notepad.exe, uses hardcoded constants, and does not include driver installation or advanced targeting logic. Still, it clearly demonstrates the exploit chain and the main offensive outcome: local disabling of security tooling via a vulnerable signed driver already reported as abused in the wild.sys0xFF · Disclosed Jun 25, 2026 · cpp · yara · localOperational
FAQ

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.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidence9Every report linking this CVE to a named adversary.
Associated malware20Malware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity4Community discussion across Reddit, Mastodon, and other social sources.