XanMod hits all three of its major branches at once with coordinated kernel updates
The EDGE, MAIN and LTS kernels all went live on 30 October, carrying a heavy batch of io_uring fixes plus an unexpected amateur-radio security sweep.
XanMod has now shipped three coordinated kernel updates in a single day. The EDGE, MAIN and LTS branches all went live on 30 October 2026, each on a different upstream tree, so the project covered much of the present and near-future of x86-64 Linux in one shot.
That's a bit unusual for a project run mostly by one person. Alexandre Frade has maintained XanMod since 2015 and does so largely solo. Yet he tracks the rolling EDGE branch, the previous stable line and the long-term-support tree at the same time. All three landed on the same calendar day here, which says something about the automation behind the build pipeline: source pulls, patch application, LLVM compilation and .deb packaging all fired cleanly for three distinct kernel trees within minutes of each other.
What changed across the releases
The headline theme running through all three builds is io_uring. This is the high-performance I/O subsystem underpinning a lot of modern database, web and container workloads, and it has been getting an unusually heavy dose of concurrency fixes this cycle.
On MAIN (7.2.14), io_uring and io-wq make up 54 of the 91 tracked commits. That's the overwhelming majority, and it lines up with what upstream stable was doing. The fixes target subtle race conditions and reference-counting bugs that can otherwise cause hangs or lost wakeups under heavy concurrent I/O. Several of them sound like they were written against real-world breakage: "don't lose a cancel," "don't strand work when a worker exits," "disable preemption while pushing."
The LTS branch (6.18.60) is the biggest at 115 commits, and its io_uring batch, 48 of them, mirrors MAIN. But the part of the changelog worth your attention is the rest.
The amateur-radio detour
6.18.60 also carries an extensive overhaul of AX.25, NET/ROM and ROSE. These make up Linux's amateur-radio network stack: legacy protocols that most users will never touch, but that are still present and still reachable over the wire. This pass mixes memory-safety fixes, including an integer overflow in ax25_rx_fragment() and an out-of-bounds read after address-header stripping in ax25_rcv(), with reference-count and leak fixes, and it now requires full NET/ROM headers before accepting frames.
That's the kind of change you wouldn't spot unless you were actually reading a kernel changelog, which is rare enough on its own. OOB-read and integer-overflow fixes in a protocol this obscure still have direct security relevance.
If you're keeping score, the EDGE branch (7.3.1) is the smallest of the three, which is expected since 7.3.1 is a very recent point release. Its 42 tracked commits break down into the usual cross-branch hardening: a keyring and trusted-key set that shows up in all three releases, plus signal and process-lifecycle fixes and a small pile of Bluetooth, tracing and misc patches.
The kernels underneath
It helps to know what sits under these builds. Linus Torvalds released Linux 7.3 on 18 October 2026, and the community's counting made it a record-breaker: 18,765 non-merge commits from 3,021 developers, 807 of them first-timers. XanMod's EDGE build is the first to carry that mainline into tuned .deb form.
7.2 is now in steady stable maintenance, so by the time of 7.2.14 it's doing bugfixes rather than shipping new features. Cache-aware task scheduling and a fairer GPU scheduler arrived back in the 7.2 cycle, for instance.
6.18 is this year's LTS. It shipped on 30 November 2025 and was promoted to long-term support with coverage projected through December 2027, possibly extended to December 2028. It brought a Rust Binder driver, the Tyr Rust DRM driver for Arm Mali GPUs, and a device-mapper cache target using persistent memory. XanMod's LTS build is the one most relevant to servers and production systems, which is why that AX.25 security sweep deserves a reader's eye.
Which build and how to install
XanMod ships for 64-bit Debian-based distributions. The standard install pulls the PGP key, adds a repo using your distro's codename, then installs the kernel. Frade has described the goal as aligning "the best performance of Linux with the desktop experience," and the builds reflect that aim: LLVM-based compilation with software pipelining, BBRv3 built in as tcp_bbr by default, Cloudflare's TCP collapse, a 500Hz tickless scheduler, and Google's multigenerational LRU as the default page-replacement scheme.
You'll need to pick the right x86-64 ABI level, and this matters more than it arguably should. Install the wrong one and you can end up with an unbootable system. v2 targets roughly 2009-and-newer CPUs, v3 covers 2015 and newer machines. There's also a v4 (AVX-512) build, but XanMod doesn't recommend it — there's no kernel benefit to justify it. The branches map to package names as linux-xanmod (MAIN), linux-xanmod-edge (EDGE), linux-xanmod-lts (LTS) and linux-xanmod-rt (RT).
A check script lives at dl.xanmod.org/check_x86-64_psabi.sh if you want to verify before installing.
One caveat worth flagging: XanMod itself notes that the current NVIDIA, OpenZFS, VirtualBox and VMware modules may not yet support the latest kernels. If you run proprietary out-of-tree modules, check compatibility before you reboot. It's the usual trade-off for running a third-party kernel, and the same caveat applies to siblings like Liquorix.
Head here to the XanMod website for more information.
