Ubuntu 25.04 'Plucky Puffin'
Ubuntu 25.04 'Plucky Puffin'
The Ubuntu 25.04 'Plucky Puffin' reached end of service life on Jan 17, 2026 — Ubuntu no longer ships security patches or fixes for it. Our third-party support keeps it safe to run: 24/7 engineers manage issues, remediate vulnerabilities, and help you maintain compliance.
24/7 engineers own your Ubuntu 25.04 'Plucky Puffin' incidents end to end.
Mitigation and patch-around guidance when the vendor no longer ships fixes.
Controls evidence and documentation that keep auditors satisfied.
Specifications
- product
- ubuntu
- release
- 25.04
- product Label
- Ubuntu
- release Label
- 25.04 'Plucky Puffin'
- codename
- Plucky Puffin
- lts
- latest Version
- 25.04
- release Date
- 2025-04-17
- maintained
- source Url
- https://endoflife.date/ubuntu
Lifecycle Dates
- End of Service Life
- Jan 17, 2026
- Last OEM Support
- Jan 17, 2026
OEM vs. 3rd Party Support
See how third-party support compares to the vendor contract for Ubuntu 25.04 'Plucky Puffin' — monitoring, break/fix, vulnerability work, operations and compliance, before and after EOSL.
| Feature | OEM Support | 3rd Party Support |
|---|---|---|
| Post-EOSL Support | ||
| Break/Fix Support | Until EOSL | |
| 24/7 Monitoring | ||
| Vulnerability Scanning & Remediation | ||
| Managed Operations | ||
| Procedure & Configuration Review | ||
| Compliance & Audit Documentation | Limited | |
| Discounted Migration to Other Platforms |
Why Choose 3rd Party Support for Ubuntu 25.04 'Plucky Puffin'?
Vulnerability Remediation
Scanning, mitigation and patch-around guidance for Ubuntu 25.04 'Plucky Puffin' when the vendor no longer ships fixes.
Compliance Maintenance
Procedure review, controls evidence and the documentation auditors ask for — maintained continuously, not scrambled at audit time.
24/7 Expert Support
Engineers who know this release monitor, manage and fix issues around the clock — break/fix to managed operations.
Ubuntu 25.04 'Plucky Puffin' Support: Frequently Asked Questions
Is the Ubuntu 25.04 'Plucky Puffin' still supported?
Ubuntu ended support for the Ubuntu 25.04 'Plucky Puffin' on Jan 17, 2026 — no more patches or fixes from the vendor. Third-party support keeps it covered: our engineers manage issues, remediate vulnerabilities, and help you maintain compliance for as long as you run it.
When is the Ubuntu 25.04 'Plucky Puffin' end of service life (EOSL) date?
Ubuntu lists the end of service life for the Ubuntu 25.04 'Plucky Puffin' as Jan 17, 2026.
Can I keep using the Ubuntu 25.04 'Plucky Puffin' after its EOSL date?
Yes. EOSL means Ubuntu stops issuing patches and support — the software itself keeps running. Third-party support covers it from there: issue management, security vulnerability remediation, and the compliance documentation auditors ask for, for as long as you choose to run it.
How much does third-party support for the Ubuntu 25.04 'Plucky Puffin' cost?
Typically 40-70% below the OEM maintenance renewal price. Exact pricing depends on quantity, service level and location — request a quote and we respond within 24 hours.
Known Vulnerabilities Affecting Ubuntu 25.04 'Plucky Puffin'
3 published CVEs affect the Ubuntu 25.04 'Plucky Puffin', including 2 rated critical or high severity. Ubuntu no longer ships security patches for this release — our engineers provide mitigation guidance, workarounds and hardening support.
| CVE | Severity | CVSS | Published | Summary |
|---|---|---|---|---|
| CVE-2025-32463 | CRITICAL | 9.3 | Jun 30, 2025 | Sudo before 1.9.17p1 allows local users to obtain root access because /etc/nsswitch.conf from a user-controlled directory is used with the --chroot option. |
| CVE-2026-31431 | HIGH | 7.8 | Apr 22, 2026 | In the Linux kernel, the following vulnerability has been resolved: crypto: algif_aead - Revert to operating out-of-place This mostly reverts commit 72548b093ee3 except for the copying of the associated data. There is no benefit in operating in-place in algif_aead since the source and destination come from different mappings. Get rid of all the complexity added for in-place operation and just copy the AD directly. |
| CVE-2025-5054 | MEDIUM | 4.7 | May 30, 2025 | Race condition in Canonical apport up to and including 2.32.0 allows a local attacker to leak sensitive information via PID-reuse by leveraging namespaces. When handling a crash, the function `_check_global_pid_and_forward`, which detects if the crashing process resided in a container, was being called before `consistency_checks`, which attempts to detect if the crashing process had been replaced. Because of this, if a process crashed and was quickly replaced with a containerized one, apport |