Linux Kernel vulnerabilities: known CVEs & security history
Linux · Operating System · 5445 tracked CVEs · 13 actively exploited · updated September 2026 · what is a CVE? →
This is the full list of known vulnerabilities (CVEs) across all Linux Kernel release lines — 5445 in total, with 13 actively exploited in the wild. A CVE here doesn't mean your version is affected — check Linux Kernel's current status and the safe version to run.
Known Linux Kernel CVEs
Actively-exploited and most-severe first. Showing the top 80 of 5445. Open any CVE for full details.
| CVE | Severity | CVSS | EPSS | Year |
|---|---|---|---|---|
| CVE-2025-10585⚡ exploited | critical | 9.8 | 5% | 2025 |
| CVE-2016-1019⚡ exploited | critical | 9.8 | 22% | 2016 |
| CVE-2026-11645⚡ exploited | high | 8.8 | 2% | 2026 |
| CVE-2026-5281⚡ exploited | high | 8.8 | 5% | 2026 |
| CVE-2025-13223⚡ exploited | high | 8.8 | 5% | 2025 |
| CVE-2026-53362⚡ exploited | high | 7.8 | 1% | 2026 |
| CVE-2026-31431⚡ exploited | high | 7.8 | 100% | 2026 |
| CVE-2025-38352⚡ exploited | high | 7.8 | 1% | 2025 |
| CVE-2024-1086⚡ exploited | high | 7.8 | 28% | 2024 |
| CVE-2022-0995⚡ exploited | high | 7.8 | 6% | 2022 |
| CVE-2018-15982⚡ exploited | high | 7.8 | 82% | 2019 |
| CVE-2022-30333⚡ exploited | high | 7.5 | 99% | 2022 |
| CVE-2022-2586⚡ exploited | medium | 5.3 | 10% | 2024 |
| CVE-2026-76197 | critical | 10 | 2% | 2026 |
| CVE-2026-76195 | critical | 10 | 2% | 2026 |
| CVE-2026-76193 | critical | 10 | 1% | 2026 |
| CVE-2026-48331 | critical | 10 | 0% | 2026 |
| CVE-2026-48330 | critical | 10 | 1% | 2026 |
| CVE-2026-48323 | critical | 10 | 1% | 2026 |
| CVE-2026-48449 | critical | 10 | 1% | 2026 |
| CVE-2026-63795 | critical | 10 | 0% | 2026 |
| CVE-2026-13782 | critical | 10 | 0% | 2026 |
| CVE-2026-48286 | critical | 10 | 1% | 2026 |
| CVE-2026-48303 | critical | 10 | 1% | 2026 |
| CVE-2026-47938 | critical | 10 | 0% | 2026 |
| CVE-2025-38429 | critical | 10 | 0% | 2025 |
| CVE-2025-22021 | critical | 10 | 0% | 2025 |
| CVE-2025-21663 | critical | 10 | 0% | 2025 |
| CVE-2024-56719 | critical | 10 | 0% | 2024 |
| CVE-2024-44984 | critical | 10 | 0% | 2024 |
| CVE-2024-38558 | critical | 10 | 0% | 2024 |
| CVE-2026-65093 | critical | 9.9 | 0% | 2026 |
| CVE-2026-65083 | critical | 9.9 | 1% | 2026 |
| CVE-2026-48326 | critical | 9.9 | 0% | 2026 |
| CVE-2026-64879 | critical | 9.9 | 3% | 2026 |
| CVE-2026-64878 | critical | 9.9 | 1% | 2026 |
| CVE-2026-8859 | critical | 9.9 | 0% | 2026 |
| CVE-2026-8635 | critical | 9.9 | 0% | 2026 |
| CVE-2026-8481 | critical | 9.9 | 0% | 2026 |
| CVE-2026-8476 | critical | 9.9 | 0% | 2026 |
| CVE-2026-9135 | critical | 9.9 | 1% | 2026 |
| CVE-2026-47627 | critical | 9.8 | 0% | 2026 |
| CVE-2026-24254 | critical | 9.8 | 0% | 2026 |
| CVE-2026-48333 | critical | 9.8 | 0% | 2026 |
| CVE-2026-64439 | critical | 9.8 | 0% | 2026 |
| CVE-2026-64410 | critical | 9.8 | 0% | 2026 |
| CVE-2026-64399 | critical | 9.8 | 0% | 2026 |
| CVE-2026-64397 | critical | 9.8 | 0% | 2026 |
| CVE-2026-64391 | critical | 9.8 | 0% | 2026 |
| CVE-2026-64387 | critical | 9.8 | 0% | 2026 |
| CVE-2026-64386 | critical | 9.8 | 0% | 2026 |
| CVE-2026-64385 | critical | 9.8 | 0% | 2026 |
| CVE-2026-64384 | critical | 9.8 | 0% | 2026 |
| CVE-2026-64383 | critical | 9.8 | 0% | 2026 |
| CVE-2026-64355 | critical | 9.8 | 1% | 2026 |
| CVE-2026-64303 | critical | 9.8 | 1% | 2026 |
| CVE-2026-64268 | critical | 9.8 | 1% | 2026 |
| CVE-2026-16280 | critical | 9.8 | 0% | 2026 |
| CVE-2026-64232 | critical | 9.8 | 0% | 2026 |
| CVE-2026-64216 | critical | 9.8 | 0% | 2026 |
| CVE-2026-64162 | critical | 9.8 | 0% | 2026 |
| CVE-2026-64160 | critical | 9.8 | 0% | 2026 |
| CVE-2026-64150 | critical | 9.8 | 0% | 2026 |
| CVE-2026-64142 | critical | 9.8 | 0% | 2026 |
| CVE-2026-64136 | critical | 9.8 | 0% | 2026 |
| CVE-2026-64132 | critical | 9.8 | 0% | 2026 |
| CVE-2026-64125 | critical | 9.8 | 1% | 2026 |
| CVE-2026-64122 | critical | 9.8 | 0% | 2026 |
| CVE-2026-64113 | critical | 9.8 | 1% | 2026 |
| CVE-2026-64102 | critical | 9.8 | 1% | 2026 |
| CVE-2026-64091 | critical | 9.8 | 1% | 2026 |
| CVE-2026-64089 | critical | 9.8 | 1% | 2026 |
| CVE-2026-64069 | critical | 9.8 | 0% | 2026 |
| CVE-2026-64068 | critical | 9.8 | 0% | 2026 |
| CVE-2026-64067 | critical | 9.8 | 0% | 2026 |
| CVE-2026-64066 | critical | 9.8 | 0% | 2026 |
| CVE-2026-64061 | critical | 9.8 | 0% | 2026 |
| CVE-2026-64056 | critical | 9.8 | 1% | 2026 |
| CVE-2026-64055 | critical | 9.8 | 1% | 2026 |
| CVE-2026-64047 | critical | 9.8 | 1% | 2026 |
5365 older / lower-severity CVEs not shown — see Linux Kernel's full record.
Is my Linux Kernel version affected?
The list above spans every release. To know whether your version is affected — and the minimum safe version to upgrade to — check it directly.
Check your Linux Kernel version → · Monitor Linux Kernel for new CVEs →
Linux Kernel vulnerabilities — frequently asked
How many known vulnerabilities does Linux Kernel have?
IsItPatched tracks 5445 CVEs for Linux Kernel, 13 of which are actively exploited (CISA KEV). 476 are critical-severity and 3715 high-severity. These span every release line — what matters is whether the version you run is affected.
Does Linux Kernel have any actively-exploited vulnerabilities?
Yes — 13 Linux Kernel CVEs are in CISA's Known Exploited Vulnerabilities catalog, meaning they are confirmed exploited in the wild (4 linked to ransomware). Patch these as a priority.
What is the most severe Linux Kernel vulnerability?
Among tracked issues, CVE-2025-10585 (CRITICAL, CVSS 9.8), which is actively exploited, ranks highest — a CWE-843 weakness.
Is Linux Kernel safe to use?
It depends on the version. The latest supported Linux Kernel release (7.2.6) clears the known issues; older versions may still be affected. Check the exact version you run for a verdict.
CVE data aggregated from NVD, CISA KEV and EPSS (FIRST.org). Related: Linux Kernel security status · Linux Kernel end-of-life · actively-exploited CVEs. Always verify against Linux's advisories — see our disclaimer.