MX Linux, the lightweight and stability-focused Debian-based distribution, has released MX-25.3, the latest update in its MX-25 “Infinity” series, refreshing its installation images with the latest Debian and MX updates.
The new release includes all updates from Debian 13.7 and everything published through the MX repositories since the previous official ISO release.
Most MX-25.3 editions now ship with the Linux kernel 6.12. The exception is the Xfce AHS edition, aimed primarily at newer hardware, which comes with the Liquorix Linux kernel 7.2.
The AHS-enabled images also receive a notable graphics stack update, moving to Mesa 26.1 and adding newer firmware packages backported from Debian Sid.
MX Linux’s own utilities have received attention as well. MX Welcome, MX Tools, and the custom-toolbox used by the Fluxbox edition now feature refreshed user interfaces.
Another addition is Verify ISO Sig, a new utility to verify digital signatures of ISO images. Although introduced as part of MX Linux, the tool is not limited to MX images and can verify ISOs from several other popular Linux distribution families.
MX-Theme-Colors is another new utility, allowing users to create custom GTK highlight color variations based on existing MX themes.
The MX Package Installer has also been updated. Its Popular Apps section now offers Siduction 7.x kernels, and several third-party VPN installation options have been updated.
It’s worth noting also that for new installations, the MX/Gazelle installer now enables the lazytime mount option in /etc/fstab by default.
Existing MX Linux users do not need to reinstall the operating system to receive these changes. The same updates are distributed through the regular package update channels, with the new ISOs primarily serving fresh installations.
MX-25.3 is available in Xfce, KDE Plasma, and Fluxbox editions, alongside an Xfce AHS image for newer hardware.
Finally, the project has also released an updated MX-25.3 Raspberry Pi respin. However, automatic filesystem expansion on first boot has currently been removed because the previously used methods have become unreliable. Raspberry Pi users are instead advised to resize the filesystem manually using raspi-config after the first boot.
For additional details, see the announcement.
