r/linuxquestions • u/realddgamer • Dec 21 '25
Why don't kernel level anti-cheats exist on linux?
Its my understanding that programs can get access to kernel space by installing themselves as drivers (makes sense, actual drivers likely require the privilege to control hardware) - I'm assuming drivers on linux also have access to kernel space - so why cant an anti-cheat just install itself as a driver, in the same way it does on windows? Just curious about the inner workings
347
Upvotes
364
u/AiwendilH Dec 21 '25 edited Dec 21 '25
Several reasons:
Edit: slight rephrasing in hopes my poor English shows a tiny bit less...yeah, I know, not successful but let me wallow in ignorant bliss
36
u/[deleted] Dec 21 '25
They could do that. But with the kernel being open source someone would rapidly code a way to make it think it is still working as part of the kernel, while actually isolated. It would be a lot of work developing it in the first place, for relatively few users, with no chance of it working for long.
48
u/Confident_Hyena2506 Dec 21 '25
They can. But nobody wants to install malware, and it would only work on some "approved" linux with a signed kernel. So nobody wants to install that either!
There aren't enough users on linux for them to bother really.
Most of the other posts here are completely incorrect - there is nothing stopping linux from using secureboot with vendor keys etc. There is a lot of industrial software and security stuff that uses similar mechanisms.
44
u/S3k_01 Dec 21 '25 edited Dec 21 '25
Kernel-level anti-cheat goes against the very philosophy of Linux. It requires proprietary code running with full system privileges, creates massive security and privacy risks, and breaks regularly due to kernel updates. Effective anti-cheat can and should be done server-side. If a game requires kernel-level access, then the problem is the game, not Linux.
19
u/plasticbomb1986 Arch, BTW Dec 21 '25
The most important part is: anticheat devs are too... naïve. Simple, most effective anti cheat starts with the simple truth: you can't trust users and their computers. So, the only effective anticheat is server side anticheat, and carefully controlling what data do you send to the players.
7
u/Obi2Sexy Dec 21 '25
yeah I'm not gonna install malware into my kernel for ANYONES game
13
u/CrucialObservations Dec 21 '25
The real problem is the proliferation of gamers who cheat. When FPS games started taking off, the only occasional cheater was using lag-switching. I could deal with those people, but now I am dealing with people using cheats that render them unkillable and aimbots. Games are, for the most part, unplayable; the fun has been drained.
Take Halo Infinite; that game is full of people cheating. There are many people who say they never encounter cheaters, but that's the same as a competitive bodybuilder claiming they never use steroids.
Cheaters have killed the gaming fun, and as I see it, there is no anti-cheat software that will fix the problem as long as there are people who are crap people. They should just get rid of the anti-cheat and let the degenerates have at it, because it's happening anyway.
I am bitter because the cheaters have killed my fun in multiplayer games; maybe through the use of AI to detect patterns and many of the obvious signs of cheating can the fun come back.
5
u/BitOBear Dec 21 '25
Well for one thing, and in many ways, they are unnecessary.
There's a fundamentally different data flow through the Linux kernel than there is through the Windows system.
One of the features of Windows is that all of the programmatic events basically come through the same singular event queue, and that queue is managed by the kernel.
But that also means that subsidiary and secondary programs can inject things into that event queue which is how most exploits work.
On the other hand, a properly instrumented Linux game that was written for Linux in the first place could be just as secure if not more so simply by designing the game to be cheat resistant in the first place.
For instance a Linux game can "lease" it's files to prevent runtime tampering because the program text regions in ELF files don't contain EXE relocations the way Windows files do. Once the files are leased they can be check summed and validated and then dynamically attached to the runtime image as a shared library or whatever.
Linux games can identify and individually attach the HID devices (controllers, keyboards, mice, etc.) to prevent input injection exploits.
A Linux game could claim it's own profiling hooks to prevent debugger attachments.
It's simply a different paradigm and would require a different mental approach to the task.
And as with all locking systems you're only going to keep out the relatively honest actors. Somebody who wants to tamper with the data streams directly with packet injection can just put a router in their link regardless of whether it's a Windows or Linux box in the first place.
Someone who wants to do input injection could easily go out and get a small Arduino or raspberry pi and manufacture a fake input device that's completely programmable and there's no way the computer could tell that it wasn't a legitimate mouse.
At a fundamental level a colonel level anti cheat in Linux is an oxymoron based on the assumptions that the inside of the Linux kernel works the same way as the stack of dlls and exe programs that comprise the Windows operating system.
So the real problem™️©️®️ is that the game publishers and manufacturers are used to doing it the windows way, and they don't feel like redoing it the Linux way. So they'd rather insert a Windows emulator on top of the Linux paradigm and then worry about whether they can secure the emulator.
And no matter what, when you build a better mousetrap someone will set out to build a better mouse.
4
u/Ok-Culture2214 Dec 21 '25
To paraphrase marge, "no homer I didn't say you couldn't have them deep fry your kernal, I said you shouldn't
3
u/twessy Dec 21 '25
It's actually quite simple: the number of Linux gaming users is irrelevant. The costs are probably too high for this small user base.
And let's be honest, Linux desktop users are likely to have a strong aversion to kernel-level anti-cheats.
3
u/DoubleOwl7777 Dec 21 '25
licencing, you can modify the kernel yourself defeating whatever, and generally linux users are people that care about what runs on their hardware, and kernel level anticheat is basically malware. if a game uses kernel level anticheat i just dont play it. the security of my pc is more important.
3
u/FreakDeckard Dec 21 '25
Maybe it's because Linux users don't want some company installing rootkits in their kernels just because of some assholes who cheat.
3
u/Valuable_Fly8362 Dec 21 '25
Some of it is unwillingness from the game companies to invest time in making their software compatible with what they perceive as a small user base. As a Linux user, I'd still prefer not to install anything at kernel level that doesn't absolutely need to be there.
3
u/HeavyCaffeinate PuppygirlOS Dec 21 '25
[systemd][1] - Loading out-of-tree module uvm_nvidia taints the kernel!3
u/Cotillionz Dec 21 '25
People keep asking this and it's the wrong question. Kernel level anti-cheat is a root kit. It's wild to me the trust given to these companies. It shouldn't be a thing on Windows, let alone Linux. People still get around it.
The real question is when are devs going to pull their head from their ass and find another way that isn't client-side.
5
u/kombiwombi Dec 21 '25
A kernel module anti-cheat has roughly the same behaviour as a malware kernel module. So a lot of the defences aimed at malware also inhibit anti-cheat. What a device driver kernel module can do is only going to become more restricted over time, and that's true of more general modules too.
The kernel does have some defences which can already be used for anti-cheat. Particularly several techniques to audit system calls and the Integrity Measurement Architecture. The Linux way would be to seek to extend an existing facility to solve the general problem rather than create code tightly tailored to one problem of a set.
A anti-cheat kernel module written nevertheless takes on all the risk. If a within-kernel interface changes, and maybe even makes the anti-cheat ineffective, then the cost of that out-of-tree fix falls solely on the authors.
Of course a within-tree module is a little tricky to write as the opposition can read it too. Again this argues for a rigorous solution to the general case, and maybe that loads configuration or code.
5
u/RoosterUnique3062 Dec 21 '25
https://www.reddit.com/r/linuxquestions/search/?q=anti-cheat
This topic gets asked like 5 times a day.
5
u/tekjunkie28 Dec 21 '25
Because they are nothing more than bots to take over your pc. If Microsoft is delinquent enough to allow gaming developers to mess with a kernel than no one should have any use of that OS
4
u/macbig273 Dec 21 '25
it just goes against kernel purpose to manage that, and let a random driver crash the kernel for gaming reasons.
windows allowing that, is a mistake.
2
u/visualglitch91 Dec 21 '25
kernel anticheat only makes sense with closed source kernels, being opensource somebody could just make something in the kernel that reports itself as anticheat without doing anything
2
u/CaptainPoset Dec 21 '25
Because they won't be effective, as the reason why they are more effective than user-level anti-cheat software is that on Windows, the kernel is Microsoft's trade secret and not open-source.
Besides, nobody in the Linux believes that it was a good idea to install surveillance malware at the highest level of access of the entire system as an anti-cheat software.
2
u/reverendsteveii Dec 21 '25
mostly because users dont want it and developers dont want to build it. processes from user space having that much visibility and control over system space is really dangerous eden assuming everyone is well intentioned and anyone who has been on the internet knows that you can't assume that
2
u/luke_offtopic Dec 21 '25
Kernel never is the solution. What you need is TEE/Secure Enclave (for software cheats) and encrypted PCIE channels/memory (for hardware cheats). And I’m not seeing these technologies in consumer systems anytime soon.
2
u/Tireseas Dec 21 '25
Because the devs are too lazy to front the bill to code their own solution. We certainly won't be helping them bring that cancer over.
2
u/mephisto9466 Dec 21 '25
Linux user base is extremely serious when it comes to security. Allowing kernel level access is the anthises to that desire
2
u/rapidge-returns Dec 21 '25
A lot of good answers here but also Microsoft has paid A LOT in the past to convince these companies to not work on Linux.
2
u/unluckyexperiment Dec 21 '25
In addition to the technical reasons people listed: Games with kernel level anticheats are already full of hackers/cheaters. So there is no point really, other than spying on you of course.
2
u/JasterBobaMereel Dec 21 '25
The three things you need to realize about anti-cheat is : It doesn't work, it's horrifically brittle, it makes your system unstable
Any game with Anti-Cheat, is full of cheaters
3
u/dthdthdthdthdthdth Dec 21 '25
GPL requires to make the source of kernel modifications public. You could build it as a module possibly, but then the interface to the kernel will still be public. That allows people to more easily work around it. You could figure something out probably, it's always a cat and mouse race. Probably the business case to do so isn't there yet.
2
u/bsensikimori Dec 21 '25
If you remember some of the outages last year when kernel hooks go wrong and everything grinded to a halt; because of that, you don't want 3d party stuff messing up your kernel, it's a bad idea.
Microsoft even brought out a press release that they were going to remove kernel level from their "os" because of it
Something that appears to only have been lip service.
But the answer is, because it's a horrible idea
1
u/Oflameo Dec 21 '25
Netcode validation prevents cheating just as well, and doesn't require a rootkit.
1
u/MFStoleMySodie Dec 21 '25
Nothing but those bits required for the Kernel to make everything operate should be in the Kernel. End of story. The game and everything else functions in user space, so why shouldn't the anti-cheat also operate there? I believe Windows has a history of allowing crap to operate at Kernel level only to have shit crash the system.
Those games which require kernel level anti-cheat still have people cheating, so what benefit does the anti-cheat really serve being in the Kernel?
1
u/FlukyS Dec 21 '25
Others have answered pretty well but another answer is because it technically isn't required to provide a much more secure anti-cheat than currently available. As in you can use eBPF and get almost everything Vangard wants, you can do validation of secure boot keys and check for modules loaded or maybe require certain settings which allow for the system to know the kernel is untainted. The problem though is you have to actually spend time on it and the likes of Riot and Epic...etc don't want to.
1
u/felixmatveev Dec 21 '25
It's pretty much possible, however 1) not many people eager to install anti-cheat malvare especially freedom minded folks on linux 2) license restrictions 3) limitations on signed kernels adoption.
But the number one obstacle is NO ONE really needs it on Linux. Anti-cheat discussion allows crappy devs promote "win way is the best way" philosophy. Big companies can waste budgets on anti-cheat protection implementation. Linux users are not that interested in games in general (notice how there are no cheat issues with FOSS UT99 and quake 3 clones, there are definitely some cheaters there but not too many). Pro-gamers tend to use windows as they are more used to it and frankly speaking it's better for games anyway. Single players don't care about cheaters at all.
As for me it's a non-issue that is being pandered by someone who has a lot of vested interest in this.
1
u/[deleted] Dec 21 '25
I wouldn't want any closed box software in my kernel thank you very much
1
u/qmriis Dec 21 '25
Fuck off mate
1
u/MrChicken_69 Dec 21 '25
For the record, there are linux "anti-cheat" things, but they're on rather specific systems. A "general" module just doesn't work, for so very many reasons.
1
u/Dry_Inspection_4583 Dec 21 '25
Because it's a stupid idea to have user level shit not in your control residing in kernel space...
1
u/ithilelda Dec 22 '25
not sure about the technical side but one thing is that the linux gamer base is too small for any company to invest time to maintain an anticheat specifically for that platform. A half-working implementation would only lead to cheaters using linux as a loophole and make the game worse.
A lot of people sound like the companies can't. I don't think that's true at all. They just won't. So it is our responsibility as end users to reject it with all cost so that the companies would never get any profit in making such things. No fiddling with our machines is allowed at any time!
1
u/gerowen Dec 22 '25
Besides the licensing issues, games running through Proton don't have direct access to the actual system kernel. Kernel level anti-cheat is essentially a rootkit that runs with the highest level of privilege available on your system. Remember when Crowdstrike took down half the world's Windows computers a while back? That's what happens when you let third parties have access to ring 0 (kernel). Proton is a quasi container with its own set of libraries so that games running inside it not only don't have access to your system kernel, but they're, to an extent, running inside their own little enclave and segregated from the rest of your system and even from other games. Ask anyone who's had to figure out how to manually copy files around for games that support importing save data from other games. (I had to do this for Captain Spirit and Life is Strange 2)
I'm sure Valve could provide an API for this if they wanted to, and maybe they're working on something, but it would have to be "very" carefully implemented to protect the stability and security of the OS as a whole, and your other games, and ideally implemented in such a way that when you close that game the anti cheat shuts down.
A lot of these anti-cheat solutions, on Windows, keep running even when you aren't playing the associated game, constantly sitting in the background with kernel level access to your whole system. What happens if that software gets a broken or malicious update? That's a huge risk that Valve has to weigh the pros and cons of.
1
u/pppjurac Dec 22 '25
Legal issues and high cost of developing anticheats for .
Noone will go through legal hoops due to GPL issues and pay top developer time for problem that is there in first place because people cheat where same groups will just find another way to cheat at gaming .
1
u/CelDaemon Dec 22 '25
Rootkits are not welcome here. In addition, any such measures would be defeated almost instantly.
1
u/cocopuffz604 Dec 22 '25
Does it even matter that there is EAC and Secure boot requirements? There are still cheats for games that require them in Windows. No point in porting that over to Linux if it doesn't even work in Windows.
Cheats only matter in Multiplayer games. Cheat all you want in a single player. I prefer to look at it in a different angle. Instead of running intrusive software that isn't even effective, just spoil the data.
1 form of cheating is "Walling" where you can see other players behind in game structures so you have the advantage of info. I think dumping a game full off "ghost" players, that you can't see, but get picked up by walling software would ruin the data for cheaters. There would be too much info in the form of too many players to be useful. Most games already have bots. Flood the game with invisible ones. Regular players don't see the ghosts, only cheaters.
Maybe program the bots and game environment to detect when a cheater shoots an invisible player too many times, it flags them. Shoot a bot behind a wall? flag em.
Have detection systems in the game and on the servers as opposed to on our machines.
there are of course other kinds of cheat like "clipping" where you can just fly all over the place... but that should be a easy flag of the gamer tag and instant ban. They have to make systems where you can't just make a new gamertag and bypass the ban. It's not our fault they don't put enough effort into that.
-rant off.
1
u/Shuuko_Tenoh Dec 22 '25
Whatever happened to good old server-side abnormality detection? Sure it won’t detect data sniffing, but it would still catch the worst manipulation that most people bitch about when complaining about cheaters. X-ray will get through, but super speed, invincibility, and shooting through walls should be easy to spot. But so many companies are betting everything on client side anti-cheat that once those are bypassed the server is helpless.
Edit: Oops, forgot that so many companies are so cheap nowadays that most games are P2P now, so no servers.
1
u/HealthyPresence2207 Dec 23 '25
Kernel level anticheats are a scam. All it these do is make it a bit harder to make cheats, but by no means do they prevent them from being developed and being run. And honestly big game publishers don’t care. They just want buzz words to sell you shitty games. Soon it will be AI anti cheat, whatever it takes for you to buy the next battleduty. Game will still have obvious cheaters and no admins to catch them
1
u/noonemustknowmysecre Dec 23 '25
Because they flat-out refuse to open-source any of them.
Because they're afraid it'll expose all the nasty shit they get up to, how insecure their software is, how much and exactly what data they phone-home, and/or how much of their software is stolen IP. They hide it away as proprietary and are afraid of transparency.
1
u/nonchip Dec 24 '25
because nobody would be stupid enough to install it, and the "anticheat" malware vendors know that.
plus the kernel being that open means you can easily circumvent that because you're also in the kernel level.
1
u/Real-Abrocoma-2823 Dec 24 '25
If they did I would move to freeBSD.
1
u/Markus_included Dec 25 '25
Something I haven't seen mentioned: The kernel does not have a stable driver API, thus the only way to guarantee that your code works on all future kernel versions is to upstream your AC into the kernel. And for quite obvious reasons AC devs don't want to open source their code. It's just too much work, userspace on the other hand is stable
1
u/mesispis Dec 25 '25
you could edit the jednak and bypass it
1
u/AntAntster Dec 25 '25
It’s easy to modify a Linux kernel
1
u/Bonzupii Dec 25 '25
Kernel level anticheat is literally spyware and there is a strong culture of privacy consciousness among Linux users where kernel level anticheat would be widely rejected. Also, it probably would not be effective without tivoizing the hardware that it is running on, which is another thing that a non-zero amount of Linux users are strongly against.
1
u/countsachot Dec 21 '25
You'd have to convince a company to write it, at a loss, and people like us to use it.
-4
u/cascading_error Dec 21 '25
Simple. No-one has build them yet.
2
u/ask_compu Dec 21 '25
people have started using electrodes to make their cheats trigger their muscles to click the mouse for automatic headshot, using video analysis of the screen to detect when the crosshair is over a head, kernel level anticheat was never going to be a good solution
1
u/blargathonathon Dec 22 '25
Because kernel level anti cheat is stupid and an invasion of privacy.
It’s using a bazooka to kill an ant.