
Technical advisory detailing three local privilege escalation vulnerabilities (CVE-2026-12166/7/8) in the Little Orbit GFAC kernel driver, including NULL pointer dereference, improper access control, and arbitrary kernel memory write leading to SYSTEM compromise.
| CVE IDs | CVE-2026-12166, CVE-2026-12167, CVE-2026-12168 |
| Vendor | Little Orbit |
| Product | GamersFirst Anti-Cheat (GFAC) Driver (GFAC_Sys_x64.sys) |
| Affected Versions | No version information is embedded in the driver binary. Sample analyzed: SHA-256 b6748d7da5759dee7d5f2f32b0326b4edb7b2135a0e4a6d5ff26aef1e139d8b2 |
| Vulnerability Types | NULL Pointer Dereference (CWE-476), Improper Access Control (CWE-284), Arbitrary Kernel Memory Write (CWE-787) |
| Impact | Denial of Service (BSOD), Privilege Escalation to SYSTEM |
| Attack Vector | Local |
| Privileges Required | Low (any local user) |
| Tested On | Windows 10/11 x64 |
| Researcher | Lucian Alexandru Necula |
The GamersFirst Anti-Cheat (GFAC) kernel-mode driver, GFAC_Sys_x64.sys, exposes privileged functionality to user-mode applications through a minifilter communication port. Insecure handling of user-controlled input received through this port results in multiple local vulnerabilities, ranging from denial-of-service conditions to full privilege escalation to SYSTEM.
Three distinct issues were identified and are tracked together in this advisory:
GFAC_Sys_x64.sysThe driver's initialization and request-handling logic contains a code path that can be driven into dereferencing a NULL pointer by a local, unprivileged caller. Triggering this path causes the driver to read or write through a NULL address, crashing the system (BSOD) and allowing an attacker to repeatedly disrupt availability.
The minifilter communication port does not enforce a sufficiently restrictive security descriptor. As a result, low-privileged, non-administrative users can open a connection to the port and reach privileged functionality that should be restricted to trusted processes only. This significantly widens the driver's attack surface and is a direct enabler for exploitation of the other issues in this advisory.
Messages received through the communication port are processed without adequately validating user-supplied memory addresses before they are used as the destination of a write operation. A local attacker can submit a crafted request containing an attacker-controlled destination address and data value, causing the driver to write arbitrary data to kernel memory. This write-what-where primitive can be leveraged to overwrite sensitive OS structures — such as a process's security token — resulting in escalation to SYSTEM privileges.
Note: No proof-of-concept exploit code is published in this advisory. The technical description above is intentionally limited to what is necessary to understand and remediate the issues.
Because GFAC is distributed as part of anti-cheat tooling bundled with multiple games, the affected driver may be present — and loadable — on systems well beyond those actively engaged in gameplay at the time of exploitation.
For defenders / system owners:
GFAC_Sys_x64.sys as vulnerable pending a vendor fix.For the vendor:
| Date | Event |
|---|---|
| 2026-04-01 |
Discovered and reported by Lucian Alexandru Necula.
| Vendor (Little Orbit) contacted directly to report the vulnerabilities |
| 2026-04-20 | Case submitted to CERT/CC for coordinated disclosure |
| — | No response received from the vendor throughout the coordination process |
| — | CVE-2026-12166 / -12167 / -12168 — currently RESERVED, pending public assignment on CVE.org/NVD |
| 2026-07-02 | Public advisory published (this document) |