EOL.Wiki EOL.Wiki
← ← Back to all products

MX Linux

Active
Operating Systems Latest Version: 25.1 Latest Release: Jan 19, 2026

MX Linux is a cooperative project between antiX and MX Linux communities, based on Debian Stable.

Versions

9

Latest Version

25.1

Active Support

2

EOL

6

Lifecycle Timeline

Today
25
25
23
23
21
21
19
19
18
18
17
17
16
16
15
15
14
14
Active SupportSecurity SupportEOL

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
25Nov 9, 2025Aug 31, 2028Jun 30, 203025.1No
Active
23Jul 31, 2023Jun 10, 2026Jun 10, 202823.6No
Active
21Oct 21, 2021Jun 30, 2024Jun 30, 202621.3No
Security
19Oct 22, 2019Sep 10, 2022Jun 30, 202419.4No
EOL
18Dec 20, 2018Jun 5, 2020Jun 30, 202218.3No
EOL
17Dec 15, 2017Jun 5, 2020Jun 30, 202217.1No
EOL
16Dec 14, 2016Jun 23, 2018Jun 30, 202016.1No
EOL
15Dec 24, 2015Jun 23, 2018Jun 30, 202015No
EOL
14Mar 25, 2014Jun 4, 2016May 31, 201814.4No
EOL

Frequently Asked Questions

Which versions of MX Linux have reached end of life?
The following MX Linux versions have reached end of life and no longer receive security updates: 19, 18, 17, 16, 15, 14. It is recommended to upgrade to a supported version.
Is it safe to continue using MX Linux 19?
MX Linux 19 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of MX Linux?
The latest version of MX Linux is 25.1, released in the 25 release cycle.
How many versions of MX Linux are currently supported?
MX Linux currently has 3 actively supported version(s): 25, 23, 21.
When does MX Linux 25 reach end of life?
MX Linux 25 is scheduled to reach end of life on Jun 30, 2030.
What should I do when MX Linux reaches end of life?
When a MX Linux version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.