Vulnerability Database · Alpine · Package report

linux-lts: vulnerability history, versions and safety

linux-lts is a package in the Alpine ecosystem. Vulert records 4 vulnerabilities for it across 96 releases, first recorded in Dec 2020. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded U4
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on linux-lts i

Updated on 22 Oct 2026

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 15 Dec 2020. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 4 vulnerabilities on record across 1 year, none in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

  • Vulnerabilities on record 4 over 1 year · 0 in the last year i
  • Latest disclosure 15 Dec 2020 i
  • Highest CVSS 8.8 i
  • With no published fix 0 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for linux-lts, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
5.10.3-r0 U4 Yes Details →
5.10.2-r0 U4 Yes Details →
5.10.1-r1 U4 Yes Details →
5.10.1-r0 U4 Yes Details →
5.10.0-r0 U4 Yes Details →
5.4.82-r0 U4 Yes Details →
5.4.81-r0 U4 Yes Details →
5.4.80-r0 U4 Yes Details →
5.4.79-r0 U4 Yes Details →
5.4.78-r0 U4 Yes Details →
5.4.77-r0 U4 Yes Details →
5.4.75-r0 U4 Yes Details →
5.4.74-r0 U4 Yes Details →
5.4.73-r0 U4 Yes Details →
5.4.72-r0 U4 Yes Details →
5.4.71-r0 U4 Yes Details →
5.4.70-r0 U4 Yes Details →
5.4.69-r0 U4 Yes Details →
5.4.68-r0 U4 Yes Details →
5.4.67-r0 U4 Yes Details →
5.4.66-r0 U4 Yes Details →
5.4.65-r0 U4 Yes Details →
5.4.64-r0 U4 Yes Details →
5.4.63-r0 U4 Yes Details →
5.4.62-r0 U4 Yes Details →
5.4.61-r1 U4 Yes Details →
5.4.61-r0 U4 Yes Details →
5.4.60-r0 U4 Yes Details →
5.4.59-r0 U4 Yes Details →
5.4.58-r0 U4 Yes Details →
5.4.57-r1 U4 Yes Details →
5.4.57-r0 U4 Yes Details →
5.4.55-r0 U4 Yes Details →
5.4.54-r2 U4 Yes Details →
5.4.54-r1 U4 Yes Details →
5.4.54-r0 U4 Yes Details →
5.4.53-r0 U4 Yes Details →
5.4.52-r0 U4 Yes Details →
5.4.51-r0 U4 Yes Details →
5.4.50-r0 U4 Yes Details →
5.4.49-r0 U4 Yes Details →
5.4.48-r0 U4 Yes Details →
5.4.47-r1 U4 Yes Details →
5.4.47-r0 U4 Yes Details →
5.4.46-r1 U4 Yes Details →
5.4.46-r0 U4 Yes Details →
5.4.45-r0 U4 Yes Details →
5.4.44-r0 U4 Yes Details →
5.4.43-r1 U4 Yes Details →
5.4.43-r0 U4 Yes Details →
5.4.42-r1 U4 Yes Details →
5.4.42-r0 U4 Yes Details →
5.4.41-r0 U4 Yes Details →
5.4.40-r0 U4 Yes Details →
5.4.39-r0 U4 Yes Details →
5.4.38-r0 U4 Yes Details →
5.4.36-r0 U4 Yes Details →
5.4.35-r0 U4 Yes Details →
5.4.34-r0 U4 Yes Details →
5.4.33-r0 U4 Yes Details →
5.4.32-r0 U4 Yes Details →
5.4.31-r0 U4 Yes Details →
5.4.30-r0 U4 Yes Details →
5.4.29-r0 U4 Yes Details →
5.4.28-r0 U4 Yes Details →
5.4.27-r0 U4 Yes Details →
5.4.26-r0 U4 Yes Details →
5.4.25-r0 U4 Yes Details →
5.4.24-r1 U4 Yes Details →
5.4.23-r1 U4 Yes Details →
5.4.23-r0 U4 Yes Details →
5.4.22-r0 U4 Yes Details →
5.4.21-r0 U4 Yes Details →
5.4.20-r1 U4 Yes Details →
5.4.20-r0 U4 Yes Details →
5.4.18-r0 U4 Yes Details →
5.4.17-r0 U4 Yes Details →
5.4.16-r0 U4 Yes Details →
5.4.14-r0 U4 Yes Details →
5.4.13-r1 U4 Yes Details →
5.4.12-r1 U4 Yes Details →
5.4.12-r0 U4 Yes Details →
5.4.11-r0 U4 Yes Details →
5.4.10-r0 U4 Yes Details →
5.4.8-r0 U4 Yes Details →
5.4.7-r0 U4 Yes Details →
5.4.6-r0 U4 Yes Details →
5.4.5-r0 U4 Yes Details →
5.4.4-r1 U4 Yes Details →
5.4.4-r0 U4 Yes Details →
5.4.3-r0 U4 Yes Details →
5.4.2-r0 U4 Yes Details →
5.4.1-r0 U4 Yes Details →
5.4.0-r3 U4 Yes Details →
5.4.0-r2 U4 Yes Details →
5.4.0-r1 U4 Yes Details →

Newest 96 of 96 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 4

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 4 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for linux-lts

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About linux-lts

Is linux-lts safe to use?

Vulert records 4 vulnerabilities for linux-lts in Alpine: 0 critical, 0 high, 0 medium and 0 low, plus 4 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

How many vulnerabilities does linux-lts have?

4 vulnerabilities are recorded for linux-lts in the Alpine ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 4 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new linux-lts vulnerabilities disclosed?

0 vulnerabilities were recorded for linux-lts in the last 12 months, and the oldest entry in this database dates to 15 Dec 2020. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of linux-lts are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor linux-lts for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the linux-lts version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.