Lineageos 22.2 · Version Status

Lineageos 22.2 End of Life Date

Lineageos 22.2 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.

Lineageos 22.2 is actively supported. EOL date: Already EOL.
EOL Date
Already EOL
Supported
Latest Release
Standard release
Release Date
Apr 11, 2025
Lineageos 22.2 series
← Lineageos 22.1 All Lineageos versions Lineageos 23.0 →
All Lineageos Versions
VersionLatestEOL DateStatus
13.0 Supported Active
14.1 Supported Active
15.1 Supported Active
16.0 Feb 16, 2021 EOL
17.1 Apr 26, 2022 EOL
18.1 Mar 5, 2024 EOL
19 Feb 14, 2024 EOL
20 Supported Active

What does Lineageos 22.2 end of life mean?

When Lineageos 22.2 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.

The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running Lineageos 22.2 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.

Migrate to Lineageos 23.2 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.

Frequently Asked Questions
When does Lineageos 22.2 reach end of life?
Lineageos 22.2 has already reached end of life.
Is Lineageos 22.2 still supported?
Yes, Lineageos 22.2 is currently supported. The EOL date is Already EOL.
What should I upgrade to from Lineageos 22.2?
The recommended upgrade from Lineageos 22.2 is Lineageos 23.2 — the latest actively supported version. Check the Lineageos full timeline for all supported versions.
What are the security risks of running Lineageos 22.2 past EOL?
When Lineageos 22.2 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL Lineageos should migrate immediately or implement compensating controls.
Data from endoflife.date API · Generated at build time · How we source data →