XanMod Ships 7.2.8 and 6.18.54 Kernels for Desktop and Workstation AMD64
Fresh point releases for both the mainline and LTS branches arrived on September 25, 2026.
XanMod just shipped two new kernel builds at once, and they track this week's upstream releases to the letter. As of September 25, you can grab 7.2.8-xanmod1 and 6.18.54-xanmod1, each mirroring Greg Kroah-Hartman's own stable and longterm point releases of Linux 7.2.8 and 6.18.54. Both land on the same day, so whether you're chasing features or stability there's a matching build ready to go.
For those not deep in the kernel weeds, XanMod is a repackaging and enhancement layer over the vanilla Linux kernel, maintained by Alexandre Frade since 2015. It pulls the upstream trees from kernel.org, then rebuilds them for 64-bit Debian- and Ubuntu-based systems with an added patchset of build-time optimizations, scheduler tuning, networking hardening, and driver fixes. The project describes its own goal as providing "a stable, smooth and solid system experience" with custom settings and new features bolted on.
The XanMod project has been quietly building kernels for over a decade. Frade started the effort in 2015, and it's still largely maintained by the same developer today. For millions who compile or install third-party kernels, XanMod sits neatly between stock distro kernels, which favor conservative and heavily tested configs, and from-scratch custom builds that demand real expertise. It's the middle path: the latest kernel code, precompiled and pre-tuned, installable with a single apt install. That's the whole appeal.
Two builds, and what the changelog tells us
The dual release reflects two distinct audiences. The 7.2 branch caters to enthusiasts and developers who want the newest scheduler tricks, filesystem work, and memory-management improvements as they arrive in vanilla mainline. The 6.18 LTS branch serves production servers, enterprise workstations, and anyone who values long-term stability over the newest features. Both branches carry XanMod's signature optimizations, so the real question is "newest" versus "most stable," not which tuning philosophy wins.
Linux 7.2 landed in mainline as the newest feature series, keeping up the short-cycle pace Linus Torvalds set and Greg Kroah-Hartman point-maintains. Per Kernel Newbies and Phoronix, the standout of the cycle was cache-aware task scheduling. The scheduler gained load-balancing logic that groups related threads, such as all the threads from a single process, inside the same Last Level Cache domain, cutting cache bouncing and misses down. Other 7.x highlights include a fairer DRM GPU scheduler, a cleanup of memory-reclaim work around Google's multigenerational LRU, a "Phase IV" rework of the swap table, btrfs folio work, and a new device-mapper inline-encryption target.
Linux 6.18 was declared a long-term-support release at the end of November 2025 and has been under extended maintenance since, so it's the natural fit for anything that needs to run reliably for years. The cycle brought a Rust port of Android's Binder IPC driver, a new dm-pcache device-mapper target that uses persistent memory as a cache, improved swapping and slab allocation, AccECN and PSP encryption for TCP, BPF-signed-program support, and a new microcode= command-line option for the x86 microcode loader.
Read through both XanMod releases and the dominant theme is clear. This is a stable-point release, so security and correctness hardening dominates. The biggest cluster of fixes lands on the SMB/CIFS network file-share client. A run of patches by Frank Sorenson and Paulo Alcantara, both at Red Hat, closed out-of-bounds reads, use-after-frees, integer overflows, and bounds-checking gaps. They patch how the kernel parses replies from untrusted SMB servers, which is exactly the surface that remote exploits have targeted for years. The fixes range from a missing iov bounds check in parse_posix_sids() that rejects past-the-end buffer replies, to a closed OOB read in smb3_enum_snapshots() that stops adjacent slab memory leaking to userspace, to a next_buffer use-after-free and bounds issue on compound PDUs, plus a missing lower-bound check on DFS referral offsets. A parallel sweep hardened the Wi-Fi stack across mac80211, cfg80211, mwifiex, wilc1000, and brcmsmac.
The xfrm/IPsec subsystem also got attention, with fixes that save input state before secpath resets to avoid dereferencing freed memory and one that stashes the original device reference to clear a refcount imbalance that previously produced unregister_netdevice: waiting for ... to become free errors. There's also a lock refactor on xfrm_input that, per the commit message, delivers large throughput gains on multi-queue IPsec offload, with reported improvements of 50% or more when using 6 to 16 RX queues on mlx5 hardware.
Storage and drivers got their share too. XFS now fixes an under-reservation of blocks during sf directory repair, correcting a transaction space-miscalculation that could force a filesystem shutdown during xfs_repair. btrfs picked up fixes for chunk validation, hole-punching and refling transaction aborts, and free-space-tree rebuild failures. AMDGPU and AMDKFD handling gained a runtime PM reference for peer-to-peer dma-buf attachments, resolving "Move buffer fallback to memcpy unavailable" errors on dual-GPU systems, while restore_mqd callbacks for GFX12/12.1 bring CRIU checkpoint and restore back. Smaller drivers like Intel's MSM, Xe, VC4, and Gud took use-after-free and runtime-PM cleanups.
The 6.18.54 LTS build shares most of 7.2.8's fixes since both are backporting the same upstream stable work. What sets it apart: a revert of a ksmbd fix that depended on SMB1 header refactoring absent from the 6.18.y tree (applying it had broken Windows negotiate responses), XFS work specific to the backport that retains the 64-bit i_ino field, and a couple of Bluetooth HFP refactor backports plus an ASoC: intel: sof_sdw change. Everything else carries over, making clear that LTS users get essentially the same security posture as mainline users on a more conservative base kernel.
How to grab them
XanMod distributes its kernels through an official APT repository for Debian/Ubuntu-based systems. The supported codenames run through bookworm, trixie, forky, sid, noble, plucky, questing, resolute, stonking, faye, gigi, wilma, xia, zara, and zena. If you're keeping score, that's a lot of codenames to track.
The install routine is the usual three-step dance. Register the PGP key.
wget -qO - https://dl.xanmod.org/archive.key | sudo gpg --dearmor -vo /etc/apt/keyrings/xanmod-archive-keyring.gpg
Add the repository.
echo "deb [signed-by=/etc/apt/keyrings/xanmod-archive-keyring.gpg] http://deb.xanmod.org $(lsb_release -sc) main" | sudo tee /etc/apt/sources.list.d/xanmod-release.list
Then update and install your branch of choice.
sudo apt update && sudo apt install linux-xanmod-x64v3 # Main (7.2) sudo apt install linux-xanmod-lts-x64v3 # LTS (6.18) sudo apt install linux-xanmod-rt-x64v3 # Real-time (6.18-rt)
A final reboot finishes it up. For those who'd rather not touch the repo, prebuilt .deb packages sit on SourceForge, installable via dpkg -i.
One thing worth flagging before you do any of this: you need to pick the right CPU level. XanMod ships kernels at different x86-64 psABI levels, and the wrong pick just won't run. The legacy x86-64 build targets circa 2003-era silicon like Pentium 4 and Core 2. x86-64-v2 covers roughly 2009 onward, from Nehalem to modern Intel and Bulldozer-era AMD. x86-64-v3, around 2015, reaches Haswell and newer plus AMD Zen. There's a v4 for AVX-512, but the kernel gains nothing from it, so it exists purely for completeness. The main branch offers x64v2 and x64v3, while the LTS branch adds a wider spread including x64v1. Run the check script at dl.xanmod.org before installing to be sure you're not wasting a boot.
Keep in mind that XanMod also runs an NVIDIA driver repo, with a Production Branch at 595.104.02 and a New Feature Branch at 615.71.09. Some DKMS modules for NVIDIA, OpenZFS, VirtualBox, and VMware don't always support the newest kernels yet, so GPU users should verify compatibility before upgrading.
The 7.2.8-xanmod1 and 6.18.54-xanmod1 builds are textbook examples of why custom kernels hang around. They deliver upstream's latest security fixes, especially the aggressive SMB client hardening and the Wi-Fi and IPsec corrections, already compiled and tuned, with XanMod's scheduler, memory, and networking optimizations layered on top. Chase the newest features and the 7.2 mainline branch is yours. Running servers or a stability-focused desktop? The 6.18 LTS branch keeps the same security posture over a much longer horizon. Either way, both share the same core promise: a faster, more responsive stock kernel, ready to boot with a single command.
Head here to the XanMod site for the full release listings and installation guide.
