Key summary: Epic Games says it is rebuilding Easy Anti-Cheat for Linux as EAC Linux v2 and will pilot it in Fortnite first, the step it says stands between Fortnite and a Linux release. Instead of a kernel driver, EAC Linux v2 will check for a signed kernel and modules, TPM 2.0, Secure Boot with well-known keys, measured boot, IOMMU, kernel lockdown, disabled kexec and the BPF security module, and run a systemd service only while a protected game is open. Epic gave no date for Fortnite on Linux and says the Steam Deck can't meet the requirements yet, though it is talking with Valve.

Fortnite is a step closer to running on Linux. In an October 14 post on its Epic Online Services site, Epic Games said it is rebuilding the Linux side of Easy Anti-Cheat (EAC) and will try the new version in Fortnite before offering it to other studios.

Why Fortnite isn’t on Linux yet

EAC has worked with native Linux games since 2014 and with Windows games run through Wine or Proton since 2021, Epic says. Each game has to opt in, though, and many haven’t, because the Linux version couldn’t protect games as well as the Windows one. Epic names that gap as the reason Fortnite skipped Linux, and says the game is “coming.”

The new version, EAC Linux v2, is meant to bring protection much closer to Windows levels. Epic plans to run it in Fortnite first, learn from the live test, and then open it up to other developers so their multiplayer games can reach Linux players.

How EAC Linux v2 works

On Windows, EAC uses a kernel driver while a game is running. The Linux rebuild won’t install a kernel module at all. It relies on security features Linux already has, plus Epic’s own eBPF code. The first time a player starts a protected game, they’re asked to install a systemd service, which only runs while that game is open.

Epic lists eight system requirements:

1. A kernel, and any loaded kernel modules, signed with a key on Epic’s well-known list. Out-of-tree drivers such as NVIDIA’s must meet the same rule.
2. TPM 2.0, switched on in the BIOS.
3. Secure Boot enabled, booting only with well-known keys.
4. Measured boot data recorded by the boot manager.
5. IOMMU on, with passthrough off (handheld devices are exempt).
6. Kernel lockdown in integrity mode, set at boot.
7. Kexec turned off at boot.
8. The BPF Linux Security Module loaded and active.

The well-known list currently covers Secure Boot keys from Canonical (Ubuntu, Linux Mint), Fedora, Universal Blue (Bazzite, Bluefin, Aurora), Debian, openSUSE, SUSE Linux Enterprise, Rocky Linux, AlmaLinux and the Microsoft UEFI CA. Epic runs the list for now and says it wants to open-source it and accept community additions.

Players don’t need to keep their PC locked down all the time: Epic suggests a separate boot entry for protected games, and says launching one without meeting the rules just shows an error, not a ban. Developers whose games already use the older Linux support can stick with it or move to v2.

Steam Deck and next steps

Epic says the Steam Deck doesn’t support the features v2 needs, but it’s talking with Valve and hopes to add support later. The company is contacting Linux distribution maintainers and plans a panel later this year with Fedora Project Leader Jef Spaleta.

What we don’t know yet

Epic’s post gives no release date or window for Fortnite on Linux, and no date for when other developers can start using EAC Linux v2.

Sources

• Epic Online Services — Awesome Gaming on Linux Without Cheating (primary)

CritFrame Newsroom · Written with AI tools from official sources. How we work