On October 14, 2026, Epic Games announced plans to bring Fortnite to Linux. The preview of the new Epic Games Launcher, released the same day, supports Linux for the first time, so the entry point for delivering the game is starting to take shape. However, before anyone can play Fortnite on Linux, Epic must rework its anti-cheat software, Easy Anti-Cheat (EAC), and coordinate with the maintainers of Linux distributions. The Steam Deck also does not currently meet the requirements of the new approach. To turn this announcement into actual play on your own machine, you need to tell apart the support conditions for the launcher and those for the game itself.
Different support conditions for the launcher, EAC, and Fortnite
The new Epic Games Launcher can be tried on Linux as well as Windows and macOS. In its official announcement, Epic explains that it will rebuild EAC and, once it has made enough progress with distribution maintainers, deliver Fortnite to Linux through the launcher. It has not given a specific release date.
In Epic's October 14, 2026 announcement, the Linux launcher release, compliance with the EAC Linux v2 requirements, and Fortnite's launch are separate stages.
| Item | Announced / released status | Conditions affecting use |
|---|---|---|
| Epic Games Launcher | Linux preview released | Per the FAQ, supported OSes are Ubuntu 22.04 LTS or later, Fedora 43 or later, and Debian 12 or later |
| EAC Linux v2 | New approach built; required security conditions published | The device and boot configuration must meet requirements such as signing and TPM |
| Fortnite | Linux release planned; to be used for early validation of EAC Linux v2 | Will launch only after support among maintainers is broad enough; no date announced |
The table sorts Epic's announcement of the same day, the requirements and FAQ in the EAC technical blog, and the launcher FAQ by item and release status. The EAC requirements may change, so the table is not a guarantee that anything will work on real hardware.
For example, even if the launcher runs on a supported OS, that alone does not tell you whether you can join Fortnite's online matches. The launcher FAQ also explains that only the launcher itself runs natively on Linux, and that because many games are built for Windows, a compatibility layer may be needed. This announcement does not settle whether Fortnite will ship as a native Linux executable or run through a compatibility layer.
No dedicated kernel module, but the boot environment is verified
EAC has supported Linux for some time. According to Epic, it has supported native Linux games since 2014, and Windows games run on Linux through Wine or Proton since 2021. Even so, Epic says it could not offer Fortnite because the previous Linux implementation could not deliver the same level of protection as the Windows version. Whether to enable support was left to each game.
The new EAC Linux v2 tries to narrow that gap using Linux's own security features. It does not install a dedicated anti-cheat kernel module equivalent to the Windows one; instead, it combines a systemd service with eBPF programs. The service runs when a protected game is launched and stops when the game exits.
Even without a dedicated module, the OS must meet several conditions. eBPF works with Linux security features to restrict other processes from reading or writing the game's memory and to monitor for suspicious behavior. The premise underlying all of this is whether the kernel running the game can be trusted.
Epic requires the kernel and kernel modules to be signed with signing keys it recognizes. Modules distributed separately from the kernel itself, such as NVIDIA GPU drivers, must also be built by an organization and signed with an approved key. The system is not designed to accept user-modified kernels under the same conditions.
Checks continue at boot time. Secure Boot verifies the signatures of the code that starts up, while TPM 2.0 and measured boot record which code and configuration actually started the system. Using both mechanisms combines signature checks with verification of the boot history. Epic requires TPM 2.0 and Secure Boot to be enabled in the BIOS.
In addition, kernel lockdown in integrity mode, which restricts modifications to the kernel even by administrators, and BPF LSM must be enabled. kexec, which switches to another kernel without a full reboot, must be disabled. This is because kexec could cause the measured boot history to no longer match the kernel that is currently running.
There are also conditions for the IOMMU, which controls access to memory from external devices. Epic explains that on non-handheld devices, the IOMMU must be enabled in both the BIOS and the Linux kernel, with passthrough disabled. In other words, whether you can simply install the game and play depends on your distribution's default settings and your device's configuration.
The signing key list and the Steam Deck's limits
The list of signing keys Epic recognizes includes Canonical's keys used for Ubuntu, as well as keys for Fedora and Debian. Keys for openSUSE and for Universal Blue, used by Bazzite and others, are also listed, but this is a list of keys EAC uses to verify systems. It should be kept distinct from any certification that Fortnite works on a given distribution.
For the Steam Deck, the technical blog's FAQ draws a clear line. It currently does not support the features EAC Linux v2 requires, and Epic says it is talking with Valve and hopes to support it in the future. The breakdown of the missing features and the timing of support have not been announced. The fact that a key for Bazzite is on the list cannot be read as meaning it will also be usable on the Steam Deck.
On the other hand, a configuration that meets EAC's conditions does not need to be used all the time for every purpose. Epic explains that a dedicated boot entry can be set up for playing protected games. That leaves room to switch between a configuration used for work or development and one with signing and boot settings aligned for gaming.
There is a caveat for users who have enrolled their own keys, however. When booting through the shim used to start Linux, an enrolled Machine Owner Key (MOK) is often trusted for kernel module signature verification, regardless of whether it was actually used for that boot. For this reason, EAC Linux v2 requires every enrolled MOK to be a key Epic recognizes. The explanation does not suggest that separating boot entries alone lets you use any custom configuration alongside it.
If a protected game is launched without meeting the conditions, an error message will be displayed. Epic says it will not suspend an account for cheating on that basis alone.
Validating on Fortnite first, then other games
Epic plans to test EAC Linux v2 first in Fortnite's live environment and improve it based on the results. After validating its effectiveness, it will offer it to other game developers. Here too, the goal of achieving protection close to that of the Windows version needs to be read separately from the result that it actually works in real matches.
For games that already enable the existing EAC Linux support, an option remains. Developers can keep using the old implementation to prioritize compatibility or switch to v2 to strengthen anti-cheat measures, so the plan is not to move all existing titles to the new requirements at once.
Distribution-side settings will also matter in broadening support. Epic has called on maintainers to cooperate and says it will align configuration requirements and add signing keys to the list. Epic will manage the list at first, with the aim of open-sourcing it in the future. If more distributions meet the necessary conditions by default, users will have fewer settings to change themselves, according to Epic.
Beyond the Fortnite validation results, whether your distribution and device can meet the requirements will be what determines whether you can start playing. If coordination with maintainers advances and the protection is shown to be effective in a live environment, Epic could bring the mechanism it tested with Fortnite to other competitive games.