SLES 15.6 End of Life: December 31, 2025

SUSE Linux Enterprise Server 15.6 Has Reached End of Life

If you are still running SUSE Linux Enterprise Server (SLES) 15.6, you are now in unsupported territory. As of December 31, 2025, this release is fully end of life (EOL) — both active support and security patching have ceased. This is not a long-term support (LTS) release, so there is no extended lifecycle cushion.

This article is written as an evergreen reference for anyone who finds themselves still on SLES 15.6 — whether you inherited the infrastructure, are locked by an application dependency, or simply missed the migration window.

What End of Life Really Means for SLES 15.6

When a SUSE Linux Enterprise Server version reaches EOL, several things happen on the vendor side:

• No new security patches. Critical CVEs that affect SLES 15.6 will not be addressed by SUSE. Your systems are vulnerable to any newly discovered exploits.
• No bug fixes. Kernel or package-level defects — even those causing downtime — will not be patched.
• No vendor technical support. SUSE will not take support tickets for 15.6 issues. If a problem occurs, you are on your own.
• No updates to installation media. You cannot deploy new SLES 15.6 instances from official channels.

What still works: all existing services, applications, and configurations will continue to run as before — until something breaks or a security issue is exploited.

The Real Risks of Running SLES 15.6 Unsupported

Running an unsupported operating system is not necessarily an immediate crisis, but it introduces cumulative risk:

• Security exposure. Without patches, every CVE that affects SLES 15.6 becomes a permanent unpatched gap. Compliance frameworks (PCI DSS, SOC 2, HIPAA) explicitly require patched systems.
• No kernel live patching. If you relied on SUSE's live patching service, it no longer functions for 15.6 kernels.
• Software rot. Third-party software vendors may drop SLES 15.6 support, making new installations or updates impossible.
• Audit failures. External auditors will flag any EOL system as a finding.
• No vendor escalation paths. If a bug takes down a critical application, you have no one to call.

Who Still Needs SLES 15.6?

Despite the risks, some organizations cannot simply upgrade:

• Stable production workloads that have run without issues for years and where change introduces more risk than staying put.
• Application-locked environments where the software vendor requires a specific OS version — and has not certified a newer one.
• Hardware constraints where the underlying infrastructure does not support SLES 15.7 or later (e.g., older IBM Power or Z systems, specialized appliances).
• Compliance-driven freezes where a full revalidation cycle for a new OS version would delay other priorities.

For these teams, upgrading is not a simple click — it is a multi-month project that may not be immediately possible.

Your Options After SLES 15.6 EOL

Option 1: Upgrade to a supported SLES release

If your hardware and applications are compatible, migrating to a currently supported version (such as SUSE Linux Enterprise Server 15.7 or later) is the best long-term path. This restores security patches, vendor support, and ecosystem compatibility.

Option 2: Third-Party Support for SLES 15.6

If you cannot upgrade immediately — or at all — third-party support keeps SLES 15.6 maintained and compliant:

• Continued security patches. Backported fixes for critical and high-severity CVEs.
• 24/7 technical support from engineers who know SLES inside out.
• No forced migration. You stay on your current, stable OS version for as long as you need.
• Cost savings. Typically a fraction of your last SUSE renewal — often 50% or more.

This is not a stopgap. Many IT organizations use third-party support as a permanent strategy for workloads that are stable but not worth the risk of going unpatchable.

Option 3: Run it unsupported

You can choose to accept the risk. This works for isolated, air-gapped systems or test/dev environments not handling sensitive data. For production systems connected to any network, this is not recommended.

How Third-Party Support Works

Third-party support providers do not fork the operating system. They:

• Monitor the same CVE lists and code repositories as SUSE.
• Develop, test, and deploy custom patches for your exact SLES 15.6 packages.
• Provide phone and email support with SLA-backed response times.
• Leave your chosen OS version untouched — no upgrade required.

For many IT leaders, this is the practical path: continued security coverage without the disruption of an OS migration.

Making the Decision

The best time to plan for SLES 15.6 EOL was before December 31, 2025. The next best time is now — because every day without patching increases risk.

Evaluate your specific constraints:

• Can your hardware run SLES 15.7+?
• Are your applications certified on a newer OS version?
• Would an OS upgrade require revalidation of your compliance posture?
• How much downtime can you afford for a migration?

If immediate upgrade is out of reach, contact us to discuss how third-party support can keep your SLES 15.6 systems patched, supported, and running safely — without the pressure of a forced migration.