Linux Kernel vulnerabilities: known CVEs & security history
Linux · Operating System · 2799 tracked CVEs · 6 actively exploited · updated August 2026 · what is a CVE? →
This is the full list of known vulnerabilities (CVEs) across all Linux Kernel release lines — 2799 in total, with 6 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 2799. Open any CVE for full details.
| CVE | Severity | CVSS | EPSS | Year |
|---|---|---|---|---|
| CVE-2025-10585⚡ exploited | critical | 9.8 | 5% | 2025 |
| 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-31431⚡ exploited | high | 7.8 | 95% | 2026 |
| CVE-2025-38352⚡ exploited | high | 7.8 | 1% | 2025 |
| 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-2025-38429 | critical | 10 | 0% | 2025 |
| CVE-2025-22021 | critical | 10 | 0% | 2025 |
| CVE-2025-21663 | critical | 10 | 0% | 2025 |
| 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-63800 | critical | 9.8 | 1% | 2026 |
| CVE-2026-53399 | critical | 9.8 | 1% | 2026 |
| CVE-2026-53398 | critical | 9.8 | 1% | 2026 |
| CVE-2026-53384 | critical | 9.8 | 0% | 2026 |
| CVE-2026-13446 | critical | 9.8 | 0% | 2026 |
| CVE-2026-8505 | critical | 9.8 | 1% | 2026 |
| CVE-2026-9103 | critical | 9.8 | 0% | 2026 |
| CVE-2026-53363 | critical | 9.8 | 0% | 2026 |
| CVE-2026-13019 | critical | 9.8 | 0% | 2026 |
| CVE-2026-9182 | critical | 9.8 | 0% | 2026 |
| CVE-2026-9181 | critical | 9.8 | 1% | 2026 |
| CVE-2026-53355 | critical | 9.8 | 0% | 2026 |
| CVE-2026-14121 | critical | 9.8 | 0% | 2026 |
| CVE-2026-13776 | critical | 9.8 | 0% | 2026 |
| CVE-2026-13775 | critical | 9.8 | 0% | 2026 |
| CVE-2026-53309 | critical | 9.8 | 0% | 2026 |
| CVE-2026-53260 | critical | 9.8 | 0% | 2026 |
| CVE-2026-53247 | critical | 9.8 | 1% | 2026 |
| CVE-2026-53246 | critical | 9.8 | 0% | 2026 |
| CVE-2026-53228 | critical | 9.8 | 1% | 2026 |
| CVE-2026-53221 | critical | 9.8 | 1% | 2026 |
| CVE-2026-53216 | critical | 9.8 | 1% | 2026 |
| CVE-2026-53215 | critical | 9.8 | 1% | 2026 |
| CVE-2026-53176 | critical | 9.8 | 1% | 2026 |
| CVE-2026-53175 | critical | 9.8 | 0% | 2026 |
| CVE-2026-53151 | critical | 9.8 | 0% | 2026 |
| CVE-2026-53088 | critical | 9.8 | 0% | 2026 |
| CVE-2026-53086 | critical | 9.8 | 0% | 2026 |
| CVE-2026-53055 | critical | 9.8 | 0% | 2026 |
| CVE-2026-53049 | critical | 9.8 | 1% | 2026 |
| CVE-2026-53046 | critical | 9.8 | 1% | 2026 |
| CVE-2026-53045 | critical | 9.8 | 1% | 2026 |
| CVE-2026-53010 | critical | 9.8 | 0% | 2026 |
| CVE-2026-53006 | critical | 9.8 | 0% | 2026 |
| CVE-2026-53002 | critical | 9.8 | 0% | 2026 |
| CVE-2026-52993 | critical | 9.8 | 0% | 2026 |
| CVE-2026-52989 | critical | 9.8 | 0% | 2026 |
| CVE-2026-52986 | critical | 9.8 | 1% | 2026 |
| CVE-2026-52982 | critical | 9.8 | 1% | 2026 |
| CVE-2026-52955 | critical | 9.8 | 0% | 2026 |
| CVE-2026-52931 | critical | 9.8 | 0% | 2026 |
| CVE-2026-52924 | critical | 9.8 | 0% | 2026 |
| CVE-2026-52914 | critical | 9.8 | 1% | 2026 |
| CVE-2026-46325 | critical | 9.8 | 0% | 2026 |
| CVE-2026-46289 | critical | 9.8 | 0% | 2026 |
| CVE-2026-46195 | critical | 9.8 | 1% | 2026 |
| CVE-2026-46137 | critical | 9.8 | 1% | 2026 |
| CVE-2026-46135 | critical | 9.8 | 0% | 2026 |
| CVE-2026-46115 | critical | 9.8 | 0% | 2026 |
| CVE-2026-45972 | critical | 9.8 | 0% | 2026 |
| CVE-2026-45898 | critical | 9.8 | 0% | 2026 |
| CVE-2026-43501 | critical | 9.8 | 0% | 2026 |
| CVE-2026-24207 | critical | 9.8 | 2% | 2026 |
| CVE-2026-43493 | critical | 9.8 | 1% | 2026 |
| CVE-2026-43414 | critical | 9.8 | 0% | 2026 |
| CVE-2026-43341 | critical | 9.8 | 0% | 2026 |
| CVE-2026-43198 | critical | 9.8 | 0% | 2026 |
| CVE-2026-43125 | critical | 9.8 | 0% | 2026 |
| CVE-2026-43038 | critical | 9.8 | 0% | 2026 |
| CVE-2026-43037 | critical | 9.8 | 1% | 2026 |
| CVE-2026-43011 | critical | 9.8 | 1% | 2026 |
| CVE-2026-31669 | critical | 9.8 | 0% | 2026 |
2719 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 2799 CVEs for Linux Kernel, 6 of which are actively exploited (CISA KEV). 214 are critical-severity and 1647 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 — 6 Linux Kernel CVEs are in CISA's Known Exploited Vulnerabilities catalog, meaning they are confirmed exploited in the wild. 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.1.5) 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.