SLES 15.5 End of Life: Last-Call Action Plan (Dec 31, 2024)

Introduction

SUSE Linux Enterprise Server (SLES) 15.5 reaches its end of life on December 31, 2024. That is roughly three months away. This is not an LTS release, so after that date, SUSE will no longer provide patches, bug fixes, or vendor support. If you are running SLES 15.5 in production, you need a plan—not for a full migration (that is no longer realistic for most estates), but for risk management and operational continuity.

What changes on December 31, 2024?

On the end-of-life date, the following stops:

• No new security patches or hotfixes from SUSE.
• No technical support from SUSE (paid or otherwise).
• No access to SUSE’s update repositories for 15.5.

Existing patches already on your systems will remain, but any new vulnerability discovered after that date will have no official fix. Your compliance and insurance exposure increases immediately.

Why full migration is no longer realistic

A migration to a newer SLES version (e.g., 15.6 or 15.7) involves testing application compatibility, validating drivers, staging environments, and cutting over. For enterprises with dozens or hundreds of SLES 15.5 instances, completing that process by December 31, 2024 is simply not feasible. Panic-driven migrations cause more downtime and risk than staying put with a support safety net.

Your week-by-week action plan

Here is a concrete checklist to complete before the EOL date. Start now—do not wait until November.

Week 1-2: Inventory and classify

• Run a discovery tool or script to identify all SLES 15.5 instances (physical, virtual, cloud).
• Record hostname, IP, role, criticality (tier 1/2/3), and compliance requirements.
• Identify which have internet-facing services or process sensitive data.

Week 3-4: Harden and isolate

• Apply all pending SUSE patches now. After EOL you cannot.
• Remove unnecessary services, open ports, and user accounts.
• Move critical systems behind a firewall or VPN if possible.
• Enable enhanced logging (auditd, syslog forwarding) to detect exploitation attempts.

Week 5-6: Document exposure and update auditors/insurers

• Create a risk register listing each SLES 15.5 system, its EOL status, and any compensating controls.
• Notify your internal audit and security teams formally.
• Check with your cyber insurance provider: some policies require patching or vendor support for covered systems.

Week 7-8: Secure third-party support

• Evaluate a third-party support provider that can deliver security patches and technical support for SLES 15.5 after December 31, 2024.
• Ensure the contract covers the same SLAs your vendor support did.
• Confirm the provider can backport critical CVEs for your kernel and libraries.

Week 9-10: Testing and fallback

• Test the third-party support patching process on a non-production instance.
• Verify that monitoring and alerting still work with the new support channel.
• Create a rollback plan in case of unexpected issues.

Week 11-12: Final pre-EOL checks

• Confirm all systems are inventoried and hardened.
• Verify documentation is complete and shared with relevant teams.
• Set a calendar reminder for the EOL date to officially switch to the third-party support contract.

The role of third-party support

Third-party maintenance providers can extend the life of SLES 15.5 beyond the vendor’s EOL. They offer security patches, bug fixes, and technical support—often at lower cost than a new SUSE subscription. This is not a permanent solution, but it buys you time to plan a methodical migration to a newer release (or a different distribution) without the pressure of a December 31 deadline. For more details on how third-party support works for outdated enterprise Linux, contact us.

Conclusion

SLES 15.5 end of life is a hard deadline. You cannot stop it, but you can control how you respond. Act now: inventory your systems, harden them, document the risk, and secure a support bridge. With a week-by-week plan in hand, you can navigate the next three months without panic—and keep your infrastructure running safely into 2025.