Vulnerability Database · Debian · Package report

linux-2.6: vulnerability history, versions and safety

linux-2.6 is a package in the Debian ecosystem. Vulert records 24 vulnerabilities for it across 45 releases, from Dec 2009 to Feb 2016. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
24 vulnerabilities recorded U24
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-2.6 i

Updated on 23 Oct 2026

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

Long-term outlook: usable, with an upgrade 24 vulnerabilities on record across 6 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 24 over 6 years · 0 in the last year i
  • Latest disclosure 28 Feb 2016 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-2.6, 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
2.6.32-48 U18 Yes Details →
2.6.32-48squeeze19 U1 Yes Details →
2.6.32-48squeeze18 U2 Yes Details →
2.6.32-48squeeze17 U3 Yes Details →
2.6.32-48squeeze16 U4 Yes Details →
2.6.32-48squeeze14 U5 Yes Details →
2.6.32-48squeeze13 U6 Yes Details →
2.6.32-48squeeze12 U7 Yes Details →
2.6.32-48squeeze11 U8 Yes Details →
2.6.32-48squeeze10 U9 Yes Details →
2.6.32-48squeeze9 U10 Yes Details →
2.6.32-48squeeze8 U11 Yes Details →
2.6.32-48squeeze7 U12 Yes Details →
2.6.32-48squeeze6 U13 Yes Details →
2.6.32-48squeeze5 U14 Yes Details →
2.6.32-48squeeze4 U15 Yes Details →
2.6.32-48squeeze3 U16 Yes Details →
2.6.32-48squeeze1 U17 Yes Details →
2.6.32-47 U18 Yes Details →
2.6.32-46 U18 Yes Details →
2.6.32-46squeeze1 U18 Yes Details →
2.6.32-45 U18 Yes Details →
2.6.32-44 U18 Yes Details →
2.6.32-43 U19 Yes Details →
2.6.32-42 U19 Yes Details →
2.6.32-41 U20 Yes Details →
2.6.32-41squeeze2 U19 Yes Details →
2.6.32-40 U20 Yes Details →
2.6.32-39 U21 Yes Details →
2.6.32-39squeeze1 U20 Yes Details →
2.6.32-38 U21 Yes Details →
2.6.32-37 U21 Yes Details →
2.6.32-36 U21 Yes Details →
2.6.32-35 U22 Yes Details →
2.6.32-35~bpo50+1 U22 Yes Details →
2.6.32-35squeeze2 U21 Yes Details →
2.6.32-35squeeze1 U21 Yes Details →
2.6.32-34 U23 Yes Details →
2.6.32-34squeeze1 U22 Yes Details →
2.6.32-33 U23 Yes Details →
2.6.32-32 U23 Yes Details →
2.6.32-31 U23 Yes Details →
2.6.32-31~bpo50+1 U23 Yes Details →
2.6.32-30 U23 Yes Details →
2.6.32-30+m68k.5 U23 Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2009 1
  • 2011 2
  • 2012 3
  • 2013 3
  • 2014 6
  • 2015 6
  • 2016 3

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

03 Vulnerabilities

Recorded vulnerabilities for linux-2.6

The 5 most severe of 24 vulnerabilities recorded for this package

Search all 24 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Security Update for linux-2.6 N/A unrated 2.6.32-48squeeze11 18 Feb 2015
Vulnerability in linux-2.6 package N/A unrated 2.6.32-48squeeze3 14 May 2013
Security Update for linux-2.6 N/A unrated 2.6.32-48squeeze9 09 Dec 2014
Security Update for linux-2.6 N/A unrated 2.6.32-48squeeze10 21 Dec 2014
Vulnerability in linux-2.6 package N/A unrated 2.6.30-8squeeze1 08 Dec 2009

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

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

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-2.6

Is linux-2.6 safe to use?

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

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

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

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