Ubuntu 24.10 EOL Action Plan: Prepare for July 10, 2025

The Deadline: Ubuntu 24.10 'Oracular Oriole' EOL on July 10, 2025

On July 10, 2025, Canonical will end all support for Ubuntu 24.10 'Oracular Oriole'. After that date, there will be:

• No more security patches
• No bug fixes
• No vendor SLAs or support tickets
• No new package updates from the main repositories

With only about three months remaining, a full migration to an LTS release (such as 24.04 LTS or an interim upgrade to 25.04 once available) is still possible, but it is becoming tight for large estates. If migration is not feasible before July 10, this article lays out a realistic last-call action plan: inventory, isolate, document, and contract for extended support.

---

What Changes on July 10, 2025?

After EOL, your 24.10 systems will still boot and run existing software, but they will become increasingly vulnerable:

• Canonical will stop releasing security patches for the kernel, system libraries, and all packages in the main repository.
• Newly discovered CVEs will not be addressed by Canonical.
• The apt update command will eventually fail as repositories are moved to old-releases.ubuntu.com.
• Compliance tools (PCI-DSS, SOC2, HIPAA) will flag unsupported operating systems.

Without a support provider that continues to deliver patches independently, your exposure grows with every new vulnerability disclosed after July 10.

---

The 12-Week Action Checklist

Take one task per week, starting immediately.

Week 1-2: Inventory All 24.10 Instances

• Run lsb_release -a or hostnamectl across your estate.
• Identify which hosts are still on 24.10 and not already on 24.04 LTS or later.
• Distinguish between:
  • Critical production (customer-facing, PCI-scoped, HA clusters)
  • Non-critical (dev, test, staging, internal tools)
  • Orphaned (VMs or containers with no clear owner)

Week 3: Risk Classification & Isolation

• For critical systems that cannot be migrated in time: plan to isolate them.
• Move these instances behind network segments with strict ingress/egress rules.
• Remove them from public-facing load balancers if possible.
• Disable unnecessary services, especially internet-facing SSH.
• Document the isolation strategy per host.

Week 4-5: Attempt Default Migration Paths

• For systems still feasible to upgrade:
  • do-release-upgrade from 24.10 to 25.04 (released April 2025) is the standard path, but note that non-LTS-to-LTS direct upgrades are not supported by Canonical.
  • If 25.04 is not yet available or stable enough, consider a clean install of 24.04 LTS.
• Migrate data and configurations. Do not attempt risky in-place upgrades on production EOL dates.

Week 6: Harden Remaining 24.10 Systems

• Apply all remaining available patches from Canonical before July 10.
• Enable unattended-upgrades to catch any last-minute fixes.
• Lock down user accounts, enforce 2FA, and audit sudoers files.

Week 7-8: Document Risk & Exposures

• Create a formal EOL risk register for your auditors and cyber insurance provider.
• For each 24.10 instance, document:
  • Business justifications for delaying migration
  • Mitigation measures (isolation, network controls, compensating controls)
  • Target migration date
  • Who is accountable
• This documentation will be critical if you are ever asked why EOL systems remain in production.

Week 9-10: Evaluate Third-Party Support Options

• Since Canonical will not provide patches after July 10, a third-party maintenance provider can step in to deliver ongoing security fixes, tech support, and compliance reporting.
• This is not an extension of Canonical’s free updates – it is a commercial contract that covers the exact same software stack.
• Compare SLAs, CVE response times, and whether they support your specific architecture (x86, ARM, etc.).

Week 11-12: Secure Day-One Support

• Sign a support contract with a third-party provider before July 10.
• Confirm that the provider will begin patching on July 11, not weeks later.
• Test their patch repository on a non-production 24.10 instance to ensure compatibility.

---

Why Third-Party Support Makes Sense Now

If migration is impossible before July 10, third-party support is the only way to keep Ubuntu 24.10 compliant and secure. A provider like 3rd Party Support can:

• Deliver independent patches for CVEs in the kernel, OpenSSL, glibc, and other critical packages.
• Provide SLAs for severity levels (e.g., critical patches within 24 hours).
• Offer compliance documentation (SBOMs, patch logs) to satisfy auditors.
• Cover both security and functional bug fixes that Canonical will stop issuing.

Because 24.10 is not an LTS, Canonical’s stance is firmly “upgrade or accept risk.” Third-party support fills the gap without requiring an immediate migration.

---

The Bottom Line

You still have three months. Use them wisely: inventory now, isolate what you cannot move, document everything for auditors, and line up a support contract before day one of EOL. Contact us to discuss a support plan for Ubuntu 24.10 'Oracular Oriole' that starts on July 10, 2025.

Lifecycle data sourced from endoflife.date/ubuntu.