Skip to content

!!IMPORTANT!! Discord server termed, join the new one! discord.gg/QNkCQDWtGD

Sense

Kernel-Level Anti-Cheat: How It Works, Who Uses It

How kernel-level anti-cheat systems work at Ring 0, why games use them, the privacy debate, and a full list of major kernel anti-cheats in gaming today.

By SensePublished

What Is Kernel-Level Anti-Cheat?

Kernel-level anti-cheat refers to any anti-cheat system that installs and operates a driver at the kernel level of your operating system. In technical terms, this means the anti-cheat runs at Ring 0, which is the most privileged execution level on x86 processors. At Ring 0, software has unrestricted access to all hardware and memory on the system, the same level of access that the Windows kernel itself operates at.

This stands in contrast to user-mode anti-cheat systems that run at Ring 3, the standard privilege level for applications. User-mode software can only see what the operating system allows it to see, which means sophisticated cheats can hide from it by manipulating the OS interfaces that the anti-cheat relies on.

Why Do Anti-Cheats Need Kernel Access?

The escalation to kernel-level anti-cheat is a direct response to the escalation of cheating techniques. Understanding this arms race helps explain why game developers accept the risks and controversies that come with kernel-level access.

The Arms Race

In the early days of online gaming, cheats were simple programs that ran alongside the game and modified its memory. Anti-cheats could detect these by scanning for known cheat programs from user mode. This worked for a while, until cheat developers started hiding their software.

The progression looked something like this:

  1. User-mode cheats: Simple memory editors and game modifiers. Detectable by user-mode anti-cheat.
  2. Hidden user-mode cheats: Cheats that used techniques like DLL injection, process hollowing, and API hooking to hide from user-mode scanners. Anti-cheats had to get more sophisticated.
  3. Kernel-mode cheats: Cheat developers moved to kernel drivers, giving their software the same access level as the operating system. From the kernel, a cheat can intercept and manipulate any user-mode anti-cheat's queries, making itself effectively invisible.
  4. Kernel-mode anti-cheat: The only way to detect kernel-mode cheats reliably is from the kernel level itself. Anti-cheat developers followed the cheaters into Ring 0.
  5. Hypervisor-level cheats: Some cheat developers have moved even deeper, using hypervisor technology to sit underneath the operating system entirely. This is cutting-edge territory that kernel anti-cheats are still developing countermeasures for.
  6. Hardware-level cheats (DMA): The newest frontier involves dedicated hardware devices that read game memory directly through the PCIe bus, completely bypassing software detection. Kernel anti-cheats are developing techniques to detect these as well.

At each stage, cheat developers found ways to evade the current level of detection, forcing anti-cheat developers to go deeper. Kernel access is not an arbitrary choice but rather a necessary response to the sophistication of modern cheating.

What Kernel Access Enables

Running at Ring 0 gives anti-cheat systems several critical capabilities:

  • Complete process visibility: No user-mode hiding technique can conceal a process from a kernel-level observer. The anti-cheat can enumerate all processes, threads, and modules on the system regardless of what tricks they use to hide.
  • Memory integrity: The anti-cheat can verify that the game's memory has not been tampered with and can detect any program that is reading game memory, even if that program is trying to hide its access.
  • Driver monitoring: The anti-cheat can watch for suspicious drivers being loaded, check driver signatures, and prevent known cheat drivers from loading.
  • System call interception: By monitoring the System Service Descriptor Table and other kernel structures, the anti-cheat can detect when cheats attempt to manipulate system calls.
  • Hardware access monitoring: Kernel access allows the anti-cheat to observe direct hardware interactions, which is important for detecting DMA-based cheats.

Major Kernel-Level Anti-Cheat Systems

Several anti-cheat solutions currently operate at the kernel level. Each has its own approach, strengths, and weaknesses.

Riot Vanguard

Riot Games' Vanguard is perhaps the most well-known kernel-level anti-cheat, largely because of the controversy it generated when it launched with Valorant in 2020. Key characteristics:

  • Always-on driver: Vanguard's kernel driver loads at system boot and runs continuously, even when you are not playing a Riot game. This was the most controversial aspect of its design.
  • TPM 2.0 requirement: Vanguard requires Trusted Platform Module 2.0 and Secure Boot to be enabled on Windows 11, using hardware-level trust to verify system integrity.
  • Strict enforcement: Vanguard blocks games from launching if it detects certain software conflicts, vulnerable drivers, or disabled security features.
  • Games protected: Valorant and League of Legends.

Easy Anti-Cheat (EAC)

Owned by Epic Games, EAC is one of the most widely deployed anti-cheat solutions:

  • On-demand driver: Unlike Vanguard, EAC's kernel driver loads only when a protected game starts and unloads when it closes.
  • Broad adoption: Used by dozens of games including Fortnite, Apex Legends, Rust, Dead by Daylight, and Elden Ring.
  • Free for developers: Epic offers EAC free to developers using Unreal Engine and Unity, which has driven widespread adoption.
  • Cross-platform: EAC supports Windows, Linux (through Proton/Wine compatibility), and some console platforms.

BattlEye

BattlEye is a veteran anti-cheat system that has been protecting games since the early 2000s:

  • Kernel driver: BattlEye uses a kernel-level driver that loads during gameplay.
  • Extensive game list: Protects titles like PUBG, Rainbow Six Siege, Escape from Tarkov, DayZ, and Arma series.
  • Aggressive scanning: BattlEye is known for thorough system scanning that sometimes triggers false positives with legitimate software.
  • Ban wave strategy: BattlEye frequently uses delayed ban waves to obscure exactly which detection method caught a cheat.

ACE (Anti-Cheat Expert)

Tencent's proprietary anti-cheat system:

  • Kernel driver on PC: ACE loads a kernel driver during gameplay on Windows.
  • Strong mobile protection: ACE was originally designed for mobile games and has robust Android and iOS detection.
  • Games protected: Arena Breakout: Infinite, PUBG Mobile, Honor of Kings, CrossFire, and other Tencent titles.
  • Machine learning focus: ACE leverages Tencent's massive player data for behavioral analysis.

nProtect GameGuard

Developed by INCA Internet, GameGuard has been used primarily in Korean and Asian MMOs:

  • Deep system monitoring: GameGuard monitors system processes, files, and memory with kernel-level access.
  • Controversial reputation: GameGuard has historically been criticized for aggressive behavior, including blocking legitimate software and causing system instability.
  • Games protected: MapleStory, Lineage, and various other Asian online games.

XIGNCODE3

Another Asian-market anti-cheat that operates at kernel level:

  • Kernel driver: Loads during gameplay with deep system scanning.
  • MMO focused: Primarily used in Korean and Japanese MMOs and online games.
  • Data collection controversy: XIGNCODE3 faced criticism for collecting and transmitting detailed system information.

Denuvo Anti-Cheat

Not to be confused with Denuvo DRM, the anti-cheat product from Irdeto also operates at kernel level:

  • Kernel driver: Loads during gameplay sessions.
  • Limited adoption: Used by fewer games than EAC or BattlEye, but protecting some notable titles.
  • Focus on competitive integrity: Designed specifically for multiplayer scenarios rather than DRM enforcement.

The Privacy and Security Debate

Kernel-level anti-cheat is one of the most debated topics in PC gaming. The arguments on both sides are substantive.

Arguments Against Kernel Anti-Cheat

Security vulnerability surface: A kernel driver is a potential attack vector. If an anti-cheat driver contains a vulnerability, an attacker could exploit it to gain kernel-level access to the system. This is not theoretical. Security researchers have found and reported vulnerabilities in anti-cheat drivers in the past.

System stability risks: Buggy kernel drivers can cause Blue Screen of Death (BSOD) crashes. Anti-cheat updates that introduce driver bugs can crash thousands of systems simultaneously.

Excessive access: Critics argue that a game should not need the same level of system access as the operating system itself. The anti-cheat can theoretically read any file, monitor any process, and access any hardware on the system.

Privacy implications: Kernel access means the anti-cheat can observe everything on the computer. While anti-cheat companies state they only collect game-related data, the technical capability exists to collect much more.

Software compatibility: Kernel anti-cheats sometimes block or conflict with legitimate software, including accessibility tools, hardware monitoring programs, and even other security software.

Arguments For Kernel Anti-Cheat

Necessity: Without kernel access, anti-cheats cannot detect kernel-level cheats. Allowing cheaters to operate freely would destroy the competitive integrity that makes games worth playing.

Equivalent trust: Players already trust numerous kernel drivers on their systems, from graphics drivers to antivirus software to hardware controller drivers. An anti-cheat driver is not fundamentally different.

Auditing and accountability: Major anti-cheat companies operate under legal frameworks that restrict data collection. They face real consequences for privacy violations, creating incentives to behave responsibly.

Proven effectiveness: Games that deploy kernel-level anti-cheat have demonstrably lower cheating rates than those relying solely on user-mode detection or server-side analysis.

How Kernel Anti-Cheat Affects Hardware Bans

Kernel-level access is directly connected to the effectiveness of hardware bans. Because the anti-cheat runs at Ring 0, it can:

  • Read hardware serial numbers directly from device firmware rather than relying on operating system APIs that can be intercepted
  • Access TPM keys and Secure Boot state for hardware attestation
  • Detect attempts to spoof hardware identifiers at the driver level
  • Monitor for patterns consistent with HWID spoofing software

This makes kernel anti-cheat hardware bans significantly harder to evade than those issued by user-mode systems. An HWID spoofer that works against a user-mode anti-cheat may fail against a kernel-level one because the anti-cheat can see past the spoofing layer.

This is why solutions like Sense AC's HWID spoofer are specifically designed to operate at the appropriate level to address kernel anti-cheat detection. A surface-level approach is not sufficient when the anti-cheat has deep system access.

The Linux and Steam Deck Question

Kernel-level anti-cheat has complicated the relationship between gaming and Linux. Most kernel anti-cheats are designed for Windows and do not natively support Linux. However, the growth of Steam Deck and Proton compatibility has forced changes:

  • EAC: Epic added official Proton compatibility for EAC, allowing many EAC-protected games to run on Linux and Steam Deck.
  • BattlEye: Also added Proton support, though adoption by individual game developers has been inconsistent.
  • Vanguard: Does not support Linux at all. Valorant cannot be played on Linux systems.
  • ACE: Does not officially support Linux.

The challenge is that kernel-level operations work very differently on Linux compared to Windows. Anti-cheat developers have to maintain separate detection systems for each platform, which increases development cost and complexity.

Looking Ahead

The future of kernel-level anti-cheat likely involves several trends:

  • Hardware attestation: Deeper integration with TPM 2.0, Secure Boot, and platform security features to create hardware-rooted trust chains that cheats cannot forge from software alone.
  • Hypervisor-based detection: Some anti-cheat systems may move to hypervisor level to counter hypervisor-based cheats.
  • AI-powered behavioral analysis: Machine learning models will become increasingly important for detecting novel cheats based on gameplay behavior rather than software signatures.
  • Cloud gaming integration: As cloud gaming grows, some anti-cheat processing may move to the cloud where the game already runs, reducing the need for client-side kernel access.

Conclusion

Kernel-level anti-cheat is a controversial but effective approach to maintaining competitive integrity in online games. It exists because cheaters pushed anti-cheat developers into an arms race that led to the deepest levels of the operating system. Whether you view it as a necessary evil or an unacceptable intrusion, it is the reality of modern multiplayer gaming. For players who end up on the wrong side of a kernel-level hardware ban, understanding how these systems work is essential for evaluating your options, whether that means appealing the ban, waiting it out, or using a specialized tool like Sense to get back in the game.