dbcve.org
Uncontrolled Resource ConsumptionWeakness · CWE-400

CVE-2025-61155

MEDIUM · 5.5 CVSS v3.1 Published 2025-10-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The GameDriverX64.sys kernel-mode anti-cheat driver (v7.23.4.7 and earlier) contains an access control vulnerability in one of its IOCTL handlers. A user-mode process can open a handle to the driver device and send specially crafted IOCTL requests. These requests are executed in kernel-mode context without proper authentication or access validation, allowing the attacker to terminate arbitrary processes, including critical system and security services, without requiring administrative privileges.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The GameDriverX64.sys kernel-mode anti-cheat driver (v7.23.4.7 and earlier) contains an access control vulnerability in an IOCTL handler. User-mode processes can open a handle to the driver device and send specially crafted IOCTL requests that execute in kernel-mode context without proper authentication or access validation. This allows unprivileged attackers to terminate arbitrary processes, including critical system and security services.

MitigationUpdate GameDriverX64.sys to a version newer than v7.23.4.7 that includes proper IOCTL access control validation. If no update is available, consider disabling the driver or implementing compensating controls until a patched version can be deployed.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate the GameDriverX64.sys driver file
    Search for GameDriverX64.sys on the system: Get-ChildItem -Path C:\ -Recurse -Filter GameDriverX64.sys -ErrorAction SilentlyContinue | Select-Object FullName
    Affected if The driver file exists on the system, meaning the anti-cheat software is installed
  2. Verify the driver version
    If the driver file is found, right-click the file, select Properties, then the Details tab to view the 'File version' or use PowerShell: (Get-Item 'C:\path\to\GameDriverX64.sys').VersionInfo
    Affected if The displayed version is 7.23.4.7 or any earlier version (e.g., 7.23.4.6, 7.23.4.0, etc.)
  3. Check if the driver is loaded
    Open an elevated command prompt and run: sc query GameDriver or driverquery /v | findstr GameDriver
    Affected if The driver shows as RUNNING or the service exists, meaning it is actively loaded in kernel memory
  4. Verify driver accessibility
    Check for the presence of the driver device object by inspecting running processes or using tools like WinObj to look for device objects related to GameDriver
    Affected if The driver device object exists and is accessible to user-mode processes, indicating the IOCTL interface is exposed
  5. Confirm unprivileged access capability
    Attempt to open a handle to the driver device using a non-admin account or verify that any user-process can access the driver interface (this may require elevated tools or code review)
    Affected if Non-privileged processes can obtain a handle to the driver and send IOCTL requests without authentication

A system is affected if GameDriverX64.sys is loaded and its version is 7.23.4.7 or earlier, enabling unprivileged processes to send IOCTL requests that can terminate arbitrary processes.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update GameDriverX64.sys to a version newer than v7.23.4.7 that includes proper IOCTL access control validation. If no update is available, consider disabling the driver or implementing compensating controls until a patched version can be deployed.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-61155 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-61155 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data