Vulnerability Database · Android · Package report

:linux_kernel:: vulnerability history, versions and safety

:linux_kernel: is a package in the Android ecosystem. Vulert records 239 vulnerabilities for it across 3 releases, from Jul 2020 to Sep 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
239 vulnerabilities recorded C21 H117 M101
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
30 in the last 12 months

Most recent disclosure 01 Sep 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on :linux_kernel: i

Updated on 23 Oct 2026

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

Long-term outlook: usable, with an upgrade 239 vulnerabilities on record across 6 years, 30 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 239 over 6 years · 30 in the last year i
  • Latest disclosure 01 Sep 2026 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_kernel:, 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
Kernel C21 H116 M100 Yes Details →
oc-mr1 H1 Yes Details →
Device specific M1 Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 11
  • 2021 57
  • 2022 96
  • 2023 26
  • 2024 7
  • 2025 21
  • 2026 21

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

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_kernel:

Is :linux_kernel: safe to use?

Vulert records 239 vulnerabilities for :linux_kernel: in Android: 21 critical, 117 high, 101 medium and 0 low. 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_kernel: have?

239 vulnerabilities are recorded for :linux_kernel: in the Android ecosystem: 21 critical, 117 high, 101 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new :linux_kernel: vulnerabilities disclosed?

30 vulnerabilities were recorded for :linux_kernel: in the last 12 months, and the oldest entry in this database dates to 01 Jul 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_kernel: 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_kernel: for upcoming vulnerabilities?

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