Vulnerability Database · Debian · Package report

linux: vulnerability history, versions and safety

linux is a package in the Debian ecosystem. Vulert records 32 vulnerabilities for it across 72 releases, from May 2013 to Jun 2018. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
32 vulnerabilities recorded U32
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 i

Updated on 22 Oct 2026

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

Long-term outlook: usable, with an upgrade 32 vulnerabilities on record across 5 years, 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 32 over 5 years · 0 in the last year i
  • Latest disclosure 01 Jun 2018 i
  • Highest CVSS n/a 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, 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
3.2.101-1 U1 Yes Details →
3.2.96-3 U2 Yes Details →
3.2.96-2 U3 Yes Details →
3.2.96-1 U3 Yes Details →
3.2.93-1 U4 Yes Details →
3.2.89-2 U5 Yes Details →
3.2.89-1 U5 Yes Details →
3.2.88-1 U6 Yes Details →
3.2.86-1 U7 Yes Details →
3.2.84-2 U8 Yes Details →
3.2.84-1 U9 Yes Details →
3.2.82-1 U10 Yes Details →
3.2.81-2 U11 Yes Details →
3.2.81-1 U12 Yes Details →
3.2.78-1 U13 Yes Details →
3.2.73-2 U16 Yes Details →
3.2.73-2+deb7u3 U13 Yes Details →
3.2.73-2+deb7u2 U14 Yes Details →
3.2.73-2+deb7u2~bpo60+1 U15 Yes Details →
3.2.73-2+deb7u1 U15 Yes Details →
3.2.73-1 U16 Yes Details →
3.2.71-2 U16 Yes Details →
3.2.71-1 U16 Yes Details →
3.2.68-1 U22 Yes Details →
3.2.68-1+deb7u6 U16 Yes Details →
3.2.68-1+deb7u6~bpo60+1 U17 Yes Details →
3.2.68-1+deb7u5 U17 Yes Details →
3.2.68-1+deb7u4 U18 Yes Details →
3.2.68-1+deb7u4~bpo60+1 U19 Yes Details →
3.2.68-1+deb7u3 U19 Yes Details →
3.2.68-1+deb7u3~bpo60+1 U20 Yes Details →
3.2.68-1+deb7u2 U20 Yes Details →
3.2.68-1+deb7u2~bpo60+1 U21 Yes Details →
3.2.68-1+deb7u1 U21 Yes Details →
3.2.68-1+deb7u1~bpo60+1 U22 Yes Details →
3.2.65-1 U24 Yes Details →
3.2.65-1+deb7u2 U22 Yes Details →
3.2.65-1+deb7u2~bpo60+1 U23 Yes Details →
3.2.65-1+deb7u1 U23 Yes Details →
3.2.65-1+deb7u1~bpo60+1 U24 Yes Details →
3.2.63-2 U26 Yes Details →
3.2.63-2+deb7u2 U24 Yes Details →
3.2.63-2+deb7u2~bpo60+1 U25 Yes Details →
3.2.63-2+deb7u1 U25 Yes Details →
3.2.63-2+deb7u1~bpo60+1 U26 Yes Details →
3.2.63-1 U26 Yes Details →
3.2.60-1 U28 Yes Details →
3.2.60-1+deb7u3 U26 Yes Details →
3.2.60-1+deb7u3~bpo60+1 U27 Yes Details →
3.2.60-1+deb7u2 U27 Yes Details →
3.2.60-1+deb7u1 U27 Yes Details →
3.2.57-3 U30 Yes Details →
3.2.57-3+deb7u2 U28 Yes Details →
3.2.57-3+deb7u2~bpo60+1 U29 Yes Details →
3.2.57-3+deb7u1 U29 Yes Details →
3.2.57-2 U30 Yes Details →
3.2.57-1 U30 Yes Details →
3.2.54-2 U30 Yes Details →
3.2.54-2~bpo60+1 U30 Yes Details →
3.2.54-1 U30 Yes Details →
3.2.53-2 U30 Yes Details →
3.2.53-1 U30 Yes Details →
3.2.51-1 U30 Yes Details →
3.2.51-1~bpo60+1 U30 Yes Details →
3.2.46-1 U31 Yes Details →
3.2.46-1~bpo60+1 U31 Yes Details →
3.2.46-1+deb7u1 U30 Yes Details →
3.2.46-1+deb7u1~bpo60+1 U31 Yes Details →
3.2.41-2 U32 Yes Details →
3.2.41-2+deb7u2 U31 Yes Details →
3.2.41-2+deb7u2~bpo60+1 U32 Yes Details →
3.2.41-2+deb7u1 U32 Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2013 2
  • 2014 6
  • 2015 9
  • 2016 5
  • 2017 7
  • 2018 3

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

03 Vulnerabilities

Recorded vulnerabilities for linux

The 5 most severe of 32 vulnerabilities recorded for this package

Search all 32 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Linux Security Update - Vulnerability in linux package N/A unrated 3.2.81-2 02 Sep 2016
Linux Kernel - Multiple Vulnerabilities N/A unrated 3.2.96-1 09 Dec 2017
Linux Kernel - Multiple Vulnerabilities N/A unrated 3.2.73-2+deb7u3 03 Mar 2016
Security Update for Linux N/A unrated 3.2.84-1 01 Jan 2017
Linux Kernel - Multiple Vulnerabilities N/A unrated 3.2.88-1 28 Apr 2017

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

Is linux safe to use?

Vulert records 32 vulnerabilities for linux in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 32 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 have?

32 vulnerabilities are recorded for linux in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 32 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 vulnerabilities disclosed?

0 vulnerabilities were recorded for linux in the last 12 months, and the oldest entry in this database dates to 15 May 2013. 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 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 for upcoming vulnerabilities?

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