XanMod drops two Linux kernels on the same day, splitting the community between mainline and LTS
Its performance-tuned 7.2.10 and 6.18.56 builds both land today, with a real-time variant a week earlier.
XanMod is one of those things Linux enthusiasts quietly love and distribution maintainers mostly ignore. It's a kernel project that doesn't write any code of its own. Instead it takes the vanilla upstream Linux kernel, layers on a performance patchset, and compiles it with aggressive, CPU-targeted optimizations. The latest pair, 7.2.10-xanmod1 on the mainline tree and 6.18.56-xanmod1 on LTS, both went out today.
The project has been going since 2015, and it's the work of Alexandre Frade, a developer based in Catalonia. He's one of the more prolific maintainers of these repackaged kernels, and XanMod has quietly become the default tuning option for x86-64 systems running Debian-based distros. That's a big chunk of the desktop and gaming market, for what it's worth.
The mainline/LTS split
Both flagship builds hit the same day, which is more deliberate than it looks. You get a clean choice: 7.2.10 rides the current stable mainline series (with 7.3 already in candidate form), meaning newest hardware support and freshly merged features, but a short shelf life. 6.18.56 sits on an LTS tree that XanMod projects to stay maintained through December 2028.
The mainline branch will be superseded within months, of course. But 6.18 joined the long-term-support club back in late 2025, sitting alongside XanMod's other actively maintained LTS trees, 6.12, 6.6, and 6.1. If you're running a production system or a workstation you don't want to churn, LTS is the safe bet.
Not quite the same day, though. The real-time variant, 6.18.55-rt-xanmod1, dropped a week earlier on October 3. PREEMPT_RT builds only exist on the LTS branch, since low-latency scheduling is exactly the kind of stability-focused workload that keeps you off the mainline bleeding edge. Head here to the GitLab releases pages if you want the direct links.
This isn't a new kernel, it's a tuned one
The headline here isn't any single feature. It's the whole philosophy. XanMod's value is that it compiles the kernel with LLVM ThinLTO link-time optimization, software pipelining, and polyhedral loop transforms, then picks instruction sets based on your CPU tier. You can build for v2 (roughly 2009-era hardware) or v3 (Haswell and later).
The third-party patchset it ships with, GPLv2, does a lot of the legwork too. Google's BBRv3 congestion control is built in and set as default, so your network stack plays nicer under load. Cloudflare's TCP collapse processing, netfilter full-cone NAT for gamers, and a hardware-offload target for packet processing round it out.
There are also the enthusiast favorites. PCIe ACS override lets you do multi-GPU passthrough in VMs, Android Binder IPC enables Waydroid containers, and the Steam Deck embedded-controller sensor support shows up, for reasons that remain a mystery to everyone outside the gaming crowd. On top of that, it runs Google's multigenerational LRU and XanMod-tuned sched/cache scheduler out of the box.
That scheduler work is worth flagging. The 7.2.10 build carries sched_ext / sched/cache fixes, including one that closes a use-after-free which messed up last-level-cache scheduling across sockets. For anyone pushing threads across multiple CPUs, that's a genuinely visible change. Not just a line in a changelog.
The numbers back up the "hardening over features" read. The 7.2.10 changelog lists roughly 425 patches with about 145 marked as fixes, 22 memory leaks, 18 use-after-frees, 13 race conditions, a cluster of bounds-check and overflow repairs. The largest single category was the I/O sensor tree, with about 49 patches of mostly defensive hardening. 6.18.56 trails slightly at around 400 patches and 133 fixes. That's standard for a stable point release: the job is to stop things breaking, not to add new toys.
One area of interest, though. The LTS branch carries five patches targeting Rust's kernel devres subsystem, fixing race conditions in a piece of code written in Rust rather than C. Rust, in other words, keeps earning its keep inside the kernel, and these maintenance fixes track that slow but steady expansion.
Pick your build and check your drivers
XanMod splits its packages by both kernel line and CPU generation. The main x64v2 build covers 2009-era CPUs and later, while x64v3 targets 2015-era hardware forward and is the recommended default. There's an x64v1 option that stretches back to Pentium 4 and Core 2 machines, an edge series for people who want rolling updates, and the RT build for real-time work. All of it ships as .deb packages plus a source tarball and a patch file if you'd rather apply it yourself.
Supported distros are Debian-based, ranging from bookworm to rolling sid, including Ubuntu flavors like noble. Keep in mind the NVIDIA compatibility note, though. XanMod runs a companion NVIDIA driver repo, current branches sit at 595.104.02 and 615.78.08, and the project warns that recent DKMS modules can lag the newest kernel by a few weeks. If you're on an NVIDIA GPU with DKMS-built modules, verify before you reboot.
XanMod 7.2.10 and 6.18.56 are available now, both free and open-source. You can grab them from xanmod.org or the GitLab releases pages for the 7.2 and 6.18 branches, with changelogs posted alongside.
Is it for you? Probably not if your distro already ships a tuned kernel, since several major ones do. But if you're chasing responsiveness out of the box, squeezing older hardware for performance, or you just like building your own stack, XanMod keeps being the most polished option available. Its edge has never been any code it writes itself. It's everything it does to make the upstream kernel feel a little faster.
