Last scanned:
This image carries significant risk; production deployment is highly discouraged without strict compensating controls. The most impactful exposed issues, CVE-2026-58012 and CVE-2026-58013 in GLib, could let an attacker crash the inference server or leak a handful of bytes of process memory by feeding crafted strings into regex replacement or custom line-terminator handling, disrupting service availability for anything relying on this endpoint. Enforcing a network policy that blocks untrusted inbound traffic to the serving port removes the remote attack path for these GLib over-reads entirely. Note that CVE-2026-0861 only bites if attacker-controlled size and alignment values reach the memalign family, and the DANE TLSA use-after-free (CVE-2026-28387) applies only to clients doing DANE TLSA server authentication with mixed PKIX and DANE-TA records, neither of which is part of the standard vLLM OpenAI serving path.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-58012 | MEDIUM6.97 | libglib2.0-0t64 2.80.0-6ubuntu3.8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-58013 | MEDIUM6.97 | libglib2.0-0t64 2.80.0-6ubuntu3.8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-0861 | MEDIUM6.88 | libc-bin 2.39-0ubuntu8.5 fixed in 2.39-0ubuntu8.7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0861 | MEDIUM6.88 | libc-dev-bin 2.39-0ubuntu8.5 fixed in 2.39-0ubuntu8.7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0861 | MEDIUM6.88 | libc6 2.39-0ubuntu8.5 fixed in 2.39-0ubuntu8.7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0861 | MEDIUM6.88 | libc6-dev 2.39-0ubuntu8.5 fixed in 2.39-0ubuntu8.7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-28387 | MEDIUM6.88 | libssl3t64 3.0.13-0ubuntu3.5 fixed in 3.0.13-0ubuntu3.9 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-23300 | MEDIUM6.63 | cuda-compat-13-0 580.82.07-0ubuntu1 fixed in 580.95.05-0ubuntu0.24.04.2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libbinutils 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libbinutils 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libbinutils 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libbinutils 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libbinutils 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libbinutils 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libctf-nobfd0 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libctf-nobfd0 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libctf-nobfd0 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libctf-nobfd0 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libctf-nobfd0 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libctf-nobfd0 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libctf0 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libctf0 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libctf0 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libctf0 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libctf0 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libctf0 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76957 | MEDIUM6.63 | libexpat1 2.6.1-2ubuntu0.4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-76957 | MEDIUM6.63 | libexpat1-dev 2.6.1-2ubuntu0.4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libgprofng0 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libgprofng0 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libgprofng0 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libgprofng0 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libgprofng0 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libgprofng0 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-48962 | MEDIUM6.63 | libperl5.38t64 5.38.2-3.2ubuntu0.2 fixed in 5.38.2-3.2ubuntu0.4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2016-2568 | MEDIUM6.63 | libpolkit-agent-1-0 124-2ubuntu1.24.04.3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2016-2568 | MEDIUM6.63 | libpolkit-gobject-1-0 124-2ubuntu1.24.04.3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libsframe1 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libsframe1 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libsframe1 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libsframe1 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libsframe1 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libsframe1 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-11822 | MEDIUM6.63 | libsqlite3-0 3.45.1-1ubuntu2.4 fixed in 3.45.1-1ubuntu2.6 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-11824 | MEDIUM6.63 | libsqlite3-0 3.45.1-1ubuntu2.4 fixed in 3.45.1-1ubuntu2.6 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-86140 | MEDIUM6.63 | libxml2 2.9.14+dfsg-1.3ubuntu3.8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1352 | MEDIUM6.38 | libdw1t64 0.190-1.1ubuntu0.1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1352 | MEDIUM6.38 | libelf1t64 0.190-1.1ubuntu0.1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-45186 | MEDIUM6.38 | libexpat1 2.6.1-2ubuntu0.4 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-66046 | MEDIUM6.38 | libexpat1 2.6.1-2ubuntu0.4 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-45186 | MEDIUM6.38 | libexpat1-dev 2.6.1-2ubuntu0.4 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-66046 | MEDIUM6.38 | libexpat1-dev 2.6.1-2ubuntu0.4 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-41989 | MEDIUM6.38 | libgcrypt20 1.10.3-2build1 fixed in 1.10.3-2ubuntu0.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-58011 | MEDIUM6.38 | libglib2.0-0t64 2.80.0-6ubuntu3.8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-58015 | MEDIUM6.38 | libglib2.0-0t64 2.80.0-6ubuntu3.8 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM6.38 | libgssapi-krb5-2 1.20.1-6ubuntu2.6 fixed in 1.20.1-6ubuntu2.7 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM6.38 | libgssapi-krb5-2 1.20.1-6ubuntu2.6 fixed in 1.20.1-6ubuntu2.7 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-32316 | MEDIUM6.38 | libjq1 1.7.1-3ubuntu0.24.04.1 fixed in 1.7.1-3ubuntu0.24.04.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40164 | MEDIUM6.38 | libjq1 1.7.1-3ubuntu0.24.04.1 fixed in 1.7.1-3ubuntu0.24.04.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM6.38 | libk5crypto3 1.20.1-6ubuntu2.6 fixed in 1.20.1-6ubuntu2.7 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM6.38 | libk5crypto3 1.20.1-6ubuntu2.6 fixed in 1.20.1-6ubuntu2.7 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM6.38 | libkrb5-3 1.20.1-6ubuntu2.6 fixed in 1.20.1-6ubuntu2.7 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM6.38 | libkrb5-3 1.20.1-6ubuntu2.6 fixed in 1.20.1-6ubuntu2.7 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM6.38 | libkrb5support0 1.20.1-6ubuntu2.6 fixed in 1.20.1-6ubuntu2.7 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM6.38 | libkrb5support0 1.20.1-6ubuntu2.6 fixed in 1.20.1-6ubuntu2.7 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-27135 | MEDIUM6.38 | libnghttp2-14 1.59.0-1ubuntu0.2 fixed in 1.59.0-1ubuntu0.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-42497 | MEDIUM6.38 | libperl5.38t64 5.38.2-3.2ubuntu0.2 fixed in 5.38.2-3.2ubuntu0.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-57433 | MEDIUM6.38 | libperl5.38t64 5.38.2-3.2ubuntu0.2 fixed in 5.38.2-3.2ubuntu0.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9538 | MEDIUM6.38 | libperl5.38t64 5.38.2-3.2ubuntu0.2 fixed in 5.38.2-3.2ubuntu0.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3731 | MEDIUM6.38 | libssh-4 0.10.6-2ubuntu0.1 fixed in 0.10.6-2ubuntu0.4 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-59847 | MEDIUM6.38 | libssh-4 0.10.6-2ubuntu0.1 fixed in 0.10.6-2ubuntu0.5 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-59850 | MEDIUM6.38 | libssh-4 0.10.6-2ubuntu0.1 fixed in 0.10.6-2ubuntu0.5 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-63072 | MEDIUM6.38 | libssl3t64 3.0.13-0ubuntu3.5 fixed in 3.0.13-0ubuntu3.15 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-69421 | MEDIUM6.38 | libssl3t64 3.0.13-0ubuntu3.5 fixed in 3.0.13-0ubuntu3.7 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-28388 | MEDIUM6.38 | libssl3t64 3.0.13-0ubuntu3.5 fixed in 3.0.13-0ubuntu3.9 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-28389 | MEDIUM6.38 | libssl3t64 3.0.13-0ubuntu3.5 fixed in 3.0.13-0ubuntu3.9 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-28390 | MEDIUM6.38 | libssl3t64 3.0.13-0ubuntu3.5 fixed in 3.0.13-0ubuntu3.9 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-54874 | MEDIUM6.38 | libssl3t64 3.0.13-0ubuntu3.5 fixed in 3.0.13-0ubuntu3.15 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63074 | MEDIUM6.38 | libssl3t64 3.0.13-0ubuntu3.5 fixed in 3.0.13-0ubuntu3.15 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3833 | MEDIUM6.29 | libgnutls30t64 3.8.3-1.1ubuntu3.4 fixed in 3.8.3-1.1ubuntu3.6 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42011 | MEDIUM6.29 | libgnutls30t64 3.8.3-1.1ubuntu3.4 fixed in 3.8.3-1.1ubuntu3.6 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-34182 | MEDIUM6.29 | libssl3t64 3.0.13-0ubuntu3.5 fixed in 3.0.13-0ubuntu3.11 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-69419 | MEDIUM6.29 | libssl3t64 3.0.13-0ubuntu3.5 fixed in 3.0.13-0ubuntu3.7 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-48526 | MEDIUM6.29 | python3-jwt 2.7.0-1ubuntu0.1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-16118 | MEDIUM6.03 | libglib2.0-0t64 2.80.0-6ubuntu3.8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42012 | MEDIUM6.03 | libgnutls30t64 3.8.3-1.1ubuntu3.4 fixed in 3.8.3-1.1ubuntu3.6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-23282 | MEDIUM5.95 | cuda-compat-13-0 580.82.07-0ubuntu1 fixed in 580.95.05-0ubuntu0.24.04.2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5222 | MEDIUM5.95 | libicu74 74.2-1ubuntu3.1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-2236 | MEDIUM5.9 | libgcrypt20 1.10.3-2build1 fixed in 1.10.3-2ubuntu0.2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-31790 | MEDIUM5.9 | libssl3t64 3.0.13-0ubuntu3.5 fixed in 3.0.13-0ubuntu3.9 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2025-13151 | MEDIUM5.9 | libtasn1-6 4.19.0-3ubuntu0.24.04.1 fixed in 4.19.0-3ubuntu0.24.04.2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-56132 | MEDIUM5.87 | libexpat1 2.6.1-2ubuntu0.4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56403 | MEDIUM5.87 | libexpat1 2.6.1-2ubuntu0.4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56404 | MEDIUM5.87 | libexpat1 2.6.1-2ubuntu0.4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56405 | MEDIUM5.87 | libexpat1 2.6.1-2ubuntu0.4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56406 | MEDIUM5.87 | libexpat1 2.6.1-2ubuntu0.4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56407 | MEDIUM5.87 | libexpat1 2.6.1-2ubuntu0.4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56410 | MEDIUM5.87 | libexpat1 2.6.1-2ubuntu0.4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56411 | MEDIUM5.87 | libexpat1 2.6.1-2ubuntu0.4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56132 | MEDIUM5.87 | libexpat1-dev 2.6.1-2ubuntu0.4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56403 | MEDIUM5.87 | libexpat1-dev 2.6.1-2ubuntu0.4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56404 | MEDIUM5.87 | libexpat1-dev 2.6.1-2ubuntu0.4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56405 | MEDIUM5.87 | libexpat1-dev 2.6.1-2ubuntu0.4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56406 | MEDIUM5.87 | libexpat1-dev 2.6.1-2ubuntu0.4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56407 | MEDIUM5.87 | libexpat1-dev 2.6.1-2ubuntu0.4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56410 | MEDIUM5.87 | libexpat1-dev 2.6.1-2ubuntu0.4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56411 | MEDIUM5.87 | libexpat1-dev 2.6.1-2ubuntu0.4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19499 | MEDIUM5.78 | libc-bin 2.39-0ubuntu8.5 fixed in 2.39-0ubuntu8.9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-19499 | MEDIUM5.78 | libc-dev-bin 2.39-0ubuntu8.5 fixed in 2.39-0ubuntu8.9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-19499 | MEDIUM5.78 | libc6 2.39-0ubuntu8.5 fixed in 2.39-0ubuntu8.9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-19499 | MEDIUM5.78 | libc6-dev 2.39-0ubuntu8.5 fixed in 2.39-0ubuntu8.9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-23330 | MEDIUM5.61 | cuda-compat-13-0 580.82.07-0ubuntu1 fixed in 580.95.05-0ubuntu0.24.04.2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-23332 | MEDIUM5.61 | cuda-compat-13-0 580.82.07-0ubuntu1 fixed in 580.95.05-0ubuntu0.24.04.2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-23345 | MEDIUM5.61 | cuda-compat-13-0 580.82.07-0ubuntu1 fixed in 580.95.05-0ubuntu0.24.04.2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42014 | MEDIUM5.61 | libgnutls30t64 3.8.3-1.1ubuntu3.4 fixed in 3.8.3-1.1ubuntu3.6 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-9230 | MEDIUM5.6 | libssl3t64 3.0.13-0ubuntu3.5 fixed in 3.0.13-0ubuntu3.6 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | libc-bin 2.39-0ubuntu8.5 fixed in 2.39-0ubuntu8.8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc-bin 2.39-0ubuntu8.5 fixed in 2.39-0ubuntu8.8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | libc-dev-bin 2.39-0ubuntu8.5 fixed in 2.39-0ubuntu8.8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc-dev-bin 2.39-0ubuntu8.5 fixed in 2.39-0ubuntu8.8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | libc6 2.39-0ubuntu8.5 fixed in 2.39-0ubuntu8.8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc6 2.39-0ubuntu8.5 fixed in 2.39-0ubuntu8.8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | libc6-dev 2.39-0ubuntu8.5 fixed in 2.39-0ubuntu8.8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc6-dev 2.39-0ubuntu8.5 fixed in 2.39-0ubuntu8.8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-39979 | MEDIUM5.52 | libjq1 1.7.1-3ubuntu0.24.04.1 fixed in 1.7.1-3ubuntu0.24.04.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-15649 | MEDIUM5.52 | libperl5.38t64 5.38.2-3.2ubuntu0.2 fixed in 5.38.2-3.2ubuntu0.4 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-19487 | MEDIUM5.52 | libperl5.38t64 5.38.2-3.2ubuntu0.2 fixed in 5.38.2-3.2ubuntu0.6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-59843 | MEDIUM5.52 | libssh-4 0.10.6-2ubuntu0.1 fixed in 0.10.6-2ubuntu0.5 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libbinutils 2.42-4ubuntu2.5 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libctf-nobfd0 2.42-4ubuntu2.5 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libctf0 2.42-4ubuntu2.5 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libgprofng0 2.42-4ubuntu2.5 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libsframe1 2.42-4ubuntu2.5 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-54371 | MEDIUM5.35 | libattr1 1:2.5.2-1build1.1 fixed in 1:2.5.2-1ubuntu0.1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0964 | MEDIUM5.35 | libssh-4 0.10.6-2ubuntu0.1 fixed in 0.10.6-2ubuntu0.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-59375 | MEDIUM5.3 | libexpat1 2.6.1-2ubuntu0.4 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-59375 | MEDIUM5.3 | libexpat1-dev 2.6.1-2ubuntu0.4 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42766 | MEDIUM5.3 | libssl3t64 3.0.13-0ubuntu3.5 fixed in 3.0.13-0ubuntu3.11 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-72522 | MEDIUM5.27 | libexpat1 2.6.1-2ubuntu0.4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-72522 | MEDIUM5.27 | libexpat1-dev 2.6.1-2ubuntu0.4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13757 | MEDIUM5.27 | libp11-kit0 0.25.3-4ubuntu2.1 fixed in 0.25.3-4ubuntu2.2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18938 | MEDIUM5.27 | libp11-kit0 0.25.3-4ubuntu2.1 fixed in 0.25.3-4ubuntu2.2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-39956 | MEDIUM5.18 | libjq1 1.7.1-3ubuntu0.24.04.1 fixed in 1.7.1-3ubuntu0.24.04.2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-33221 | MEDIUM5.1 | cuda-compat-13-0 580.82.07-0ubuntu1 fixed in 580.159.03-0ubuntu0.24.04.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | libc-bin 2.39-0ubuntu8.5 fixed in 2.39-0ubuntu8.7 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc-bin 2.39-0ubuntu8.5 fixed in 2.39-0ubuntu8.8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.02 | libc-bin 2.39-0ubuntu8.5 fixed in 2.39-0ubuntu8.9 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.02 | libc-bin 2.39-0ubuntu8.5 fixed in 2.39-0ubuntu8.9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.02 | libc-bin 2.39-0ubuntu8.5 fixed in 2.39-0ubuntu8.9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | libc-dev-bin 2.39-0ubuntu8.5 fixed in 2.39-0ubuntu8.7 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc-dev-bin 2.39-0ubuntu8.5 fixed in 2.39-0ubuntu8.8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.02 | libc-dev-bin 2.39-0ubuntu8.5 fixed in 2.39-0ubuntu8.9 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.02 | libc-dev-bin 2.39-0ubuntu8.5 fixed in 2.39-0ubuntu8.9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.02 | libc-dev-bin 2.39-0ubuntu8.5 fixed in 2.39-0ubuntu8.9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | libc6 2.39-0ubuntu8.5 fixed in 2.39-0ubuntu8.7 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc6 2.39-0ubuntu8.5 fixed in 2.39-0ubuntu8.8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.02 | libc6 2.39-0ubuntu8.5 fixed in 2.39-0ubuntu8.9 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.02 | libc6 2.39-0ubuntu8.5 fixed in 2.39-0ubuntu8.9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.02 | libc6 2.39-0ubuntu8.5 fixed in 2.39-0ubuntu8.9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | libc6-dev 2.39-0ubuntu8.5 fixed in 2.39-0ubuntu8.7 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc6-dev 2.39-0ubuntu8.5 fixed in 2.39-0ubuntu8.8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.02 | libc6-dev 2.39-0ubuntu8.5 fixed in 2.39-0ubuntu8.9 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.02 | libc6-dev 2.39-0ubuntu8.5 fixed in 2.39-0ubuntu8.9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.02 | libc6-dev 2.39-0ubuntu8.5 fixed in 2.39-0ubuntu8.9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-50219 | MEDIUM5.02 | libexpat1 2.6.1-2ubuntu0.4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56412 | MEDIUM5.02 | libexpat1 2.6.1-2ubuntu0.4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-50219 | MEDIUM5.02 | libexpat1-dev 2.6.1-2ubuntu0.4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56412 | MEDIUM5.02 | libexpat1-dev 2.6.1-2ubuntu0.4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-59845 | MEDIUM5.02 | libssh-4 0.10.6-2ubuntu0.1 fixed in 0.10.6-2ubuntu0.5 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69420 | MEDIUM5.02 | libssl3t64 3.0.13-0ubuntu3.5 fixed in 3.0.13-0ubuntu3.7 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-22796 | MEDIUM5.02 | libssl3t64 3.0.13-0ubuntu3.5 fixed in 3.0.13-0ubuntu3.7 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42770 | MEDIUM5.02 | libssl3t64 3.0.13-0ubuntu3.5 fixed in 3.0.13-0ubuntu3.11 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-9076 | MEDIUM5.02 | libssl3t64 3.0.13-0ubuntu3.5 fixed in 3.0.13-0ubuntu3.11 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-48524 | MEDIUM5.02 | python3-jwt 2.7.0-1ubuntu0.1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34180 | MEDIUM5 | libssl3t64 3.0.13-0ubuntu3.5 fixed in 3.0.13-0ubuntu3.11 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-15534 | MEDIUM4.84 | libperl5.38t64 5.38.2-3.2ubuntu0.2 fixed in 5.38.2-3.2ubuntu0.6 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-24195 | MEDIUM4.67 | cuda-compat-13-0 580.82.07-0ubuntu1 fixed in 580.159.03-0ubuntu0.24.04.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libbinutils 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libbinutils 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libbinutils 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libbinutils 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libbinutils 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libbinutils 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libbinutils 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libbinutils 2.42-4ubuntu2.5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM4.67 | libc-bin 2.39-0ubuntu8.5 fixed in 2.39-0ubuntu8.9 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM4.67 | libc-dev-bin 2.39-0ubuntu8.5 fixed in 2.39-0ubuntu8.9 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM4.67 | libc6 2.39-0ubuntu8.5 fixed in 2.39-0ubuntu8.9 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM4.67 | libc6-dev 2.39-0ubuntu8.5 fixed in 2.39-0ubuntu8.9 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libctf-nobfd0 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libctf-nobfd0 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libctf-nobfd0 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libctf-nobfd0 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libctf-nobfd0 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libctf-nobfd0 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libctf-nobfd0 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libctf-nobfd0 2.42-4ubuntu2.5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libctf0 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libctf0 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libctf0 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libctf0 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libctf0 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libctf0 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libctf0 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libctf0 2.42-4ubuntu2.5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19617 | MEDIUM4.67 | libdevmapper1.02.1 2:1.02.185-3ubuntu3.2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66382 | MEDIUM4.67 | libexpat1 2.6.1-2ubuntu0.4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32776 | MEDIUM4.67 | libexpat1 2.6.1-2ubuntu0.4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32777 | MEDIUM4.67 | libexpat1 2.6.1-2ubuntu0.4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32778 | MEDIUM4.67 | libexpat1 2.6.1-2ubuntu0.4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66382 | MEDIUM4.67 | libexpat1-dev 2.6.1-2ubuntu0.4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32776 | MEDIUM4.67 | libexpat1-dev 2.6.1-2ubuntu0.4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32777 | MEDIUM4.67 | libexpat1-dev 2.6.1-2ubuntu0.4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32778 | MEDIUM4.67 | libexpat1-dev 2.6.1-2ubuntu0.4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libgprofng0 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libgprofng0 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libgprofng0 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libgprofng0 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libgprofng0 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libgprofng0 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libgprofng0 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libgprofng0 2.42-4ubuntu2.5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-33947 | MEDIUM4.67 | libjq1 1.7.1-3ubuntu0.24.04.1 fixed in 1.7.1-3ubuntu0.24.04.2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-41256 | MEDIUM4.67 | libjq1 1.7.1-3ubuntu0.24.04.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-41257 | MEDIUM4.67 | libjq1 1.7.1-3ubuntu0.24.04.1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43896 | MEDIUM4.67 | libjq1 1.7.1-3ubuntu0.24.04.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-44777 | MEDIUM4.67 | libjq1 1.7.1-3ubuntu0.24.04.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libsframe1 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libsframe1 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libsframe1 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libsframe1 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libsframe1 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libsframe1 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libsframe1 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libsframe1 2.42-4ubuntu2.5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-50812 | MEDIUM4.67 | libsqlite3-0 3.45.1-1ubuntu2.4 fixed in 3.45.1-1ubuntu2.7 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-50813 | MEDIUM4.67 | libsqlite3-0 3.45.1-1ubuntu2.4 fixed in 3.45.1-1ubuntu2.7 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-0967 | MEDIUM4.67 | libssh-4 0.10.6-2ubuntu0.1 fixed in 0.10.6-2ubuntu0.3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-22795 | MEDIUM4.67 | libssl3t64 3.0.13-0ubuntu3.5 fixed in 3.0.13-0ubuntu3.7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-7383 | MEDIUM4.67 | libssl3t64 3.0.13-0ubuntu3.5 fixed in 3.0.13-0ubuntu3.11 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-58016 | MEDIUM4.64 | libglib2.0-bin 2.80.0-6ubuntu3.8 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-45445 | MEDIUM4.64 | openssl 3.0.13-0ubuntu3.5 fixed in 3.0.13-0ubuntu3.11 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-42496 | MEDIUM4.64 | perl 5.38.2-3.2ubuntu0.2 fixed in 5.38.2-3.2ubuntu0.3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42496 | MEDIUM4.64 | perl-base 5.38.2-3.2ubuntu0.2 fixed in 5.38.2-3.2ubuntu0.3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13221 | MEDIUM4.64 | perl-modules-5.38 5.38.2-3.2ubuntu0.2 fixed in 5.38.2-3.2ubuntu0.4 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42496 | MEDIUM4.64 | perl-modules-5.38 5.38.2-3.2ubuntu0.2 fixed in 5.38.2-3.2ubuntu0.3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-58055 | MEDIUM4.59 | libnghttp2-14 1.59.0-1ubuntu0.2 fixed in 1.59.0-1ubuntu0.4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-48523 | MEDIUM4.59 | python3-jwt 2.7.0-1ubuntu0.1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3497 | MEDIUM4.5 | openssh-client 1:9.6p1-3ubuntu13.13 fixed in 1:9.6p1-3ubuntu13.15 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-63076 | MEDIUM4.5 | openssl 3.0.13-0ubuntu3.5 fixed in 3.0.13-0ubuntu3.15 | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2018-6952 | MEDIUM4.5 | patch 2.7.6-7build3 No fix yet | 8.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-21441 | MEDIUM4.5 | python3-pip 24.0+dfsg-1ubuntu1.3 No fix yet | 3.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-21441 | MEDIUM4.5 | python3-pip-whl 24.0+dfsg-1ubuntu1.3 No fix yet | 3.0% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1147 | MEDIUM4.5 | libbinutils 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM4.5 | libc-bin 2.39-0ubuntu8.5 fixed in 2.39-0ubuntu8.7 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc-bin 2.39-0ubuntu8.5 fixed in 2.39-0ubuntu8.8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM4.5 | libc-dev-bin 2.39-0ubuntu8.5 fixed in 2.39-0ubuntu8.7 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc-dev-bin 2.39-0ubuntu8.5 fixed in 2.39-0ubuntu8.8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM4.5 | libc6 2.39-0ubuntu8.5 fixed in 2.39-0ubuntu8.7 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc6 2.39-0ubuntu8.5 fixed in 2.39-0ubuntu8.8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM4.5 | libc6-dev 2.39-0ubuntu8.5 fixed in 2.39-0ubuntu8.7 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc6-dev 2.39-0ubuntu8.5 fixed in 2.39-0ubuntu8.8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libctf-nobfd0 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libctf0 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-15588 | MEDIUM4.5 | libglib2.0-0t64 2.80.0-6ubuntu3.8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14831 | MEDIUM4.5 | libgnutls30t64 3.8.3-1.1ubuntu3.4 fixed in 3.8.3-1.1ubuntu3.5 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-42015 | MEDIUM4.5 | libgnutls30t64 3.8.3-1.1ubuntu3.4 fixed in 3.8.3-1.1ubuntu3.6 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libgprofng0 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-33948 | MEDIUM4.5 | libjq1 1.7.1-3ubuntu0.24.04.1 fixed in 1.7.1-3ubuntu0.24.04.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-34743 | MEDIUM4.5 | liblzma5 5.6.1+really5.4.5-1ubuntu0.2 fixed in 5.6.1+really5.4.5-1ubuntu0.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-12087 | MEDIUM4.5 | libperl5.38t64 5.38.2-3.2ubuntu0.2 fixed in 5.38.2-3.2ubuntu0.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libsframe1 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-59848 | MEDIUM4.5 | libssh-4 0.10.6-2ubuntu0.1 fixed in 0.10.6-2ubuntu0.5 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42767 | MEDIUM4.5 | libssl3t64 3.0.13-0ubuntu3.5 fixed in 3.0.13-0ubuntu3.11 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-48525 | MEDIUM4.5 | python3-jwt 2.7.0-1ubuntu0.1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-52005 | MEDIUM4.49 | git 1:2.43.0-1ubuntu7.3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-47162 | MEDIUM4.49 | vim 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.16 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-73078 | MEDIUM4.49 | vim 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.19 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-58014 | MEDIUM4.39 | libglib2.0-bin 2.80.0-6ubuntu3.8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-57432 | MEDIUM4.28 | perl 5.38.2-3.2ubuntu0.2 fixed in 5.38.2-3.2ubuntu0.4 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-57432 | MEDIUM4.28 | perl-base 5.38.2-3.2ubuntu0.2 fixed in 5.38.2-3.2ubuntu0.4 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-57432 | MEDIUM4.28 | perl-modules-5.38 5.38.2-3.2ubuntu0.2 fixed in 5.38.2-3.2ubuntu0.4 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-42250 | MEDIUM4.25 | libbz2-1.0 1.0.8-5.1build0.1 fixed in 1.0.8-5.1ubuntu0.1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc-bin 2.39-0ubuntu8.5 fixed in 2.39-0ubuntu8.8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc-bin 2.39-0ubuntu8.5 fixed in 2.39-0ubuntu8.8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc-dev-bin 2.39-0ubuntu8.5 fixed in 2.39-0ubuntu8.8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc-dev-bin 2.39-0ubuntu8.5 fixed in 2.39-0ubuntu8.8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc6 2.39-0ubuntu8.5 fixed in 2.39-0ubuntu8.8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc6 2.39-0ubuntu8.5 fixed in 2.39-0ubuntu8.8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc6-dev 2.39-0ubuntu8.5 fixed in 2.39-0ubuntu8.8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc6-dev 2.39-0ubuntu8.5 fixed in 2.39-0ubuntu8.8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libgssapi-krb5-2 1.20.1-6ubuntu2.6 fixed in 1.20.1-6ubuntu2.7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libk5crypto3 1.20.1-6ubuntu2.6 fixed in 1.20.1-6ubuntu2.7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libkrb5-3 1.20.1-6ubuntu2.6 fixed in 1.20.1-6ubuntu2.7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libkrb5support0 1.20.1-6ubuntu2.6 fixed in 1.20.1-6ubuntu2.7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-48959 | MEDIUM4.25 | libperl5.38t64 5.38.2-3.2ubuntu0.2 fixed in 5.38.2-3.2ubuntu0.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-58010 | MEDIUM4.18 | libglib2.0-bin 2.80.0-6ubuntu3.8 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-58012 | MEDIUM4.18 | libglib2.0-bin 2.80.0-6ubuntu3.8 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-58013 | MEDIUM4.18 | libglib2.0-bin 2.80.0-6ubuntu3.8 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-34982 | MEDIUM4.18 | vim 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.11 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-52859 | MEDIUM4.18 | vim 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.16 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-18374 | MEDIUM4.17 | libc-bin 2.39-0ubuntu8.5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.17 | libc-dev-bin 2.39-0ubuntu8.5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.17 | libc6 2.39-0ubuntu8.5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.17 | libc6-dev 2.39-0ubuntu8.5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-35385 | MEDIUM4.13 | openssh-client 1:9.6p1-3ubuntu13.13 fixed in 1:9.6p1-3ubuntu13.16 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-35386 | MEDIUM4.13 | openssh-client 1:9.6p1-3ubuntu13.13 fixed in 1:9.6p1-3ubuntu13.16 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-35414 | MEDIUM4.13 | openssh-client 1:9.6p1-3ubuntu13.13 fixed in 1:9.6p1-3ubuntu13.16 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-28387 | MEDIUM4.13 | openssl 3.0.13-0ubuntu3.5 fixed in 3.0.13-0ubuntu3.9 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-12216 | MEDIUM4.08 | libduktape207 2.7.0+tests-0ubuntu3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-15467 | MEDIUM4.06 | libssl3t64 3.0.13-0ubuntu3.5 fixed in 3.0.13-0ubuntu3.7 | 48.2% High Exploitation Risk | Post-Exploit |
| CVE-2025-15467 | MEDIUM4.06 | openssl 3.0.13-0ubuntu3.5 fixed in 3.0.13-0ubuntu3.7 | 48.2% High Exploitation Risk | Post-Exploit |
| CVE-2025-1376 | MEDIUM4 | libdw1t64 0.190-1.1ubuntu0.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1376 | MEDIUM4 | libelf1t64 0.190-1.1ubuntu0.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-8114 | MEDIUM4 | libssh-4 0.10.6-2ubuntu0.1 fixed in 0.10.6-2ubuntu0.2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68160 | MEDIUM4 | libssl3t64 3.0.13-0ubuntu3.5 fixed in 3.0.13-0ubuntu3.7 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-24032 | MEDIUM4 | libzstd 1.4.4-1.el8 fixed in 1.4.8+dfsg-2build1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | LOW3.98 | binutils 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11083 | LOW3.98 | binutils 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-5244 | LOW3.98 | binutils 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW3.98 | binutils 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-7545 | LOW3.98 | binutils 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-7546 | LOW3.98 | binutils 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11082 | LOW3.98 | binutils-common 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11083 | LOW3.98 | binutils-common 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-5244 | LOW3.98 | binutils-common 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW3.98 | binutils-common 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-7545 | LOW3.98 | binutils-common 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-7546 | LOW3.98 | binutils-common 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11082 | LOW3.98 | binutils-x86-64-linux-gnu 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11083 | LOW3.98 | binutils-x86-64-linux-gnu 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-5244 | LOW3.98 | binutils-x86-64-linux-gnu 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW3.98 | binutils-x86-64-linux-gnu 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-7545 | LOW3.98 | binutils-x86-64-linux-gnu 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-7546 | LOW3.98 | binutils-x86-64-linux-gnu 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-48962 | LOW3.98 | perl 5.38.2-3.2ubuntu0.2 fixed in 5.38.2-3.2ubuntu0.4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-48962 | LOW3.98 | perl-base 5.38.2-3.2ubuntu0.2 fixed in 5.38.2-3.2ubuntu0.4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-48962 | LOW3.98 | perl-modules-5.38 5.38.2-3.2ubuntu0.2 fixed in 5.38.2-3.2ubuntu0.4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2016-2568 | LOW3.98 | polkitd 124-2ubuntu1.24.04.3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-28421 | LOW3.98 | vim 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-39881 | LOW3.98 | vim 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.12 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-43961 | LOW3.98 | vim 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.15 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-51401 | LOW3.98 | vim 2:9.1.0016-1ubuntu7.8 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52858 | LOW3.98 | vim 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.16 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-52860 | LOW3.98 | vim 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.16 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-55693 | LOW3.98 | vim 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.17 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-55895 | LOW3.98 | vim 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.17 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-57455 | LOW3.98 | vim 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.17 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-57456 | LOW3.98 | vim 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.17 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-59856 | LOW3.98 | vim 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.18 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-59858 | LOW3.98 | vim 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.18 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-73072 | LOW3.98 | vim 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.19 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-19931 | LOW3.9 | curl 8.5.0-2ubuntu10.13 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-19931 | LOW3.9 | libcurl3t64-gnutls 8.5.0-2ubuntu10.13 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-19931 | LOW3.9 | libcurl4t64 8.5.0-2ubuntu10.13 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-41992 | LOW3.82 | gzip 1.12-1ubuntu3.1 fixed in 1.12-1ubuntu3.2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-32316 | LOW3.82 | jq 1.7.1-3ubuntu0.24.04.1 fixed in 1.7.1-3ubuntu0.24.04.2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-40164 | LOW3.82 | jq 1.7.1-3ubuntu0.24.04.1 fixed in 1.7.1-3ubuntu0.24.04.2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-58011 | LOW3.82 | libglib2.0-bin 2.80.0-6ubuntu3.8 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-58015 | LOW3.82 | libglib2.0-bin 2.80.0-6ubuntu3.8 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-59999 | LOW3.82 | openssh-client 1:9.6p1-3ubuntu13.13 fixed in 1:9.6p1-3ubuntu13.18 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-60000 | LOW3.82 | openssh-client 1:9.6p1-3ubuntu13.13 fixed in 1:9.6p1-3ubuntu13.18 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-63072 | LOW3.82 | openssl 3.0.13-0ubuntu3.5 fixed in 3.0.13-0ubuntu3.15 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-69421 | LOW3.82 | openssl 3.0.13-0ubuntu3.5 fixed in 3.0.13-0ubuntu3.7 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-28388 | LOW3.82 | openssl 3.0.13-0ubuntu3.5 fixed in 3.0.13-0ubuntu3.9 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-28389 | LOW3.82 | openssl 3.0.13-0ubuntu3.5 fixed in 3.0.13-0ubuntu3.9 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-28390 | LOW3.82 | openssl 3.0.13-0ubuntu3.5 fixed in 3.0.13-0ubuntu3.9 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-54874 | LOW3.82 | openssl 3.0.13-0ubuntu3.5 fixed in 3.0.13-0ubuntu3.15 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-63074 | LOW3.82 | openssl 3.0.13-0ubuntu3.5 fixed in 3.0.13-0ubuntu3.15 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-42497 | LOW3.82 | perl 5.38.2-3.2ubuntu0.2 fixed in 5.38.2-3.2ubuntu0.3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-57433 | LOW3.82 | perl 5.38.2-3.2ubuntu0.2 fixed in 5.38.2-3.2ubuntu0.4 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9538 | LOW3.82 | perl 5.38.2-3.2ubuntu0.2 fixed in 5.38.2-3.2ubuntu0.4 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42497 | LOW3.82 | perl-base 5.38.2-3.2ubuntu0.2 fixed in 5.38.2-3.2ubuntu0.3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-57433 | LOW3.82 | perl-base 5.38.2-3.2ubuntu0.2 fixed in 5.38.2-3.2ubuntu0.4 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9538 | LOW3.82 | perl-base 5.38.2-3.2ubuntu0.2 fixed in 5.38.2-3.2ubuntu0.4 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42497 | LOW3.82 | perl-modules-5.38 5.38.2-3.2ubuntu0.2 fixed in 5.38.2-3.2ubuntu0.3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-57433 | LOW3.82 | perl-modules-5.38 5.38.2-3.2ubuntu0.2 fixed in 5.38.2-3.2ubuntu0.4 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9538 | LOW3.82 | perl-modules-5.38 5.38.2-3.2ubuntu0.2 fixed in 5.38.2-3.2ubuntu0.4 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-66418 | LOW3.82 | python3-pip 24.0+dfsg-1ubuntu1.3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-66471 | LOW3.82 | python3-pip 24.0+dfsg-1ubuntu1.3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-66418 | LOW3.82 | python3-pip-whl 24.0+dfsg-1ubuntu1.3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-66471 | LOW3.82 | python3-pip-whl 24.0+dfsg-1ubuntu1.3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-26269 | LOW3.82 | vim 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.10 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-56131 | LOW3.82 | libexpat1 2.6.1-2ubuntu0.4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56131 | LOW3.82 | libexpat1-dev 2.6.1-2ubuntu0.4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69277 | LOW3.82 | libsodium23 1.0.18-1build3 fixed in 1.0.18-1ubuntu0.24.04.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-34182 | LOW3.77 | openssl 3.0.13-0ubuntu3.5 fixed in 3.0.13-0ubuntu3.11 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-69419 | LOW3.77 | openssl 3.0.13-0ubuntu3.5 fixed in 3.0.13-0ubuntu3.7 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-43895 | LOW3.74 | libjq1 1.7.1-3ubuntu0.24.04.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-33412 | LOW3.72 | vim 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.11 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-41411 | LOW3.72 | vim 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.13 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-73073 | LOW3.72 | vim 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.20 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-73076 | LOW3.72 | vim 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.19 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-73077 | LOW3.72 | vim 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.19 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-25749 | LOW3.72 | vim 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-31879 | LOW3.66 | wget 1.21.4-1ubuntu4.1 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-16118 | LOW3.62 | libglib2.0-bin 2.80.0-6ubuntu3.8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-35177 | LOW3.62 | vim 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.12 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-58471 | LOW3.62 | wget 1.21.4-1ubuntu4.1 fixed in 1.21.4-1ubuntu4.3 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-58472 | LOW3.62 | wget 1.21.4-1ubuntu4.1 fixed in 1.21.4-1ubuntu4.3 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68973 | LOW3.57 | dirmngr 2.4.4-2ubuntu17.3 fixed in 2.4.4-2ubuntu17.4 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68973 | LOW3.57 | gnupg 2.4.4-2ubuntu17.3 fixed in 2.4.4-2ubuntu17.4 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68973 | LOW3.57 | gnupg-utils 2.4.4-2ubuntu17.3 fixed in 2.4.4-2ubuntu17.4 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68973 | LOW3.57 | gpg 2.4.4-2ubuntu17.3 fixed in 2.4.4-2ubuntu17.4 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68973 | LOW3.57 | gpg-agent 2.4.4-2ubuntu17.3 fixed in 2.4.4-2ubuntu17.4 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68973 | LOW3.57 | gpgconf 2.4.4-2ubuntu17.3 fixed in 2.4.4-2ubuntu17.4 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68973 | LOW3.57 | gpgsm 2.4.4-2ubuntu17.3 fixed in 2.4.4-2ubuntu17.4 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68973 | LOW3.57 | gpgv 2.4.4-2ubuntu17.3 fixed in 2.4.4-2ubuntu17.4 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68973 | LOW3.57 | keyboxd 2.4.4-2ubuntu17.3 fixed in 2.4.4-2ubuntu17.4 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46483 | LOW3.57 | vim 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.15 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-8058 | LOW3.57 | libc-bin 2.39-0ubuntu8.5 fixed in 2.39-0ubuntu8.6 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | LOW3.57 | libc-bin 2.39-0ubuntu8.5 fixed in 2.39-0ubuntu8.9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-8058 | LOW3.57 | libc-dev-bin 2.39-0ubuntu8.5 fixed in 2.39-0ubuntu8.6 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | LOW3.57 | libc-dev-bin 2.39-0ubuntu8.5 fixed in 2.39-0ubuntu8.9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-8058 | LOW3.57 | libc6 2.39-0ubuntu8.5 fixed in 2.39-0ubuntu8.6 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | LOW3.57 | libc6 2.39-0ubuntu8.5 fixed in 2.39-0ubuntu8.9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-8058 | LOW3.57 | libc6-dev 2.39-0ubuntu8.5 fixed in 2.39-0ubuntu8.6 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | LOW3.57 | libc6-dev 2.39-0ubuntu8.5 fixed in 2.39-0ubuntu8.9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-48522 | LOW3.57 | python3-jwt 2.7.0-1ubuntu0.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31790 | LOW3.54 | openssl 3.0.13-0ubuntu3.5 fixed in 3.0.13-0ubuntu3.9 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-42010 | LOW3.53 | libgnutls30t64 3.8.3-1.1ubuntu3.4 fixed in 3.8.3-1.1ubuntu3.6 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-85498 | LOW3.5 | libpolkit-agent-1-0 124-2ubuntu1.24.04.3 fixed in 124-2ubuntu1.24.04.4 | — | Directly Exposed |
| CVE-2026-85498 | LOW3.5 | libpolkit-gobject-1-0 124-2ubuntu1.24.04.3 fixed in 124-2ubuntu1.24.04.4 | — | Directly Exposed |
| CVE-2026-6390 | LOW3.47 | nano 7.2-2ubuntu0.1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-4438 | LOW3.4 | libc-bin 2.39-0ubuntu8.5 fixed in 2.39-0ubuntu8.8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | libc-dev-bin 2.39-0ubuntu8.5 fixed in 2.39-0ubuntu8.8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | libc6 2.39-0ubuntu8.5 fixed in 2.39-0ubuntu8.8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | libc6-dev 2.39-0ubuntu8.5 fixed in 2.39-0ubuntu8.8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-9820 | LOW3.4 | libgnutls30t64 3.8.3-1.1ubuntu3.4 fixed in 3.8.3-1.1ubuntu3.5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69418 | LOW3.4 | libssl3t64 3.0.13-0ubuntu3.5 fixed in 3.0.13-0ubuntu3.7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-28419 | LOW3.37 | vim 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-9230 | LOW3.36 | openssl 3.0.13-0ubuntu3.5 fixed in 3.0.13-0ubuntu3.6 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2026-39979 | LOW3.31 | jq 1.7.1-3ubuntu0.24.04.1 fixed in 1.7.1-3ubuntu0.24.04.2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-35387 | LOW3.31 | openssh-client 1:9.6p1-3ubuntu13.13 fixed in 1:9.6p1-3ubuntu13.16 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-59998 | LOW3.31 | openssh-client 1:9.6p1-3ubuntu13.13 fixed in 1:9.6p1-3ubuntu13.18 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-60001 | LOW3.31 | openssh-client 1:9.6p1-3ubuntu13.13 fixed in 1:9.6p1-3ubuntu13.18 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-15649 | LOW3.31 | perl 5.38.2-3.2ubuntu0.2 fixed in 5.38.2-3.2ubuntu0.4 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-19487 | LOW3.31 | perl 5.38.2-3.2ubuntu0.2 fixed in 5.38.2-3.2ubuntu0.6 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15649 | LOW3.31 | perl-base 5.38.2-3.2ubuntu0.2 fixed in 5.38.2-3.2ubuntu0.4 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-19487 | LOW3.31 | perl-base 5.38.2-3.2ubuntu0.2 fixed in 5.38.2-3.2ubuntu0.6 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15649 | LOW3.31 | perl-modules-5.38 5.38.2-3.2ubuntu0.2 fixed in 5.38.2-3.2ubuntu0.4 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-19487 | LOW3.31 | perl-modules-5.38 5.38.2-3.2ubuntu0.2 fixed in 5.38.2-3.2ubuntu0.6 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-58469 | LOW3.31 | wget 1.21.4-1ubuntu4.1 fixed in 1.21.4-1ubuntu4.3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13346 | LOW3.31 | pip 24.0 fixed in 26.2.0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-59846 | LOW3.31 | libssh-4 0.10.6-2ubuntu0.1 fixed in 0.10.6-2ubuntu0.5 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2017-13716 | LOW3.3 | binutils 2.42-4ubuntu2.5 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2017-13716 | LOW3.3 | binutils-common 2.42-4ubuntu2.5 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2017-13716 | LOW3.3 | binutils-x86-64-linux-gnu 2.42-4ubuntu2.5 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2019-20633 | LOW3.3 | patch 2.7.6-7build3 No fix yet | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-5958 | LOW3.21 | sed 4.9-2build1 fixed in 4.9-2ubuntu0.24.04.1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-42766 | LOW3.18 | openssl 3.0.13-0ubuntu3.5 fixed in 3.0.13-0ubuntu3.11 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1152 | LOW3.15 | libbinutils 2.42-4ubuntu2.5 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libctf-nobfd0 2.42-4ubuntu2.5 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libctf0 2.42-4ubuntu2.5 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-41080 | LOW3.15 | libexpat1 2.6.1-2ubuntu0.4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-41080 | LOW3.15 | libexpat1-dev 2.6.1-2ubuntu0.4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3832 | LOW3.15 | libgnutls30t64 3.8.3-1.1ubuntu3.4 fixed in 3.8.3-1.1ubuntu3.6 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-5419 | LOW3.15 | libgnutls30t64 3.8.3-1.1ubuntu3.4 fixed in 3.8.3-1.1ubuntu3.6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libgprofng0 2.42-4ubuntu2.5 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libsframe1 2.42-4ubuntu2.5 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-45446 | LOW3.15 | libssl3t64 3.0.13-0ubuntu3.5 fixed in 3.0.13-0ubuntu3.11 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-75803 | LOW3.15 | libssl3t64 3.0.13-0ubuntu3.5 fixed in 3.0.13-0ubuntu3.15 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-39956 | LOW3.11 | jq 1.7.1-3ubuntu0.24.04.1 fixed in 1.7.1-3ubuntu0.24.04.2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-59890 | LOW3.11 | setuptools 80.10.2 fixed in 83.0.0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-69420 | LOW3.01 | openssl 3.0.13-0ubuntu3.5 fixed in 3.0.13-0ubuntu3.7 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-22796 | LOW3.01 | openssl 3.0.13-0ubuntu3.5 fixed in 3.0.13-0ubuntu3.7 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-42770 | LOW3.01 | openssl 3.0.13-0ubuntu3.5 fixed in 3.0.13-0ubuntu3.11 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-9076 | LOW3.01 | openssl 3.0.13-0ubuntu3.5 fixed in 3.0.13-0ubuntu3.11 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-15146 | LOW3.01 | wget 1.21.4-1ubuntu4.1 fixed in 1.21.4-1ubuntu4.4 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-8376 | LOW3 | libperl5.38t64 5.38.2-3.2ubuntu0.2 fixed in 5.38.2-3.2ubuntu0.3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-31789 | LOW3 | libssl3t64 3.0.13-0ubuntu3.5 fixed in 3.0.13-0ubuntu3.9 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-31789 | LOW3 | openssl 3.0.13-0ubuntu3.5 fixed in 3.0.13-0ubuntu3.9 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-8376 | LOW3 | perl 5.38.2-3.2ubuntu0.2 fixed in 5.38.2-3.2ubuntu0.3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8376 | LOW3 | perl-base 5.38.2-3.2ubuntu0.2 fixed in 5.38.2-3.2ubuntu0.3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8376 | LOW3 | perl-modules-5.38 5.38.2-3.2ubuntu0.2 fixed in 5.38.2-3.2ubuntu0.3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-34180 | LOW3 | openssl 3.0.13-0ubuntu3.5 fixed in 3.0.13-0ubuntu3.11 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-6357 | LOW2.96 | pip 24.0 fixed in 26.1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45447 | LOW2.92 | libssl3t64 3.0.13-0ubuntu3.5 fixed in 3.0.13-0ubuntu3.11 | 3.6% Low-Moderate Risk | Post-Exploit |
| CVE-2026-45447 | LOW2.92 | openssl 3.0.13-0ubuntu3.5 fixed in 3.0.13-0ubuntu3.11 | 3.6% Low-Moderate Risk | Post-Exploit |
| CVE-2026-15534 | LOW2.91 | perl 5.38.2-3.2ubuntu0.2 fixed in 5.38.2-3.2ubuntu0.6 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-15534 | LOW2.91 | perl-base 5.38.2-3.2ubuntu0.2 fixed in 5.38.2-3.2ubuntu0.6 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-15534 | LOW2.91 | perl-modules-5.38 5.38.2-3.2ubuntu0.2 fixed in 5.38.2-3.2ubuntu0.6 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-60002 | LOW2.87 | openssh-client 1:9.6p1-3ubuntu13.13 fixed in 1:9.6p1-3ubuntu13.18 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-73282 | LOW2.86 | openssh-client 1:9.6p1-3ubuntu13.13 fixed in 1:9.6p1-3ubuntu13.19 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35195 | LOW2.86 | python3-pip 24.0+dfsg-1ubuntu1.3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-35195 | LOW2.86 | python3-pip-whl 24.0+dfsg-1ubuntu1.3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-45582 | LOW2.86 | tar 1.35+dfsg-3build1 fixed in 1.35+dfsg-3ubuntu0.2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-28417 | LOW2.81 | vim 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.10 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2025-11412 | LOW2.8 | binutils 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.8 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11413 | LOW2.8 | binutils 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.8 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11414 | LOW2.8 | binutils 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.8 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11494 | LOW2.8 | binutils 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.8 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11839 | LOW2.8 | binutils 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.7 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11840 | LOW2.8 | binutils 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.7 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-3198 | LOW2.8 | binutils 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | binutils 2.42-4ubuntu2.5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11412 | LOW2.8 | binutils-common 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.8 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11413 | LOW2.8 | binutils-common 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.8 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11414 | LOW2.8 | binutils-common 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.8 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11494 | LOW2.8 | binutils-common 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.8 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11839 | LOW2.8 | binutils-common 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.7 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11840 | LOW2.8 | binutils-common 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.7 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-3198 | LOW2.8 | binutils-common 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | binutils-common 2.42-4ubuntu2.5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11412 | LOW2.8 | binutils-x86-64-linux-gnu 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.8 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11413 | LOW2.8 | binutils-x86-64-linux-gnu 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.8 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11414 | LOW2.8 | binutils-x86-64-linux-gnu 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.8 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11494 | LOW2.8 | binutils-x86-64-linux-gnu 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.8 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11839 | LOW2.8 | binutils-x86-64-linux-gnu 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.7 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11840 | LOW2.8 | binutils-x86-64-linux-gnu 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.7 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-3198 | LOW2.8 | binutils-x86-64-linux-gnu 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | binutils-x86-64-linux-gnu 2.42-4ubuntu2.5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-33947 | LOW2.8 | jq 1.7.1-3ubuntu0.24.04.1 fixed in 1.7.1-3ubuntu0.24.04.2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-41256 | LOW2.8 | jq 1.7.1-3ubuntu0.24.04.1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-41257 | LOW2.8 | jq 1.7.1-3ubuntu0.24.04.1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43896 | LOW2.8 | jq 1.7.1-3ubuntu0.24.04.1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-44777 | LOW2.8 | jq 1.7.1-3ubuntu0.24.04.1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6843 | LOW2.8 | nano 7.2-2ubuntu0.1 fixed in 7.2-2ubuntu0.2 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-22795 | LOW2.8 | openssl 3.0.13-0ubuntu3.5 fixed in 3.0.13-0ubuntu3.7 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-7383 | LOW2.8 | openssl 3.0.13-0ubuntu3.5 fixed in 3.0.13-0ubuntu3.11 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2021-45261 | LOW2.8 | patch 2.7.6-7build3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-56288 | LOW2.8 | patch 2.7.6-7build3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-56289 | LOW2.8 | patch 2.7.6-7build3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-24049 | LOW2.8 | python3-wheel 0.42.0-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5704 | LOW2.8 | tar 1.35+dfsg-3build1 fixed in 1.35+dfsg-3ubuntu0.4 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-28418 | LOW2.8 | vim 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-32249 | LOW2.8 | vim 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.11 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45130 | LOW2.8 | vim 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.14 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-51400 | LOW2.8 | vim 2:9.1.0016-1ubuntu7.8 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-55892 | LOW2.8 | vim 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.17 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-59857 | LOW2.8 | vim 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.18 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-73074 | LOW2.8 | vim 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.19 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-8643 | LOW2.8 | pip 24.0 fixed in 26.1.2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW2.8 | libbinutils 2.42-4ubuntu2.5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libbinutils 2.42-4ubuntu2.5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libbinutils 2.42-4ubuntu2.5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libbinutils 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libctf-nobfd0 2.42-4ubuntu2.5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libctf-nobfd0 2.42-4ubuntu2.5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libctf-nobfd0 2.42-4ubuntu2.5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libctf-nobfd0 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libctf0 2.42-4ubuntu2.5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libctf0 2.42-4ubuntu2.5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libctf0 2.42-4ubuntu2.5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libctf0 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libgprofng0 2.42-4ubuntu2.5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libgprofng0 2.42-4ubuntu2.5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libgprofng0 2.42-4ubuntu2.5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libgprofng0 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-0987 | LOW2.8 | libpackagekit-glib2-18 1.2.8-2ubuntu1.5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-0217 | LOW2.8 | libpackagekit-glib2-18 1.2.8-2ubuntu1.5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libsframe1 2.42-4ubuntu2.5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libsframe1 2.42-4ubuntu2.5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libsframe1 2.42-4ubuntu2.5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libsframe1 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-0965 | LOW2.8 | libssh-4 0.10.6-2ubuntu0.1 fixed in 0.10.6-2ubuntu0.3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libsystemd-shared 255.4-1ubuntu8.17 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libsystemd0 255.4-1ubuntu8.17 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libudev1 255.4-1ubuntu8.17 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-58016 | LOW2.78 | libglib2.0-0t64 2.80.0-6ubuntu3.8 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-33845 | LOW2.78 | libgnutls30t64 3.8.3-1.1ubuntu3.4 fixed in 3.8.3-1.1ubuntu3.6 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-13221 | LOW2.78 | libperl5.38t64 5.38.2-3.2ubuntu0.2 fixed in 5.38.2-3.2ubuntu0.4 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42496 | LOW2.78 | libperl5.38t64 5.38.2-3.2ubuntu0.2 fixed in 5.38.2-3.2ubuntu0.3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-45445 | LOW2.78 | libssl3t64 3.0.13-0ubuntu3.5 fixed in 3.0.13-0ubuntu3.11 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-13221 | LOW2.78 | perl 5.38.2-3.2ubuntu0.2 fixed in 5.38.2-3.2ubuntu0.4 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13221 | LOW2.78 | perl-base 5.38.2-3.2ubuntu0.2 fixed in 5.38.2-3.2ubuntu0.4 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-59995 | LOW2.75 | openssh-client 1:9.6p1-3ubuntu13.13 fixed in 1:9.6p1-3ubuntu13.18 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-59996 | LOW2.75 | openssh-client 1:9.6p1-3ubuntu13.13 fixed in 1:9.6p1-3ubuntu13.18 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-59997 | LOW2.75 | openssh-client 1:9.6p1-3ubuntu13.13 fixed in 1:9.6p1-3ubuntu13.18 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-73283 | LOW2.75 | openssh-client 1:9.6p1-3ubuntu13.13 fixed in 1:9.6p1-3ubuntu13.19 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-33846 | LOW2.7 | libgnutls30t64 3.8.3-1.1ubuntu3.4 fixed in 3.8.3-1.1ubuntu3.6 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-42009 | LOW2.7 | libgnutls30t64 3.8.3-1.1ubuntu3.4 fixed in 3.8.3-1.1ubuntu3.6 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-63076 | LOW2.7 | libssl3t64 3.0.13-0ubuntu3.5 fixed in 3.0.13-0ubuntu3.15 | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1147 | LOW2.7 | binutils 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1147 | LOW2.7 | binutils-common 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1147 | LOW2.7 | binutils-x86-64-linux-gnu 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-53910 | LOW2.7 | diffutils 1:3.10-1build1 fixed in 1:3.10-1ubuntu0.1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-33948 | LOW2.7 | jq 1.7.1-3ubuntu0.24.04.1 fixed in 1.7.1-3ubuntu0.24.04.2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-15588 | LOW2.7 | libglib2.0-bin 2.80.0-6ubuntu3.8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-61984 | LOW2.7 | openssh-client 1:9.6p1-3ubuntu13.13 fixed in 1:9.6p1-3ubuntu13.15 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-61985 | LOW2.7 | openssh-client 1:9.6p1-3ubuntu13.13 fixed in 1:9.6p1-3ubuntu13.15 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-42767 | LOW2.7 | openssl 3.0.13-0ubuntu3.5 fixed in 3.0.13-0ubuntu3.11 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-12087 | LOW2.7 | perl 5.38.2-3.2ubuntu0.2 fixed in 5.38.2-3.2ubuntu0.4 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-12087 | LOW2.7 | perl-base 5.38.2-3.2ubuntu0.2 fixed in 5.38.2-3.2ubuntu0.4 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-12087 | LOW2.7 | perl-modules-5.38 5.38.2-3.2ubuntu0.2 fixed in 5.38.2-3.2ubuntu0.4 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-44656 | LOW2.7 | vim 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.14 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-47167 | LOW2.7 | vim 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.16 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-58470 | LOW2.7 | wget 1.21.4-1ubuntu4.1 fixed in 1.21.4-1ubuntu4.3 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-34743 | LOW2.7 | xz-utils 5.6.1+really5.4.5-1ubuntu0.2 fixed in 5.6.1+really5.4.5-1ubuntu0.3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-8869 | LOW2.7 | pip 24.0 fixed in 25.3 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-58014 | LOW2.63 | libglib2.0-0t64 2.80.0-6ubuntu3.8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-1148 | LOW2.63 | libbinutils 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW2.63 | libctf-nobfd0 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW2.63 | libctf0 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW2.63 | libgprofng0 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW2.63 | libsframe1 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-0968 | LOW2.63 | libssh-4 0.10.6-2ubuntu0.1 fixed in 0.10.6-2ubuntu0.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-8277 | LOW2.63 | libssh-4 0.10.6-2ubuntu0.1 fixed in 0.10.6-2ubuntu0.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-74860 | LOW2.6 | libxml2 2.9.14+dfsg-1.3ubuntu3.8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-57432 | LOW2.57 | libperl5.38t64 5.38.2-3.2ubuntu0.2 fixed in 5.38.2-3.2ubuntu0.4 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-42250 | LOW2.55 | bzip2 1.0.8-5.1build0.1 fixed in 1.0.8-5.1ubuntu0.1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-48959 | LOW2.55 | perl 5.38.2-3.2ubuntu0.2 fixed in 5.38.2-3.2ubuntu0.4 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-48959 | LOW2.55 | perl-base 5.38.2-3.2ubuntu0.2 fixed in 5.38.2-3.2ubuntu0.4 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-48959 | LOW2.55 | perl-modules-5.38 5.38.2-3.2ubuntu0.2 fixed in 5.38.2-3.2ubuntu0.4 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-3219 | LOW2.55 | pip 24.0 fixed in 26.1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-58010 | LOW2.51 | libglib2.0-0t64 2.80.0-6ubuntu3.8 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-42013 | LOW2.51 | libgnutls30t64 3.8.3-1.1ubuntu3.4 fixed in 3.8.3-1.1ubuntu3.6 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-5260 | LOW2.51 | libgnutls30t64 3.8.3-1.1ubuntu3.4 fixed in 3.8.3-1.1ubuntu3.6 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-0966 | LOW2.51 | libssh-4 0.10.6-2ubuntu0.1 fixed in 0.10.6-2ubuntu0.3 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-41991 | LOW2.4 | gzip 1.12-1ubuntu3.1 fixed in 1.12-1ubuntu3.2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68160 | LOW2.4 | openssl 3.0.13-0ubuntu3.5 fixed in 3.0.13-0ubuntu3.7 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-57452 | LOW2.4 | vim 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.17 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69644 | LOW2.38 | libbinutils 2.42-4ubuntu2.5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libbinutils 2.42-4ubuntu2.5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libbinutils 2.42-4ubuntu2.5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW2.38 | libctf-nobfd0 2.42-4ubuntu2.5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libctf-nobfd0 2.42-4ubuntu2.5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libctf-nobfd0 2.42-4ubuntu2.5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW2.38 | libctf0 2.42-4ubuntu2.5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libctf0 2.42-4ubuntu2.5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libctf0 2.42-4ubuntu2.5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW2.38 | libgprofng0 2.42-4ubuntu2.5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libgprofng0 2.42-4ubuntu2.5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libgprofng0 2.42-4ubuntu2.5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW2.38 | libsframe1 2.42-4ubuntu2.5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libsframe1 2.42-4ubuntu2.5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libsframe1 2.42-4ubuntu2.5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5278 | LOW2.24 | coreutils 9.4-3ubuntu6 fixed in 9.4-3ubuntu6.3 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-43895 | LOW2.24 | jq 1.7.1-3ubuntu0.24.04.1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-18477 | LOW2.24 | tar 1.35+dfsg-3build1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-18508 | LOW2.24 | tar 1.35+dfsg-3build1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-28420 | LOW2.24 | vim 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-42307 | LOW2.24 | vim 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.14 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-85498 | LOW2.1 | polkitd 124-2ubuntu1.24.04.3 fixed in 124-2ubuntu1.24.04.4 | — | Post-Exploit |
| CVE-2025-53905 | LOW2.09 | vim 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.9 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-53906 | LOW2.09 | vim 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.9 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-69418 | LOW2.04 | openssl 3.0.13-0ubuntu3.5 fixed in 3.0.13-0ubuntu3.7 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-1703 | LOW1.99 | python3-pip 24.0+dfsg-1ubuntu1.3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-1703 | LOW1.99 | python3-pip-whl 24.0+dfsg-1ubuntu1.3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-1703 | LOW1.99 | pip 24.0 fixed in 26.0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils 2.42-4ubuntu2.5 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils-common 2.42-4ubuntu2.5 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils-x86-64-linux-gnu 2.42-4ubuntu2.5 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-18924 | LOW1.89 | curl 8.5.0-2ubuntu10.13 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-18924 | LOW1.89 | libcurl3t64-gnutls 8.5.0-2ubuntu10.13 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-18924 | LOW1.89 | libcurl4t64 8.5.0-2ubuntu10.13 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-45446 | LOW1.89 | openssl 3.0.13-0ubuntu3.5 fixed in 3.0.13-0ubuntu3.11 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-75803 | LOW1.89 | openssl 3.0.13-0ubuntu3.5 fixed in 3.0.13-0ubuntu3.15 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56433 | LOW1.84 | passwd 1:4.13+dfsg1-4ubuntu3.2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-73281 | LOW1.78 | openssh-client 1:9.6p1-3ubuntu13.13 fixed in 1:9.6p1-3ubuntu13.19 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.68 | binutils 2.42-4ubuntu2.5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.68 | binutils 2.42-4ubuntu2.5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils 2.42-4ubuntu2.5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8225 | LOW1.68 | binutils 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.68 | binutils-common 2.42-4ubuntu2.5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.68 | binutils-common 2.42-4ubuntu2.5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils-common 2.42-4ubuntu2.5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8225 | LOW1.68 | binutils-common 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.68 | binutils-x86-64-linux-gnu 2.42-4ubuntu2.5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.68 | binutils-x86-64-linux-gnu 2.42-4ubuntu2.5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils-x86-64-linux-gnu 2.42-4ubuntu2.5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8225 | LOW1.68 | binutils-x86-64-linux-gnu 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-0987 | LOW1.68 | packagekit 1.2.8-2ubuntu1.5 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-0217 | LOW1.68 | packagekit 1.2.8-2ubuntu1.5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-40228 | LOW1.68 | systemd-sysv 255.4-1ubuntu8.17 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-73071 | LOW1.68 | vim 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.19 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1148 | LOW1.58 | binutils 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1148 | LOW1.58 | binutils-common 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1148 | LOW1.58 | binutils-x86-64-linux-gnu 2.42-4ubuntu2.5 fixed in 2.42-4ubuntu2.6 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW1.48 | dirmngr 2.4.4-2ubuntu17.3 fixed in 2.4.4-2ubuntu17.6 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW1.48 | gnupg 2.4.4-2ubuntu17.3 fixed in 2.4.4-2ubuntu17.6 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW1.48 | gnupg-utils 2.4.4-2ubuntu17.3 fixed in 2.4.4-2ubuntu17.6 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW1.48 | gpg 2.4.4-2ubuntu17.3 fixed in 2.4.4-2ubuntu17.6 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW1.48 | gpg-agent 2.4.4-2ubuntu17.3 fixed in 2.4.4-2ubuntu17.6 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW1.48 | gpgconf 2.4.4-2ubuntu17.3 fixed in 2.4.4-2ubuntu17.6 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW1.48 | gpgsm 2.4.4-2ubuntu17.3 fixed in 2.4.4-2ubuntu17.6 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW1.48 | gpgv 2.4.4-2ubuntu17.3 fixed in 2.4.4-2ubuntu17.6 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW1.48 | keyboxd 2.4.4-2ubuntu17.3 fixed in 2.4.4-2ubuntu17.6 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69644 | LOW1.43 | binutils 2.42-4ubuntu2.5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.43 | binutils 2.42-4ubuntu2.5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.43 | binutils 2.42-4ubuntu2.5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69644 | LOW1.43 | binutils-common 2.42-4ubuntu2.5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.43 | binutils-common 2.42-4ubuntu2.5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.43 | binutils-common 2.42-4ubuntu2.5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69644 | LOW1.43 | binutils-x86-64-linux-gnu 2.42-4ubuntu2.5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.43 | binutils-x86-64-linux-gnu 2.42-4ubuntu2.5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.43 | binutils-x86-64-linux-gnu 2.42-4ubuntu2.5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6842 | LOW1.27 | nano 7.2-2ubuntu0.1 fixed in 7.2-2ubuntu0.2 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-35388 | LOW1.27 | openssh-client 1:9.6p1-3ubuntu13.13 fixed in 1:9.6p1-3ubuntu13.16 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-28422 | LOW1.12 | vim 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.10 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68121 | NONE0 | stdlib v1.23.4 fixed in 1.24.13, 1.25.7, 1.26.0-rc.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-23112 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-111.111 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-58016 | NONE0 | gir1.2-glib-2.0 2.80.0-6ubuntu3.8 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58016 | NONE0 | libglib2.0-data 2.80.0-6ubuntu3.8 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-68809 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68457 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-52005 | NONE0 | git-man 1:2.43.0-1ubuntu7.3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43037 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-23395 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52924 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-137.137 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64562 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64268 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-68159 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-68480 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72130 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-74516 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74588 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74669 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74744 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74752 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80726 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-47162 | NONE0 | vim-common 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.16 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-73078 | NONE0 | vim-common 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.19 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-47162 | NONE0 | vim-runtime 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.16 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-73078 | NONE0 | vim-runtime 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.19 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64018 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-58014 | NONE0 | gir1.2-glib-2.0 2.80.0-6ubuntu3.8 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-58014 | NONE0 | libglib2.0-data 2.80.0-6ubuntu3.8 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-10263 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-63797 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80586 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-58010 | NONE0 | gir1.2-glib-2.0 2.80.0-6ubuntu3.8 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58012 | NONE0 | gir1.2-glib-2.0 2.80.0-6ubuntu3.8 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58013 | NONE0 | gir1.2-glib-2.0 2.80.0-6ubuntu3.8 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58010 | NONE0 | libglib2.0-data 2.80.0-6ubuntu3.8 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58012 | NONE0 | libglib2.0-data 2.80.0-6ubuntu3.8 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58013 | NONE0 | libglib2.0-data 2.80.0-6ubuntu3.8 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31788 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-34982 | NONE0 | vim-common 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.11 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-52859 | NONE0 | vim-common 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.16 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-34982 | NONE0 | vim-runtime 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.11 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-52859 | NONE0 | vim-runtime 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.16 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39821 | NONE0 | stdlib v1.23.4 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-68263 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-68315 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-68799 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43114 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-72129 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89530 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89653 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89690 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43112 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-56858 | NONE0 | stdlib v1.23.4 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74509 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43133 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | libncurses6 6.4+20240113-1ubuntu2 fixed in 6.4+20240113-1ubuntu2.1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | libncursesw6 6.4+20240113-1ubuntu2 fixed in 6.4+20240113-1ubuntu2.1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | libtinfo6 6.4+20240113-1ubuntu2 fixed in 6.4+20240113-1ubuntu2.1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-37777 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-38490 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-38724 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-71068 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-23216 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31402 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-64564 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2025-21968 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22040 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-86.87 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-22041 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-86.87 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-22056 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-86.87 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-22068 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-86.87 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23142 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37738 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37778 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2025-37823 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37839 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37849 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37854 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37869 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37899 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-101.101 | 1.0% Theoretical Threat | Not Applicable |
| CVE-2025-37913 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37914 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37921 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37924 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 20.7% High Exploitation Risk | Not Applicable |
| CVE-2025-37926 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-37943 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37944 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37952 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-38024 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38068 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38079 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38087 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38129 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38146 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-38180 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38187 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38211 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-38212 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38226 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38230 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38236 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-38248 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-38257 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38323 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38348 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38349 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38377 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38401 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38416 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38425 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38437 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-38464 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38494 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38550 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38552 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-38563 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-38572 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38593 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38627 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38666 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-90.91 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38685 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38697 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38703 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38707 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38730 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39730 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39743 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39790 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39824 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39828 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39841 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-39849 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39860 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39863 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39864 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39866 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-39881 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39952 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39967 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40149 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40277 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68817 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-71073 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71082 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71089 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71123 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71162 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23001 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23025 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23074 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-107.107 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23111 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-107.107 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-23171 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23208 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23209 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23226 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-23227 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23231 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-111.111 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-23268 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23378 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23410 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23411 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23412 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23413 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23428 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31431 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 99.9% Actively Exploited | Not Applicable |
| CVE-2026-31474 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31488 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31532 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31566 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31627 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31678 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31709 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31720 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31729 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31759 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43049 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43059 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43120 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43128 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43206 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43284 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-124.124 | 93.2% Actively Exploited | Not Applicable |
| CVE-2026-43329 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43378 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43499 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-43500 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-124.124 | 92.9% Actively Exploited | Not Applicable |
| CVE-2026-45891 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46274 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46300 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-124.124 | 9.3% Low-Moderate Risk | Not Applicable |
| CVE-2026-46323 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-124.124 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46333 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-124.124 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2026-53130 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53148 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53262 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53359 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-137.137 | 1.0% Theoretical Threat | Not Applicable |
| CVE-2026-53362 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64531 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-138.138 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80714 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2013-7445 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 2.8% Low-Moderate Risk | Not Applicable |
| CVE-2020-14356 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2022-3238 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50090 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50240 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-0030 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-26242 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54187 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-27022 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38581 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-40954 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-44932 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44951 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44964 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46820 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46833 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53098 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21687 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21883 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21914 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21919 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21927 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-21929 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21945 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-21966 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21967 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-21969 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21979 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22020 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-86.87 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22022 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37763 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37789 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37796 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37891 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37903 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37928 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-37947 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-37979 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38022 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38052 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-38157 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38182 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38201 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38227 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-88.89 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38279 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38338 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38369 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38389 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38396 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38403 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38471 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-38476 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-38500 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-85.85 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38512 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38568 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38574 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-38579 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38618 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-85.85 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38688 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38718 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38729 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38734 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-39691 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39766 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39776 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39836 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39873 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39955 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39957 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40047 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40258 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-68808 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71078 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71091 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71238 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23010 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23078 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23083 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23089 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23098 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23193 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-23245 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23281 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23343 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23408 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23447 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23448 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31452 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31578 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31581 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31582 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31696 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43007 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43196 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43250 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45839 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45902 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45914 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45916 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45920 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45936 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45938 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45946 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45984 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45989 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45996 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45998 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-124.124 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46004 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46047 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46068 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46069 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46075 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46084 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46121 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46122 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46136 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46163 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46174 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46180 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46189 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46219 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46234 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46241 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46243 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52912 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52923 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52933 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52943 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52962 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52969 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52992 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53004 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53109 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53136 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53137 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53143 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53294 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53296 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53361 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53366 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63794 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63804 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63829 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64085 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64099 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64225 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64242 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64246 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64270 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64271 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64273 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64274 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64305 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64329 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64330 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64340 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64341 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64342 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64343 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64344 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64346 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64348 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64352 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64362 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64363 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64365 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64377 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64381 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64421 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64424 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64433 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64446 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64530 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64556 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64565 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64582 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64600 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68143 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68290 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68398 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72042 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72052 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72098 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72255 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74480 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-74518 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74581 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74582 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74583 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74746 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80536 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2017-13165 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2018-12930 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-12931 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-19378 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2019-19814 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 3.3% Low-Moderate Risk | Not Applicable |
| CVE-2021-26934 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-33053 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-50217 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-21915 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21928 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21934 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21991 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22083 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-86.87 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22126 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23133 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-23158 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37786 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37803 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37810 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37817 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37819 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37822 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37840 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37861 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37885 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37892 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37916 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37923 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37927 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37957 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37991 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38013 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38019 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38069 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38077 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38101 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38109 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38117 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38118 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-87.88 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38131 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38154 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38183 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38198 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38206 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38239 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38245 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38250 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38259 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38280 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38289 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38295 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38298 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38313 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38346 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38361 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38375 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38385 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38415 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38421 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38422 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38428 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38443 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38456 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38459 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38485 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38488 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-38527 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-38533 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-38535 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38538 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38548 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38555 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38565 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38582 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38584 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38585 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38595 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38653 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38676 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-38699 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38702 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38704 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38708 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-38722 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39686 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39689 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39701 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39711 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39738 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39783 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39788 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39797 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39810 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39823 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39835 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39854 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39859 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39861 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39862 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39870 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39871 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39877 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39880 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-39896 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39911 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39913 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39944 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39945 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39951 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39958 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40014 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40114 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-86.87 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-71071 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71075 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71086 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71122 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71137 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71143 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71152 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71220 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22980 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23068 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23073 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23156 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23221 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23233 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23234 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23262 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23319 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23359 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23361 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23387 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31399 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31455 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31485 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31489 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31493 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31500 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31506 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31527 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31530 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31576 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31580 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31583 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31686 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31702 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31715 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31730 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31731 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31747 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31748 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43015 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43020 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43027 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43150 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43205 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43328 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43426 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43458 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45866 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45867 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45879 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45882 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45885 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46246 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46267 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46285 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46294 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46301 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53059 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53089 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53097 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53098 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53112 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53115 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53117 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53118 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53120 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53129 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53156 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53157 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53195 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53272 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64103 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64239 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64245 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64249 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64272 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-base 6.4+20240113-1ubuntu2 fixed in 6.4+20240113-1ubuntu2.1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-bin 6.4+20240113-1ubuntu2 fixed in 6.4+20240113-1ubuntu2.1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-28417 | NONE0 | vim-common 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.10 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-28421 | NONE0 | vim-common 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.10 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-39881 | NONE0 | vim-common 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.12 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-43961 | NONE0 | vim-common 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.15 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-51401 | NONE0 | vim-common 2:9.1.0016-1ubuntu7.8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52858 | NONE0 | vim-common 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.16 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52860 | NONE0 | vim-common 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.16 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-55693 | NONE0 | vim-common 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.17 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-55895 | NONE0 | vim-common 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.17 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-57455 | NONE0 | vim-common 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.17 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-57456 | NONE0 | vim-common 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.17 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-59856 | NONE0 | vim-common 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.18 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-59858 | NONE0 | vim-common 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.18 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-73072 | NONE0 | vim-common 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.19 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-28417 | NONE0 | vim-runtime 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.10 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-28421 | NONE0 | vim-runtime 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.10 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-39881 | NONE0 | vim-runtime 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.12 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-43961 | NONE0 | vim-runtime 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.15 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-51401 | NONE0 | vim-runtime 2:9.1.0016-1ubuntu7.8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52858 | NONE0 | vim-runtime 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.16 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52860 | NONE0 | vim-runtime 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.16 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-55693 | NONE0 | vim-runtime 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.17 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-55895 | NONE0 | vim-runtime 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.17 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-57455 | NONE0 | vim-runtime 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.17 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-57456 | NONE0 | vim-runtime 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.17 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-59856 | NONE0 | vim-runtime 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.18 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-59858 | NONE0 | vim-runtime 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.18 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-73072 | NONE0 | vim-runtime 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.19 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-39822 | NONE0 | stdlib v1.23.4 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80590 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89542 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-39971 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63869 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-58011 | NONE0 | gir1.2-glib-2.0 2.80.0-6ubuntu3.8 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58015 | NONE0 | gir1.2-glib-2.0 2.80.0-6ubuntu3.8 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-58011 | NONE0 | libglib2.0-data 2.80.0-6ubuntu3.8 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58015 | NONE0 | libglib2.0-data 2.80.0-6ubuntu3.8 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-43501 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-38566 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-39982 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31669 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43186 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-46195 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-53071 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53266 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64396 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-0400 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2022-25836 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-36347 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38501 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2025-40210 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40240 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-68255 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-68256 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-68349 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-68369 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-68806 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-22998 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-43110 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43190 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68136 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89465 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89650 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89669 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2019-20426 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2025-39973 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-26269 | NONE0 | vim-common 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.10 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-26269 | NONE0 | vim-runtime 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.10 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-61726 | NONE0 | stdlib v1.23.4 fixed in 1.24.12, 1.25.6 | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2025-61729 | NONE0 | stdlib v1.23.4 fixed in 1.24.11, 1.25.5 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-25679 | NONE0 | stdlib v1.23.4 fixed in 1.25.8, 1.26.1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-27145 | NONE0 | stdlib v1.23.4 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-32280 | NONE0 | stdlib v1.23.4 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-32281 | NONE0 | stdlib v1.23.4 fixed in 1.25.9, 1.26.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-32283 | NONE0 | stdlib v1.23.4 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-33811 | NONE0 | stdlib v1.23.4 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-33814 | NONE0 | stdlib v1.23.4 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-33818 | NONE0 | stdlib v1.23.4 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-39820 | NONE0 | stdlib v1.23.4 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-39836 | NONE0 | stdlib v1.23.4 fixed in 1.25.10, 1.26.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-42499 | NONE0 | stdlib v1.23.4 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-42504 | NONE0 | stdlib v1.23.4 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-56853 | NONE0 | stdlib v1.23.4 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-56859 | NONE0 | stdlib v1.23.4 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-56860 | NONE0 | stdlib v1.23.4 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-56862 | NONE0 | stdlib v1.23.4 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-58183 | NONE0 | stdlib v1.23.4 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-61728 | NONE0 | stdlib v1.23.4 fixed in 1.24.12, 1.25.6 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-10963 | NONE0 | libpam-modules 1.5.3-5ubuntu5.4 fixed in 1.5.3-5ubuntu5.5 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-10963 | NONE0 | libpam-modules-bin 1.5.3-5ubuntu5.4 fixed in 1.5.3-5ubuntu5.5 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-10963 | NONE0 | libpam-runtime 1.5.3-5ubuntu5.4 fixed in 1.5.3-5ubuntu5.5 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-10963 | NONE0 | libpam0g 1.5.3-5ubuntu5.4 fixed in 1.5.3-5ubuntu5.5 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2025-40170 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43117 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74631 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89480 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89481 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89652 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89691 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2019-14899 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-43038 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-39981 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40176 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40269 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68741 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31607 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43074 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43078 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63974 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-68121 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40141 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40294 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40304 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68800 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23243 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46099 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46244 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64563 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68166 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68278 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68294 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68426 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-72099 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-72243 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74574 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74580 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80863 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43248 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53202 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-33412 | NONE0 | vim-common 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.11 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-41411 | NONE0 | vim-common 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.13 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-73073 | NONE0 | vim-common 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.20 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-73076 | NONE0 | vim-common 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.19 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-73077 | NONE0 | vim-common 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.19 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-25749 | NONE0 | vim-common 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.10 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-33412 | NONE0 | vim-runtime 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.11 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-41411 | NONE0 | vim-runtime 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.13 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-73073 | NONE0 | vim-runtime 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.20 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-73076 | NONE0 | vim-runtime 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.19 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-73077 | NONE0 | vim-runtime 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.19 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-25749 | NONE0 | vim-runtime 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.10 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74556 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-16118 | NONE0 | gir1.2-glib-2.0 2.80.0-6ubuntu3.8 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-16118 | NONE0 | libglib2.0-data 2.80.0-6ubuntu3.8 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46135 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52989 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-22121 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38714 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38715 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39735 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-86.87 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-39806 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39943 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40064 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22984 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-23455 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2026-31613 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46259 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68198 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74510 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50551 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53034 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-86.87 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-14040 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-53216 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58015 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21920 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21946 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-21985 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22038 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-86.87 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-22039 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-86.87 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2025-22079 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-86.87 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22104 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22107 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23156 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37739 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37749 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-37761 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37780 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37785 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-85.85 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37846 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37879 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-37973 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37975 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38004 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38027 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38081 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38088 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38103 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38110 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38111 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38153 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38159 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38204 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38249 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38286 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38320 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38329 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38330 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38340 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38342 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38395 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38445 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38482 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38483 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38497 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38502 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38521 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38529 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38530 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38556 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38616 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-88.89 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38636 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38652 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38670 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38677 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38679 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38680 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38713 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38728 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-39682 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-86.87 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-39685 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39687 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39710 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39719 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39744 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39750 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39757 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39760 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39761 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39817 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39839 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-39853 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39883 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39891 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39901 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40082 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40301 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40322 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40349 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40351 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40358 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68168 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68183 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68184 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68254 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-68324 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68347 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68356 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68366 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68724 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68811 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-71093 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-71101 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71112 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71116 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-71133 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71136 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71231 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23076 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23099 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23102 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23187 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23204 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23235 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23244 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23269 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23315 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23318 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23325 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23327 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23363 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23388 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23397 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31430 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31479 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31568 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31614 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31685 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31778 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43040 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43042 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43051 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43052 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43141 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43241 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43281 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43330 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43386 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43427 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43449 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43450 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43453 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45893 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45943 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45957 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45994 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46022 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46033 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46053 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46056 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46064 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46094 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46120 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46130 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46150 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46191 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46203 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46209 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52968 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53138 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53149 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53179 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53303 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53309 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53330 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63806 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64039 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64078 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64121 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64237 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64407 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64572 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68099 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68155 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-68188 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68263 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68373 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89633 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89636 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89637 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-21905 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21950 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23157 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38292 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39683 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39869 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43056 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43126 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43380 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43414 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-45851 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46293 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53255 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64153 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-35177 | NONE0 | vim-common 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-35177 | NONE0 | vim-runtime 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43304 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46043 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-52993 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53002 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53398 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63940 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74394 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-22036 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-86.87 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37915 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38352 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-87.88 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2025-40158 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40318 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-23191 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23392 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31419 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31586 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31656 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31663 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31694 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31772 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43023 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43116 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43198 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-137.137 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43341 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43370 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43493 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-43494 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-124.124 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43503 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-124.124 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-45852 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45878 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45972 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46119 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46185 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46242 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-137.137 | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-46275 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46319 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46330 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53006 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53072 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53182 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53185 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53212 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-137.137 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53224 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-138.138 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53239 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53250 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53254 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53256 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53264 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53270 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53275 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53356 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53357 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53388 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53399 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63801 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63809 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63823 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63884 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63917 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63946 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63971 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64002 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64015 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64032 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64115 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64191 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64266 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64380 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64385 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64386 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64387 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64543 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64548 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64554 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64557 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64597 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68117 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68147 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68162 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68236 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68257 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68323 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68329 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68399 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68442 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68451 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68470 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-72111 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72123 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72135 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72288 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72338 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74378 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74390 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74446 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74506 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74534 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74535 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80668 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80681 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80691 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80693 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80700 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80702 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80710 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80716 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80718 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80725 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-3864 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2022-1247 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-2961 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50106 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-22004 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37776 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-38051 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38107 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38108 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39702 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-39749 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39759 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39826 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39905 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39993 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-90.91 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40135 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-40154 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40168 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40248 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40259 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40271 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-40354 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68174 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68175 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68303 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68810 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71192 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71203 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71221 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23050 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23054 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23270 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23454 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31408 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43050 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43158 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43226 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43233 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43303 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43334 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43339 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45856 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45859 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-45860 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-45910 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45942 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45970 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46015 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46052 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46054 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46076 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46090 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46114 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46116 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46117 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46123 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46133 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-46145 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46149 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46152 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46173 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46176 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46181 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46199 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46204 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46227 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46230 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46266 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46306 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46324 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52917 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52918 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-52920 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-52935 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52942 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52945 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52947 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52951 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52953 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52956 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52957 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-52986 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-52991 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52998 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-53000 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53005 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53009 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53011 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53016 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53049 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53075 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53091 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53131 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53132 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53133 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53223 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53228 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-137.137 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53242 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53246 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-138.138 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53268 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53329 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53354 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53355 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53381 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53391 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53392 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53397 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63795 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63802 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63807 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63808 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63824 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63826 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63831 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63879 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63883 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63886 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-63887 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-63888 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-63889 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-63891 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63896 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63898 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63899 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63901 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63912 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-63913 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2026-63914 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63916 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-63919 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-63920 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63921 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63922 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-63924 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-63925 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63928 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63944 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63945 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63947 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63952 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63956 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63957 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63958 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63962 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63970 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63975 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-63978 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-63979 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-63984 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63992 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63993 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63994 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64000 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64001 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64007 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64009 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64017 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64025 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64026 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64029 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64047 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64048 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64051 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64098 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64102 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64109 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64111 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64113 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64114 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64117 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64136 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64137 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64160 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64189 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64217 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64219 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64221 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64247 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64255 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64280 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64283 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64287 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64298 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64304 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64312 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64319 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64320 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-64323 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64364 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64372 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64379 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64382 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64384 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64402 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64418 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64422 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64438 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64456 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64470 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64471 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64473 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64508 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64523 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64525 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64527 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64534 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64539 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64551 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64552 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64560 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64561 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64573 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64577 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-68086 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68093 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68100 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68108 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68118 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68123 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-68125 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-68131 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68138 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-68140 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-68144 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68145 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68148 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68149 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68154 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-68157 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-68158 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-68160 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-68161 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-68169 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68181 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68202 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68245 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68253 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68266 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68273 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68289 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68293 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68299 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68300 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-68315 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68320 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68325 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68335 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68338 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68343 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68349 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68351 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68363 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68365 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68368 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68374 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68376 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68377 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68381 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68388 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68389 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-68391 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68397 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-68400 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68401 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68402 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-68404 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68409 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68427 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68448 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68452 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68453 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68479 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72020 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72021 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72045 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72049 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72053 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72055 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72057 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72061 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72065 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72066 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72069 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72072 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72083 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72084 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72102 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72125 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72126 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72136 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72157 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-72217 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72218 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72219 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72221 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72222 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72242 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72247 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72251 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72252 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72253 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72261 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72262 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72284 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72289 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72298 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72301 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72317 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72318 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72319 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72320 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-72322 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72323 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72339 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72348 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72351 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72361 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72371 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72382 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72389 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72398 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72399 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72405 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-72419 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72422 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72427 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-72436 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72443 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72449 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72451 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72469 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-72473 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72492 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-72499 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-72502 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-74256 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74269 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74270 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74271 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74283 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74287 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74289 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74305 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74310 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74345 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74359 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74391 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74398 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74436 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74439 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74440 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74441 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74443 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74456 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74469 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74471 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74472 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74474 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74476 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74488 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74492 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74493 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74496 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74498 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74499 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74501 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74502 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74533 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74537 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74541 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74557 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74563 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74569 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74575 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74586 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74587 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74594 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74597 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74598 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74608 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74609 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74610 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74611 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74612 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74614 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74615 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74616 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74621 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74624 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74630 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74637 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74641 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74656 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74660 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74661 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74662 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74666 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74668 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74672 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74677 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74682 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74684 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74688 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74692 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74695 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74697 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74700 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74705 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74714 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74715 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74724 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74730 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74737 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-74743 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80521 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80528 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80540 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80552 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80553 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80558 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80561 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80584 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80585 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-80589 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80603 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80609 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80613 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80630 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80663 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80722 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80944 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80945 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80947 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80951 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80952 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80971 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80973 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80976 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-80977 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80978 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80979 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80982 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80989 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-80994 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-81000 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-81001 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-81002 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-81008 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89440 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89458 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89476 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89478 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89482 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89487 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89489 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89500 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89510 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89526 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89532 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89533 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89540 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89543 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89547 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89548 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89551 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89553 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89555 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89559 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89564 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89569 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89579 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89583 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89603 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89607 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89625 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89626 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89634 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89638 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89643 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89648 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89654 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89655 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89656 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89659 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89662 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89665 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89666 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89672 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89682 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89693 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89694 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89697 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89702 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89705 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89706 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89707 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89708 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89710 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89729 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89736 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89741 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89747 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-45885 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-38102 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40096 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31508 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43332 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45861 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45894 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46251 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46325 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-137.137 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53053 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53062 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53078 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53189 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53209 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53230 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53253 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53374 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53384 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63800 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63830 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-63875 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64011 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64034 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64286 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64303 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-64355 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64375 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64378 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64401 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64448 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64475 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64481 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68142 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68156 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-68432 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-72051 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72310 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72329 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72342 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74405 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80698 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46483 | NONE0 | vim-common 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.15 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-46483 | NONE0 | vim-runtime 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.15 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-47907 | NONE0 | stdlib v1.23.4 fixed in 1.23.12, 1.24.6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53196 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40345 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68346 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46125 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89671 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89704 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89713 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-4673 | NONE0 | stdlib v1.23.4 fixed in 1.23.10, 1.24.4 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-40257 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46331 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-137.137 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-68284 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2019-15794 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2025-40024 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68237 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64296 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64322 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64324 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89615 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-6238 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-57795 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22035 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-86.87 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-22097 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-86.87 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53094 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40018 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-90.91 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40261 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-45991 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53267 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89545 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-28419 | NONE0 | vim-common 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.10 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-28419 | NONE0 | vim-runtime 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.10 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68284 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-64535 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-40273 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53176 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-137.137 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2023-1193 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2025-39969 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40061 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68354 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68362 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68380 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68729 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23179 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31470 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31588 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64003 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89642 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89698 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89723 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89761 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-0564 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-43239 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-47906 | NONE0 | stdlib v1.23.4 fixed in 1.23.12, 1.24.6 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-61727 | NONE0 | stdlib v1.23.4 fixed in 1.24.11, 1.25.5 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39825 | NONE0 | stdlib v1.23.4 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-23383 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23450 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-31502 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31516 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31525 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52910 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53033 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53036 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53085 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53090 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64276 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64383 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-39978 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40074 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40321 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40350 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-68371 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23456 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-45932 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64277 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89469 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89471 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89495 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89537 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89617 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89663 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89675 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89742 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-44034 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-21999 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23178 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53110 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-32282 | NONE0 | stdlib v1.23.4 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31504 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40000 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40307 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40320 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-68282 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64483 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89580 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89632 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89649 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89743 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23253 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40048 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-40052 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40146 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68305 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68757 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71066 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80788 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40190 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68819 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31449 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31505 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31700 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31708 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40019 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-94.96 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40038 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40071 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40080 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40279 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40355 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68245 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68342 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68343 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68736 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68764 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68770 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-68815 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43044 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43134 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68103 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68350 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31464 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31511 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31570 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43197 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-137.137 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-72054 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-32289 | NONE0 | stdlib v1.23.4 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31649 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89573 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89763 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23246 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-3714 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2025-40083 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40242 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40324 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-68246 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-68302 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-68320 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89477 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89479 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89484 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89511 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89528 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89531 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89539 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89541 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89549 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89550 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89565 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89696 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2018-1121 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 4.2% Low-Moderate Risk | Not Applicable |
| CVE-2024-45336 | NONE0 | stdlib v1.23.4 fixed in 1.22.11, 1.23.5, 1.24.0-rc.2 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-40111 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23240 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-23271 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23317 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31414 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52908 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39994 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39998 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40118 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40194 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40201 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40203 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40237 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40272 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40323 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40329 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40340 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68742 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23239 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31426 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43279 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46065 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46113 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31392 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40319 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46024 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89493 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89587 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89631 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-28956 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-36350 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-36357 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-68801 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68816 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31637 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-45988 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-21926 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23150 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37790 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37956 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-38003 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38005 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38075 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-38382 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38560 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38577 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38578 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38604 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38615 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39698 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-94.96 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39714 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39931 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39948 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40075 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40159 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40167 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40300 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-87.88 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-68192 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-68208 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68304 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71315 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23066 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23105 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23172 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23222 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23273 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-111.111 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23340 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23351 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23391 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23449 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31403 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31436 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31447 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31454 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31469 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31473 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31507 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31528 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31548 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31554 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31648 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31665 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31673 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31680 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31693 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31758 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43009 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43016 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43019 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43030 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43033 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43060 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43083 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-137.137 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43084 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43091 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43093 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43111 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43153 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43214 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43215 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43278 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43365 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43406 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43407 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43408 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43437 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43456 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43502 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45850 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45864 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45899 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46273 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46304 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46320 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52909 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52958 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53050 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53086 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53151 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-137.137 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53159 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53183 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53269 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53365 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63926 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63976 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64005 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64073 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64123 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64423 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64567 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68085 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-68098 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68189 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68196 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68204 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68446 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-72024 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72110 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72124 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-72195 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72372 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72390 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72472 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72478 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74317 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74334 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74341 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74363 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74411 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74427 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74438 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74465 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74470 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80631 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-80634 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80637 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80644 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80671 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80692 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80721 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2015-7837 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2016-8660 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-0480 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-4543 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2022-48846 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48929 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49940 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50230 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50232 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50332 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50380 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-0160 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31082 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-52879 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53642 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54190 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-14027 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27025 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-35895 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35948 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35995 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41008 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42125 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42139 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43844 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43872 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46742 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46748 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47729 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49904 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49908 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49910 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49916 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49932 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49940 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49970 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49990 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50003 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50004 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50034 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50102 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-52560 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53056 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53064 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56368 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56544 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56591 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-56617 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56639 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56671 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56702 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56712 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57809 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57852 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57922 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-57950 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57976 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58012 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58089 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58090 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58092 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-86.87 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58094 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58095 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58096 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-58097 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58098 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58100 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58241 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21696 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21709 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21729 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-88.89 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21730 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21752 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21817 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21819 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21833 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21872 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21873 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21875 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21877 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21880 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21881 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21884 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21885 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-21888 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21889 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21890 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-21891 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21894 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21898 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21903 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21904 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21907 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21908 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21909 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21910 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21911 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21912 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21913 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21916 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21917 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21918 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21922 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21925 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21930 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21931 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21935 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21936 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21937 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21941 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21944 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21948 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21955 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-21956 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21957 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21959 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-21960 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-21961 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-21972 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21977 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21978 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21980 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21982 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21986 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21992 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21994 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-21995 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21996 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21997 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22001 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22002 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22003 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22007 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22008 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22009 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22010 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22011 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22013 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22015 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22017 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22018 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-86.87 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22019 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-86.87 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22021 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-86.87 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-22025 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-86.87 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-22026 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22028 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-86.87 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22033 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-86.87 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22037 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-101.101 | 67.6% Actively Exploited | Not Applicable |
| CVE-2025-22042 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-86.87 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-22043 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-22045 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-86.87 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22053 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-86.87 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22055 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-86.87 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-22057 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-86.87 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22058 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-86.87 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22062 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-86.87 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-22063 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-86.87 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-22064 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-86.87 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-22070 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-86.87 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22071 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-86.87 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22072 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-86.87 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22073 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-86.87 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22080 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-86.87 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22081 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-86.87 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22086 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-86.87 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-22089 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-86.87 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22090 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-86.87 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22101 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22103 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22105 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22106 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22108 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-22109 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22111 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22113 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22116 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22120 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22125 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22127 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-22128 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23129 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23130 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23131 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23132 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23135 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23136 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-86.87 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23138 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-86.87 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23140 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23141 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23143 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23144 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23145 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-23146 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23147 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23148 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23149 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23155 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23159 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23160 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23161 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-23162 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23163 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37740 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37741 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37742 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37743 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37744 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37745 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37746 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37747 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37748 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37754 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37755 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-37756 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-85.85 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37757 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-37758 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37759 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37764 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37765 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37766 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37767 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37768 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37769 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37770 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37771 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37772 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37773 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37775 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37781 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37784 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37787 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37788 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37792 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37793 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37794 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37799 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37801 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37805 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37806 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37807 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37808 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37809 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37811 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37812 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37813 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37815 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37816 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37820 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-37824 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37826 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37827 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37828 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37829 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37830 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37831 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37833 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37834 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37836 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37841 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37842 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37844 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37850 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37851 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37852 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37853 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37855 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37856 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37857 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37858 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37859 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37860 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37862 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37863 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37864 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37865 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37867 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37870 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37871 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-37872 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37873 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37874 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37875 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37876 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37877 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37878 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37880 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37881 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37883 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37884 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37886 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37887 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37889 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37897 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37900 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37901 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37905 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37907 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37909 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37911 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37912 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37917 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-37922 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37925 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37930 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37931 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37933 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37935 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-37936 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37937 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-86.87 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37938 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37940 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37945 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37948 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37951 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37954 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37958 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-90.91 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37959 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-37960 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37961 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37962 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37963 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37967 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37968 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37969 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37970 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37972 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37977 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37978 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37980 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37982 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37983 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37984 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37986 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37987 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37989 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37990 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37992 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37994 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37995 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37998 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38006 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38007 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38009 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38010 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38011 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38014 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38015 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38018 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-38020 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38023 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38029 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38031 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38033 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38034 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38035 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-38036 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38037 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38038 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38039 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38040 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38041 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38042 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38043 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38044 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38045 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38047 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38053 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38055 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38057 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-38058 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38059 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38060 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38061 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38063 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38066 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38067 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-38070 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38071 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38072 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38080 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38084 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38086 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38089 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-38090 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38094 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38095 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38096 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38097 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38098 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38099 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38100 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38105 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38113 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38115 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38119 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38120 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-38122 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38123 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-38124 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-38125 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38126 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38127 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38132 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38135 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38136 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38138 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38140 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38142 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38143 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38145 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38147 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38148 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38149 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38155 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38156 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38158 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38160 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38161 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38162 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38163 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38164 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38165 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-38166 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38167 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38168 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38169 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38170 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38173 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38174 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38181 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-38184 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38185 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38188 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38189 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38190 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38191 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2025-38192 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38193 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38194 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38197 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38199 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38200 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38202 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38203 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38205 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38207 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38208 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38210 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38214 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38215 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38218 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38219 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38220 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38222 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38225 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38229 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38231 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38237 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38244 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38246 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-38251 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38255 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38258 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38260 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38261 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38262 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38263 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38264 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-38265 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38269 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38272 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38274 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38275 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38277 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38278 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38282 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38283 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38285 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38290 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38299 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38300 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38303 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38304 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38305 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38307 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38310 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38311 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38312 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38319 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38321 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38322 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38324 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38326 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38328 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38331 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-38332 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38333 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38334 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38335 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38336 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38337 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38343 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38344 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38345 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38347 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38351 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38353 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38354 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38359 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38360 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38362 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38363 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38364 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38368 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38371 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38372 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38373 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38374 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38376 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38384 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38387 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38388 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38390 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38391 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38392 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38399 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-38400 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38402 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38405 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-38406 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38407 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38408 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38409 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38410 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38412 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38414 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38418 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38419 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38420 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38424 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38426 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38427 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38430 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-38436 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38438 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38441 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38444 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38449 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38455 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38457 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38458 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38460 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38463 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38465 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38466 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38467 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38468 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38469 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38470 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38472 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-38473 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38474 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38480 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38481 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38487 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38489 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38493 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38495 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-38496 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38498 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38503 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38506 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38507 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38510 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38511 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38513 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38514 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-38516 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38520 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38526 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-38528 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38531 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38537 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38540 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38542 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38543 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38544 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38546 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38549 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38551 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38562 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 8.3% Low-Moderate Risk | Not Applicable |
| CVE-2025-38569 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38571 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-38576 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38581 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38583 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38587 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38588 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38590 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-38591 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38597 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38601 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38602 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38605 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38608 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-38609 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38610 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38612 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38614 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38619 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38621 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38622 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38623 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38624 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38625 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38626 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38630 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38634 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38635 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38637 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-86.87 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-38639 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38640 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38644 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38645 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38646 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38648 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38650 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38660 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-38663 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38664 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38665 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38668 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38671 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38678 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-88.89 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-38683 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38684 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38686 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38691 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38692 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38693 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38694 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38695 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38696 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38698 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38700 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38701 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38705 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38706 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38709 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38710 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38711 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38712 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38716 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38721 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38725 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38732 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39675 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39676 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39677 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39678 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39679 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39681 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39684 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39692 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39693 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39694 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39703 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-39705 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39706 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39707 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39709 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39712 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39715 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39716 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39718 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39720 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-39721 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39724 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39731 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39732 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39734 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39736 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39737 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39739 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39742 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39745 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39746 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39747 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39748 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39752 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39753 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39756 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39758 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-39762 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39763 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39764 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39770 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-39771 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39772 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39773 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39779 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39781 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39782 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39787 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39789 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39794 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39795 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39798 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-39800 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39801 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39805 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39807 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39808 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39811 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39812 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39815 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39819 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39827 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39829 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39832 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39833 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39838 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39842 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39843 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39844 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39845 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39846 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39847 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39848 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39850 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39851 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-39852 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39857 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-39865 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39876 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39885 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39886 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39889 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39890 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39894 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-39895 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39897 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-39899 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39902 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39907 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39909 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39910 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39914 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39916 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39920 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39923 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39925 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39929 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-39932 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-39933 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39934 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39937 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39938 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39940 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39942 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-39946 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 9.6% Low-Moderate Risk | Not Applicable |
| CVE-2025-39947 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39950 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39953 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39965 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39989 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39990 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40005 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40009 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40010 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40020 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40026 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40029 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40030 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40031 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40037 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40040 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40042 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40044 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40049 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40053 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-40057 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40070 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40078 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40086 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40088 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40092 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40099 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40100 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40102 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40103 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40104 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40105 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40109 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40115 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40125 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40140 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40153 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40155 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40160 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40164 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40169 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40171 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40195 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40196 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40205 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40211 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40219 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40231 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40235 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40251 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40253 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40264 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40280 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40283 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40284 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40287 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40293 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40297 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40305 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40325 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40328 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-40334 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40339 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40346 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40347 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-40360 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40363 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68171 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68173 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68176 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68178 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68185 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68188 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68193 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68194 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68198 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68200 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68204 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68206 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-68209 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68211 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68212 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68213 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68218 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-68219 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68222 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68223 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68227 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68229 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68231 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68233 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68236 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68244 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68251 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68259 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68261 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-68281 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68283 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-68285 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-68287 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68288 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68291 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68295 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68297 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68301 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-68307 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68308 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68309 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68310 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68313 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68321 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-68331 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68333 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68334 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68336 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-68337 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-68340 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68345 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68351 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68353 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68358 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68363 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68365 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-68372 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68378 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68379 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68725 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68730 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68732 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68734 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68753 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68756 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68758 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68774 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-68776 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68778 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68780 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68783 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68785 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68794 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-68795 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68798 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68802 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68803 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-68813 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68814 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68818 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-68820 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68821 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68822 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68823 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71064 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71072 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-71077 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71079 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71081 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71083 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71084 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71085 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-71087 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71088 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71094 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71096 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71097 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71098 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71102 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71104 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71105 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71107 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71108 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71109 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71113 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71114 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71115 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71118 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71119 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71120 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-71121 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71125 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71126 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-71127 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71130 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71131 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-71132 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-71135 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71138 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71141 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71144 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71147 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71150 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71151 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71153 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71154 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71160 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71161 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-71163 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71180 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71182 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71183 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-71184 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71185 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71186 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71188 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71189 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71190 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71191 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71194 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71200 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71202 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71204 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-71222 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71223 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71227 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71229 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71232 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71233 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71235 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71236 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71237 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71239 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71265 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71266 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71267 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71268 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71269 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71272 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71273 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71285 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71287 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71288 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71289 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-71290 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71291 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71292 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-71293 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71294 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71295 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71297 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71299 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22976 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22977 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22979 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22981 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22982 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22985 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22990 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-22991 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-22992 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-22993 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22994 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22996 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-22997 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-22999 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23000 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23003 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-23005 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23006 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23011 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23017 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23019 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23020 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23021 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23026 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23031 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23038 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-23047 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23057 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23058 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23059 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23060 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-107.107 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23061 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23062 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23063 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23064 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23065 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23069 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23075 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23080 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23084 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23085 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23086 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23087 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23088 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23090 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23091 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23093 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23094 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23095 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23096 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23097 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23100 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23104 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23107 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23108 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23113 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23116 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23119 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23120 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23121 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23123 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23124 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23125 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23128 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23129 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23131 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23133 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23135 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23136 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-23137 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23138 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23139 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-23140 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23141 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23142 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23144 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23145 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23146 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23148 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-23150 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23151 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23152 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23154 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23157 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23159 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23160 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23163 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23164 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23166 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23168 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23170 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23173 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23190 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23196 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23200 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23201 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23202 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23205 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23206 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23213 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23214 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23215 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23217 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23220 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23228 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23229 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23236 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23237 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23238 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23241 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23242 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-23247 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23249 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23254 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23255 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23256 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23257 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23258 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23259 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23260 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23261 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23264 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23265 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23266 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23267 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23272 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23274 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23276 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23277 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23278 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23279 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23284 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23285 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23286 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23287 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23289 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23290 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23291 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23292 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23293 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23296 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23298 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23300 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23303 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23304 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23307 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23308 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23310 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23312 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23313 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23321 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23324 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23330 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23334 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23335 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23339 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23346 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23347 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23352 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23356 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23357 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23360 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23362 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23365 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23367 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23368 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23369 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23370 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23371 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23374 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23375 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23377 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23379 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23381 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23382 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23386 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23389 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23396 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23398 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23399 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23401 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23403 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23404 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23405 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23409 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23414 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23418 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23419 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23420 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23426 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23434 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23438 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23439 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23442 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23446 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23460 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23461 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23462 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-23464 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23465 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23468 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23470 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23472 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23474 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23475 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31391 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31394 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31400 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31407 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31410 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31411 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31412 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31415 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31416 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31418 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31420 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31421 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31422 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31423 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31424 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31425 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31427 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31428 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31429 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31434 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31438 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31439 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31440 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31441 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31450 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31451 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31458 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31461 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31462 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31467 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31480 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31482 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31483 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31486 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31487 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31492 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31495 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31496 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31497 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31498 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31499 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31503 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31509 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31510 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31512 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31515 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31518 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31519 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31520 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31521 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31522 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31524 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31526 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31531 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31533 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31537 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31540 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31542 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31545 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31546 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31549 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31550 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31551 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31552 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31555 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31556 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31557 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31560 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31565 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31575 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31577 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31579 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31585 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31590 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31592 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31594 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31595 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31596 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31599 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31603 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31604 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31605 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31606 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31610 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31615 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31616 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31617 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31618 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31619 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31623 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31624 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31625 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31628 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31630 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31634 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31638 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31639 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31642 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31645 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31646 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31651 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31655 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31658 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31660 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31661 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31662 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31664 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31670 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31671 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31672 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31674 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31675 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31676 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-124.124 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31677 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31679 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31681 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31682 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31684 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31687 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31689 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31692 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31698 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31699 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31701 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31704 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31714 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31721 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31722 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31723 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31724 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31725 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31726 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31737 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31738 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31740 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31741 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31749 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31752 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31754 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31755 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31756 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31762 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31763 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31767 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31770 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31773 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31777 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31781 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43010 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43012 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43013 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43014 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43017 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43018 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43021 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43022 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43024 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43025 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43026 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43028 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43029 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43032 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43034 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43035 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43036 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43041 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43043 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43045 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43046 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43048 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43054 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43057 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43058 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43061 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43062 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43064 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43065 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43066 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43068 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43069 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43072 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43073 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43077 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43079 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43080 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43081 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43082 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43085 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43086 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43088 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43089 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43092 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43094 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43098 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43099 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43101 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43103 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43104 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43105 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43107 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43109 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43113 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43115 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43118 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43119 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43123 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43124 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43127 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43129 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43130 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43131 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43132 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43135 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43136 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43137 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43139 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43140 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43143 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43145 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43147 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43148 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43149 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43152 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43156 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43157 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43159 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43161 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43162 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43165 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43167 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43168 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43169 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43170 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43171 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43172 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43173 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43175 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43182 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43183 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43187 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43189 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43191 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43194 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43195 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43199 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43200 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43201 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43202 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43204 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43209 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43213 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43216 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43218 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43219 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43220 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43221 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43223 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43225 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43227 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43228 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43229 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43230 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43231 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43234 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43238 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43240 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43242 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43243 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43244 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43246 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43251 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43252 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43253 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43255 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43257 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43261 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43262 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43264 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43265 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43266 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43267 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43268 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43269 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43270 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43271 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43273 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43277 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43287 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43288 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43289 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43292 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43294 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43295 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43296 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43297 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43298 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43299 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43300 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43301 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43302 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43305 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43306 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43308 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43309 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43310 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43311 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43312 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43313 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43314 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43315 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43316 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43317 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43318 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43319 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43320 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43327 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43331 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43333 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43338 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43340 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43343 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43344 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43345 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43350 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43355 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43357 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43359 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43360 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43361 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43362 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43363 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43366 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43368 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43371 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43372 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43381 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43382 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43387 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43395 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43397 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43398 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43400 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43405 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43409 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43410 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43411 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43412 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43413 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43416 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43419 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43421 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43424 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43425 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43428 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43429 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43432 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43436 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43441 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43443 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43445 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43451 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43452 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43455 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43457 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43459 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43463 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43464 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43466 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43467 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43468 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43469 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43471 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43472 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43473 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43474 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43475 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43483 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43488 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43491 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43492 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43496 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45834 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45835 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45836 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45840 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45842 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45843 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-45845 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45846 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45847 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45848 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45855 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45857 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45873 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45886 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45890 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45901 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45904 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45912 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45913 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45915 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45917 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45919 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45921 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45923 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45924 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45928 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45930 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45934 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45940 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45941 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45944 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45947 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45948 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45954 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45960 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45961 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45962 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45963 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45964 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45965 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45968 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45969 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45973 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45974 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45976 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45978 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45981 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45982 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45983 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45985 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45986 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45987 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45997 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45999 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46000 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-124.124 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46002 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46003 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46005 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46007 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46009 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46012 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46014 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46016 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46018 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46019 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46021 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46023 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46026 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46027 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46028 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46032 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46037 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46038 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46040 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46041 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46044 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46046 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46049 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46050 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46051 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46059 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46061 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46063 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46066 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46070 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46071 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46072 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46073 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46077 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46078 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46079 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46080 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46082 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46083 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46086 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46088 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46089 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46091 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46092 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46098 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46101 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46102 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46103 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46106 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46107 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46108 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46111 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46115 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46126 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46127 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46128 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46131 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46132 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46137 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46138 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46139 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46142 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46143 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46144 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46146 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46148 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46151 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46153 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46157 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46158 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46160 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46161 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46167 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46168 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46169 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46170 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46171 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46172 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46178 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46179 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46184 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46186 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46190 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46193 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46196 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46197 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46200 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46201 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46207 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46211 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46214 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46220 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46225 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46226 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46229 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46231 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46233 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46235 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46236 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46247 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46260 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46289 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46302 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46303 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46314 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46315 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46321 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46322 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52913 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52915 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52916 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52921 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52925 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52926 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52927 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52928 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52929 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-52930 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52936 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52937 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52939 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52941 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52944 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52946 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-52948 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52954 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-52961 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52963 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52964 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52967 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52970 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52972 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52974 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-52975 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52977 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52981 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-52984 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52985 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52988 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52990 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52994 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52995 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52999 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-53001 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53003 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53012 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53013 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53014 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53015 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53017 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53018 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53021 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53022 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53023 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53027 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53032 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53034 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53037 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53039 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53056 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53064 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53066 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53069 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53074 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53076 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53077 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53080 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53083 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53088 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53103 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53107 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53122 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53128 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53134 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53139 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53140 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53144 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53150 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53163 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53167 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53168 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53181 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53184 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53190 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53199 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-53208 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53210 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53214 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53218 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53219 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53220 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53221 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53227 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53245 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53251 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53252 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53263 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53274 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53279 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53281 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53284 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53285 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53287 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53289 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53291 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53292 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53293 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53295 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53297 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53304 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53306 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53313 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53314 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53317 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53320 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53325 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53327 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53331 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53332 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53336 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53337 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53339 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53343 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53345 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53347 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53349 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53350 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53353 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53358 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53369 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53375 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53376 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53377 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53379 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53382 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53385 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53393 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53402 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53403 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63798 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63803 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63810 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63821 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63822 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63838 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63843 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63844 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63845 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63846 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63847 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63848 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63851 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63852 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63853 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63854 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63855 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63856 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63858 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63860 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63865 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63867 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-63868 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63870 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63876 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63877 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63881 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63882 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63890 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63892 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63897 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63900 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63902 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63903 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63904 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63943 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63948 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63961 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63963 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63964 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63968 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-63969 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63973 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63980 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-63983 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63985 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63990 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63991 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63999 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64004 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64006 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64012 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64014 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64036 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64038 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64046 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64052 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64060 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64064 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64070 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64076 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64077 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64079 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64083 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64087 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64090 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64092 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64094 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64097 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64106 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64112 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64116 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64118 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64125 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-64126 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64127 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64128 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64131 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64133 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64134 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64135 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64144 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64146 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64147 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64154 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64155 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64163 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64164 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64165 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64166 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64168 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64170 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64173 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64174 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64177 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64178 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64179 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64180 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64182 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64183 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64184 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64185 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64187 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64190 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64192 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64205 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64206 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64210 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64212 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64213 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64214 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64220 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64222 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64227 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64231 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64233 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64234 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64240 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64241 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64243 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64244 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64254 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64256 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64275 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64289 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64294 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64297 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64299 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64301 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64306 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64315 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64316 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64321 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64326 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64331 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64332 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64333 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64334 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64335 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64336 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64337 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64338 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64345 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64347 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64350 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64351 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64358 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64359 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64360 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64368 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64369 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64370 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64371 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64374 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64376 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64388 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64403 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64404 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64405 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64406 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64408 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64409 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64411 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64412 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64413 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64417 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64419 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64425 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64428 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64429 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64430 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64436 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64450 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64452 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64454 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64455 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64458 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64463 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64465 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64472 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64474 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64476 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64478 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64479 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64480 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64482 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64486 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64487 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64488 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64489 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64496 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64507 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64510 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64511 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64512 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64513 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64514 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64524 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64529 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64537 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64540 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64541 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-64542 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64544 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64545 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64546 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64547 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64549 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64553 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64555 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64569 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64570 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64571 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64576 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64578 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64579 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68090 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68091 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-68096 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68102 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68105 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68106 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68109 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68110 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68111 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68112 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68113 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68114 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68115 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68119 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68126 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68127 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68129 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68130 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68132 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68135 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68137 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68139 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68141 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68146 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68152 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68164 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68165 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68175 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68176 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68178 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68180 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68182 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68183 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68184 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68186 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68187 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68190 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68193 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68194 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68195 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68197 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68205 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68206 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68207 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68209 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68210 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68211 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68212 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68214 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68215 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68216 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68217 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68218 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68219 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68222 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68226 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68227 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68228 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68229 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68231 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68233 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68234 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68235 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68238 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68241 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68242 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68243 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68244 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68246 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68247 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68248 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68249 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68250 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68251 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68252 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68254 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68255 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68256 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68258 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68259 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68260 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68261 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68262 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68269 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68271 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68272 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68277 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68279 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68281 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68286 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68287 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68288 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68291 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68297 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68301 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68304 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68306 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68308 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68309 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68310 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68312 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68313 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68317 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68318 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68319 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68322 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68324 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68326 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-68328 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68331 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68333 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68336 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68339 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68346 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68348 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68352 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68354 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-68355 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68357 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68360 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68362 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68366 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68367 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68369 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68371 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68372 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68382 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68383 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68386 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68392 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68395 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68396 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68403 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68405 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68406 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68407 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68408 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68410 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68411 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68412 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68413 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68414 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68416 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68417 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68418 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68419 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68422 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68425 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-68428 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68429 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68430 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68431 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68433 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-68436 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68437 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68439 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68441 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68443 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68444 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68445 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68447 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68449 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68450 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68456 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68459 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68460 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68461 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68467 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68469 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68471 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-68474 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68475 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68477 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-68478 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72004 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72005 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72007 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72009 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72010 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72012 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72013 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72014 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72015 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72017 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72019 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72022 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72023 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72025 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72028 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72029 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-72030 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72031 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72033 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72035 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72036 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72037 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72038 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72039 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72040 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72041 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72047 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72048 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72056 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72058 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72059 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72062 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72063 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72067 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72068 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72070 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72073 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72074 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72075 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72076 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72077 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72078 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72079 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72081 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72082 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72085 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72086 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72087 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72088 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72089 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72096 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72097 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72105 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72106 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72107 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72109 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72113 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72114 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72115 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-72116 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72117 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72118 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72119 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72120 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72121 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-72122 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72127 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72132 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72133 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72138 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72142 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72144 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72146 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72147 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72148 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-72149 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72150 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72152 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72153 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72155 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72156 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72158 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72159 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72160 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72161 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72162 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72163 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72164 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72165 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72166 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72167 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72168 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72170 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72171 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72172 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72174 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72175 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72176 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72177 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72179 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72181 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72182 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72191 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72192 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72193 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72194 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-72196 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72197 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72198 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72200 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72202 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-72203 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72205 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72212 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72213 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72214 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72215 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72216 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72223 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72224 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72225 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72226 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72227 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-72228 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72229 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72230 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72231 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72232 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72233 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-72234 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72235 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-72236 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72237 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72238 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72240 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72241 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72244 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72245 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72250 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72254 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72256 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72257 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72258 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72259 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72260 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72264 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72265 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72266 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72267 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72268 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72269 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72270 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72271 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72272 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72273 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72274 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72275 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72276 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72282 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72290 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72296 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72297 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72299 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72300 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72302 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72304 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72305 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72307 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72308 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72315 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72321 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72324 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72325 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72326 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72327 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72330 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72334 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-72335 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72336 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72337 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72340 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72341 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72343 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72347 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72349 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72350 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72362 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72369 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72373 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72374 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72375 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72376 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72379 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72380 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-72383 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72384 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72391 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72392 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72395 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72396 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72397 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72400 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72402 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72404 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72406 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72409 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72413 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72414 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72416 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72418 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72420 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-72421 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72423 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72424 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72425 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72428 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72430 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72433 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72434 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72435 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72437 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72438 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-72439 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72440 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-72441 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72444 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-72447 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72448 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72450 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72459 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-72460 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-72464 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72466 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72467 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72470 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-72474 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72479 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72480 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-72481 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72483 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72484 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72485 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72486 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72487 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72488 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72489 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-72491 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72493 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-72494 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-72495 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72496 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74255 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74257 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74258 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74261 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74263 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74264 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74265 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74267 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-74272 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74273 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74276 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74278 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74279 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74280 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-74281 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-74282 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-74284 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74288 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74290 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74291 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74292 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74293 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74294 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74295 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74296 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74297 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74300 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74302 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74303 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74307 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74308 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74314 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74318 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74320 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74321 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74324 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74327 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74329 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74330 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74331 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74337 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74338 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74339 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74340 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74342 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74344 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74346 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74347 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74348 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74349 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74350 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74351 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74356 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74362 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74365 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74368 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74373 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74374 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74375 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74376 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74377 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74379 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74380 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74381 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74382 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74384 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74385 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74386 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74387 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74388 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74389 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74395 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74399 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74402 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74406 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74407 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74408 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74410 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74416 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74417 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74424 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74426 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74432 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74444 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74445 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74448 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74453 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74454 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74455 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74457 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74458 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74459 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74460 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74461 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74463 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74464 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74466 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74467 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74468 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74473 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74475 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74478 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-74479 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74482 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74483 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74484 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74485 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74487 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74494 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74495 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74497 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74500 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74505 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74507 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74508 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74514 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74515 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74521 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74522 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74523 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74525 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74530 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74531 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74532 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74536 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74538 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74540 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74543 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74544 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74546 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74547 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74548 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74549 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74550 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74551 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74552 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74553 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74555 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74558 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74559 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74560 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74565 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74566 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74567 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74571 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74572 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74577 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74578 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74579 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74584 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74585 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74589 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74590 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74592 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74595 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74599 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74600 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74601 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74602 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74603 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74605 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74606 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74607 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74613 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74618 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74619 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74620 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74622 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74623 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74625 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74626 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74628 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74632 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74634 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74635 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74636 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74638 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74646 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74647 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74648 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74649 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74650 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74651 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74653 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74654 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74655 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74657 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74658 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74659 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74663 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74664 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74667 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74670 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74671 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74673 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74675 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74676 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74678 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74679 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74680 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74683 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74687 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74689 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74693 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74694 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74696 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74701 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74704 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74710 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74711 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74713 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74717 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74718 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74719 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74720 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74722 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74723 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74725 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74726 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74729 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74733 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74734 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74735 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74736 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74739 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74740 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74747 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74748 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74754 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80526 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80527 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80529 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80539 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80541 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80542 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80547 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80548 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80549 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80550 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80551 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80554 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80556 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80557 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80559 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80560 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80562 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80565 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80566 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80567 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80568 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80569 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80570 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80572 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80573 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80574 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80576 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80578 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80579 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80580 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80581 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80583 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80587 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80591 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80593 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80594 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80595 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80597 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80598 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80599 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-80600 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80601 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-80602 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80605 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80607 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80611 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80616 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80618 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80619 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80620 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80626 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80646 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80659 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80664 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80667 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80669 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80670 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80684 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80686 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80694 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80695 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80697 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80703 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80707 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-80715 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80717 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-80928 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80930 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80931 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80932 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80933 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80935 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80937 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-80938 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80939 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80941 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80948 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80949 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80963 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80964 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80965 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80966 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80967 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80968 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80969 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80972 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80974 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80980 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-80983 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80984 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80987 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80988 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80990 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80991 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80992 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80996 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80999 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-81010 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-81011 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-81012 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-81013 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-81014 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-81016 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-81017 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89437 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89438 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89439 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89441 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89442 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89443 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89444 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89452 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89457 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89460 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89461 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89462 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89463 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89468 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89470 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89472 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89474 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89483 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89490 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89491 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89492 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89494 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89496 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89497 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89498 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89502 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89503 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89512 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89515 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89524 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89525 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89527 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89544 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89554 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89556 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89561 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89566 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89567 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89586 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89588 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89594 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89595 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89598 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89599 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89601 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89604 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89605 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89616 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89622 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89623 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89624 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89627 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89640 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89644 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89673 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89674 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89711 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89718 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89720 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89722 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89724 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89725 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89730 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89740 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89744 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89749 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89753 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89756 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89757 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89759 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89762 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89771 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89773 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2017-13693 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-12928 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-12929 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-53207 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21693 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21878 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21899 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21924 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21951 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21962 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21963 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21964 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21970 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21975 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21976 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21981 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22005 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22014 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22016 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22044 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-86.87 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22047 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-86.87 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22054 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-86.87 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22065 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-86.87 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-22066 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-86.87 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22075 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-86.87 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22077 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-22095 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-86.87 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22102 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22124 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37800 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37918 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37949 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38062 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38064 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38065 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38074 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38152 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-86.87 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-38240 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-86.87 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-38253 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38293 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-38386 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38429 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-38439 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-38478 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38491 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38499 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38532 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38539 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38575 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-86.87 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-38643 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38659 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38735 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39728 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-86.87 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-39949 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40027 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40051 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40094 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40292 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68179 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68265 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71095 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-71286 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71304 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71305 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71313 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23103 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23198 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23230 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23306 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23336 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23444 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31446 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31448 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31453 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31667 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31771 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31779 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43071 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43180 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43211 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43352 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43353 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43465 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-137.137 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43480 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43484 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43485 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45838 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45841 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45844 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45849 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45858 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45862 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45865 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45868 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45869 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45870 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45871 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45872 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45875 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45877 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45880 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45881 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45883 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45884 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45895 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45897 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45911 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46147 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46245 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46249 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46252 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46253 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46254 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46255 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46261 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46280 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46282 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46286 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46287 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46291 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46292 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46296 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46299 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46307 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46312 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52982 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53035 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53047 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53048 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53052 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53058 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53060 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53061 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53063 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53065 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53070 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53073 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53082 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53084 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53093 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53096 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53102 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53104 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53106 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53111 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53113 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53123 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53126 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53135 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53142 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53146 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53147 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53154 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53158 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53177 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53205 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53207 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53213 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53225 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-137.137 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53226 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53229 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-53232 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53236 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53237 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53238 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53249 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53258 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53261 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53265 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53400 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63893 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-63906 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63927 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63942 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64279 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64313 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64435 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64574 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68104 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68107 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68116 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68153 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68353 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-68454 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68466 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-72071 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72108 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72312 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72314 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72352 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72410 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72454 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-72476 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74262 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74312 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74313 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74397 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74401 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74450 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74481 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74490 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74512 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74519 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74527 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80622 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80623 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80624 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80627 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80628 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80629 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80635 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-80636 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80643 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80645 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-80647 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80649 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80650 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80652 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80653 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80654 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80660 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80662 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80676 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80677 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80678 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80679 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80680 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80689 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80704 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80706 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80708 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80709 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80711 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-28418 | NONE0 | vim-common 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.10 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-32249 | NONE0 | vim-common 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.11 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45130 | NONE0 | vim-common 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.14 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-51400 | NONE0 | vim-common 2:9.1.0016-1ubuntu7.8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-55892 | NONE0 | vim-common 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.17 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-59857 | NONE0 | vim-common 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.18 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-73074 | NONE0 | vim-common 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.19 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-28418 | NONE0 | vim-runtime 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.10 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-32249 | NONE0 | vim-runtime 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.11 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45130 | NONE0 | vim-runtime 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.14 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-51400 | NONE0 | vim-runtime 2:9.1.0016-1ubuntu7.8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-55892 | NONE0 | vim-runtime 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.17 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-59857 | NONE0 | vim-runtime 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.18 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-73074 | NONE0 | vim-runtime 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.19 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-32288 | NONE0 | stdlib v1.23.4 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89628 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22871 | NONE0 | stdlib v1.23.4 fixed in 1.23.8, 1.24.2 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-27142 | NONE0 | stdlib v1.23.4 fixed in 1.25.8, 1.26.1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39823 | NONE0 | stdlib v1.23.4 fixed in 1.25.10, 1.26.3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39826 | NONE0 | stdlib v1.23.4 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-15588 | NONE0 | gir1.2-glib-2.0 2.80.0-6ubuntu3.8 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-15588 | NONE0 | libglib2.0-data 2.80.0-6ubuntu3.8 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39968 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39972 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40204 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40353 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68367 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71225 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23053 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23457 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53194 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64538 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89485 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89536 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89538 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89560 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89608 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89609 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89657 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89676 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89680 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89684 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89685 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89686 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89699 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89712 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89726 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89765 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-20585 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40058 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-44656 | NONE0 | vim-common 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.14 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-47167 | NONE0 | vim-common 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.16 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-44656 | NONE0 | vim-runtime 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.14 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-47167 | NONE0 | vim-runtime 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.16 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-22866 | NONE0 | stdlib v1.23.4 fixed in 1.22.12, 1.23.6, 1.24.0-rc.3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-22873 | NONE0 | stdlib v1.23.4 fixed in 1.23.9, 1.24.3 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-47912 | NONE0 | stdlib v1.23.4 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-58185 | NONE0 | stdlib v1.23.4 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-58187 | NONE0 | stdlib v1.23.4 fixed in 1.24.9, 1.25.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-58189 | NONE0 | stdlib v1.23.4 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-61723 | NONE0 | stdlib v1.23.4 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-61724 | NONE0 | stdlib v1.23.4 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-61725 | NONE0 | stdlib v1.23.4 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-61730 | NONE0 | stdlib v1.23.4 fixed in 1.24.12, 1.25.6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-42505 | NONE0 | stdlib v1.23.4 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-42507 | NONE0 | stdlib v1.23.4 fixed in 1.25.11, 1.26.4 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-58186 | NONE0 | stdlib v1.23.4 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-39970 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40217 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40338 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40343 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-40344 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89456 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89475 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40178 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71193 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23035 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89574 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40121 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23180 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-modules 1.5.3-5ubuntu5.4 fixed in 1.5.3-5ubuntu5.6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-modules-bin 1.5.3-5ubuntu5.4 fixed in 1.5.3-5ubuntu5.6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-runtime 1.5.3-5ubuntu5.4 fixed in 1.5.3-5ubuntu5.6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam0g 1.5.3-5ubuntu5.4 fixed in 1.5.3-5ubuntu5.6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63871 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52955 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-57857 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21947 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-37906 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37920 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38078 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38561 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-94.96 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-38717 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39673 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-39726 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39977 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40039 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-23004 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23169 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43047 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-39293 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42107 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56552 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-56788 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21892 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21895 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21984 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-22027 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-86.87 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22050 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-86.87 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22060 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-86.87 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22115 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37985 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37988 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38008 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38048 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38085 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38104 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38112 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38217 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38232 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38234 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38242 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38365 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-38393 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-38448 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38461 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38462 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38477 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-85.85 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38515 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38524 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-38617 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-85.85 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-38632 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38675 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38681 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38687 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39697 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39713 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39754 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39813 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39825 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39884 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39927 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39980 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39991 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39992 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39996 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40006 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40011 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40016 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40056 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40085 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40110 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40120 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40129 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-40134 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40139 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40179 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40187 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-40215 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40220 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40238 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40244 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40250 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40252 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-40254 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40331 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68214 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68239 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68241 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-68264 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68296 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68312 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68374 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68745 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-68749 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71074 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71111 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71274 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23071 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23101 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23110 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23118 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23126 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23167 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23181 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23207 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23212 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23302 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23348 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23394 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23440 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23441 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23452 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23463 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23469 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31393 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31466 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31523 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31697 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31728 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31751 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43053 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43163 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43275 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43342 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43383 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43415 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43420 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43430 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43439 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43448 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45905 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45949 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46159 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46187 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53108 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53352 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64373 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-72316 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80534 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89488 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89501 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89508 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89520 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89575 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89596 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89606 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89647 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89717 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89731 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89750 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89751 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2017-0537 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2025-23151 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39961 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40342 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31389 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46272 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-57452 | NONE0 | vim-common 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.17 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-57452 | NONE0 | vim-runtime 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.17 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89733 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2019-15213 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-68360 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-40308 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40312 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40166 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40081 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23458 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2018-17977 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40001 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40021 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40123 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40157 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-86.87 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40183 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-40198 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40200 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40206 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40281 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68768 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23032 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68337 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89464 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89473 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89557 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89563 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89576 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89585 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89645 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89709 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89735 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89746 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2020-14304 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-28420 | NONE0 | vim-common 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.10 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-42307 | NONE0 | vim-common 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.14 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-28420 | NONE0 | vim-runtime 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.10 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-42307 | NONE0 | vim-runtime 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.14 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2025-22870 | NONE0 | stdlib v1.23.4 fixed in 1.23.7, 1.24.1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40275 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89621 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-41848 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-45341 | NONE0 | stdlib v1.23.4 fixed in 1.22.11, 1.23.5, 1.24.0-rc.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-40173 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40218 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74604 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-81005 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89448 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89451 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89467 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89504 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89552 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89582 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89719 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89732 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89738 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89752 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89755 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-53905 | NONE0 | vim-common 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.9 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-53906 | NONE0 | vim-common 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.9 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-53905 | NONE0 | vim-runtime 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.9 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-53906 | NONE0 | vim-runtime 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.9 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-64317 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56433 | NONE0 | login 1:4.13+dfsg1-4ubuntu3.2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-68740 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2020-35501 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-0987 | NONE0 | gir1.2-packagekitglib-1.0 1.2.8-2ubuntu1.5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-0217 | NONE0 | gir1.2-packagekitglib-1.0 1.2.8-2ubuntu1.5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | libncurses6 6.4+20240113-1ubuntu2 fixed in 6.4+20240113-1ubuntu2.2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | libncursesw6 6.4+20240113-1ubuntu2 fixed in 6.4+20240113-1ubuntu2.2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-40228 | NONE0 | libpam-systemd 255.4-1ubuntu8.17 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | libtinfo6 6.4+20240113-1ubuntu2 fixed in 6.4+20240113-1ubuntu2.2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39964 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-90.91 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40035 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40268 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40341 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-54505 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68191 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68744 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68746 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68775 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-68782 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-71148 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71224 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-22978 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31668 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52960 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89466 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40303 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | ncurses-base 6.4+20240113-1ubuntu2 fixed in 6.4+20240113-1ubuntu2.2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | ncurses-bin 6.4+20240113-1ubuntu2 fixed in 6.4+20240113-1ubuntu2.2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-40228 | NONE0 | systemd 255.4-1ubuntu8.17 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-40228 | NONE0 | systemd-dev 255.4-1ubuntu8.17 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-73071 | NONE0 | vim-common 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.19 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-73071 | NONE0 | vim-runtime 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.19 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68788 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-27139 | NONE0 | stdlib v1.23.4 fixed in 1.25.8, 1.26.1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89572 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89597 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-28422 | NONE0 | vim-common 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.10 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-28422 | NONE0 | vim-runtime 2:9.1.0016-1ubuntu7.8 fixed in 2:9.1.0016-1ubuntu7.10 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-23280 | NONE0 | cuda-compat-13-0 580.82.07-0ubuntu1 fixed in 580.95.05-0ubuntu0.24.04.2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-33219 | NONE0 | cuda-compat-13-0 580.82.07-0ubuntu1 fixed in 580.126.09-0ubuntu0.24.04.1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-33220 | NONE0 | cuda-compat-13-0 580.82.07-0ubuntu1 fixed in 580.126.09-0ubuntu0.24.04.1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-24182 | NONE0 | cuda-compat-13-0 580.82.07-0ubuntu1 fixed in 580.159.03-0ubuntu0.24.04.1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-24187 | NONE0 | cuda-compat-13-0 580.82.07-0ubuntu1 fixed in 580.159.03-0ubuntu0.24.04.1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-24190 | NONE0 | cuda-compat-13-0 580.82.07-0ubuntu1 fixed in 580.159.03-0ubuntu0.24.04.1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-24192 | NONE0 | cuda-compat-13-0 580.82.07-0ubuntu1 fixed in 580.159.03-0ubuntu0.24.04.1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-24193 | NONE0 | cuda-compat-13-0 580.82.07-0ubuntu1 fixed in 580.159.03-0ubuntu0.24.04.1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-24194 | NONE0 | cuda-compat-13-0 580.82.07-0ubuntu1 fixed in 580.159.03-0ubuntu0.24.04.1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-24196 | NONE0 | cuda-compat-13-0 580.82.07-0ubuntu1 fixed in 580.159.03-0ubuntu0.24.04.1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-24197 | NONE0 | cuda-compat-13-0 580.82.07-0ubuntu1 fixed in 580.159.03-0ubuntu0.24.04.1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-24198 | NONE0 | cuda-compat-13-0 580.82.07-0ubuntu1 fixed in 580.159.03-0ubuntu0.24.04.1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-24199 | NONE0 | cuda-compat-13-0 580.82.07-0ubuntu1 fixed in 580.159.03-0ubuntu0.24.04.1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-13608 | NONE0 | curl 8.5.0-2ubuntu10.13 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-80230 | NONE0 | curl 8.5.0-2ubuntu10.13 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-82209 | NONE0 | curl 8.5.0-2ubuntu10.13 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-2219 | NONE0 | dpkg 1.22.6ubuntu6.1 fixed in 1.22.6ubuntu6.6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-6297 | NONE0 | dpkg 1.22.6ubuntu6.1 fixed in 1.22.6ubuntu6.5 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-2219 | NONE0 | dpkg-dev 1.22.6ubuntu6.1 fixed in 1.22.6ubuntu6.6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-6297 | NONE0 | dpkg-dev 1.22.6ubuntu6.1 fixed in 1.22.6ubuntu6.5 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-13608 | NONE0 | libcurl3t64-gnutls 8.5.0-2ubuntu10.13 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-80230 | NONE0 | libcurl3t64-gnutls 8.5.0-2ubuntu10.13 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-82209 | NONE0 | libcurl3t64-gnutls 8.5.0-2ubuntu10.13 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-13608 | NONE0 | libcurl4t64 8.5.0-2ubuntu10.13 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-80230 | NONE0 | libcurl4t64 8.5.0-2ubuntu10.13 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-82209 | NONE0 | libcurl4t64 8.5.0-2ubuntu10.13 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-2219 | NONE0 | libdpkg-perl 1.22.6ubuntu6.1 fixed in 1.22.6ubuntu6.6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-6297 | NONE0 | libdpkg-perl 1.22.6ubuntu6.1 fixed in 1.22.6ubuntu6.5 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-56408 | NONE0 | libexpat1 2.6.1-2ubuntu0.4 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56409 | NONE0 | libexpat1 2.6.1-2ubuntu0.4 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-76641 | NONE0 | libexpat1 2.6.1-2ubuntu0.4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-56408 | NONE0 | libexpat1-dev 2.6.1-2ubuntu0.4 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56409 | NONE0 | libexpat1-dev 2.6.1-2ubuntu0.4 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-76641 | NONE0 | libexpat1-dev 2.6.1-2ubuntu0.4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-7017 | NONE0 | libperl5.38t64 5.38.2-3.2ubuntu0.2 fixed in 5.38.2-3.2ubuntu0.4 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-43904 | NONE0 | libpmi2-0-dev 23.11.4-1.2ubuntu5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-43904 | NONE0 | libpmi2-0t64 23.11.4-1.2ubuntu5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-43904 | NONE0 | libslurm40t64 23.11.4-1.2ubuntu5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-7709 | NONE0 | libsqlite3-0 3.45.1-1ubuntu2.4 fixed in 3.45.1-1ubuntu2.5 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39113 | NONE0 | libsqlite3-0 3.45.1-1ubuntu2.4 fixed in 3.45.1-1ubuntu2.8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43011 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-43185 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-53215 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-137.137 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-39987 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40025 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-54518 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-23372 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23393 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31405 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31413 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31432 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31433 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-31476 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31478 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31536 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31584 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31657 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31659 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31695 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31705 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31706 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31712 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31716 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31780 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43075 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43076 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43222 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43236 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43263 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43490 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-47331 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-124.124 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-47333 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-124.124 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52911 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52914 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-137.137 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53040 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53043 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53046 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53068 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53178 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53186 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53198 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-63815 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63954 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64091 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64093 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64188 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64269 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-64361 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64390 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64393 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64432 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64440 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64441 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64442 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-68199 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74268 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2023-54105 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36331 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-13350 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-84.84 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-27558 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37838 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-87.88 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39985 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39995 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40003 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40008 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40013 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40032 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40033 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40036 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40043 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40054 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40055 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40059 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40060 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40062 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40065 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40067 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40068 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40073 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40077 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40079 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40084 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40087 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-40093 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40095 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40097 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40098 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40101 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40106 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40107 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40112 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40116 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40124 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40126 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40127 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40136 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40137 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40150 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40156 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40165 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40172 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40180 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40188 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40192 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40193 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40207 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40208 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40221 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40223 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40226 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40233 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40243 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40245 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40247 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40263 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40274 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40278 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40282 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40285 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40286 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40288 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40289 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40306 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40310 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40311 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40313 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40314 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40315 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40317 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40332 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40333 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40335 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40337 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-62626 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68172 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68177 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68180 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68190 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68196 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68201 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68217 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68220 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68230 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68235 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68238 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68249 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68257 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68258 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68266 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68286 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68289 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68290 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68311 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68318 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68322 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68325 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68327 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68328 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68330 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68332 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68335 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68338 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68339 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68344 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68364 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68376 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68727 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68728 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68733 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68750 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-100.100 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68755 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68759 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68763 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68765 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68766 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68767 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68769 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68771 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68772 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68773 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68777 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68781 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68786 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68787 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68796 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68797 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68804 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71065 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71067 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71069 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71140 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-110.110 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71195 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71196 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71197 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71198 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71199 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23030 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23033 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23037 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23049 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23056 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23176 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23182 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-117.117 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23364 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-23406 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23407 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31409 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31417 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31477 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31494 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31563 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31597 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31598 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31602 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31611 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31612 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31622 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31626 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31629 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31683 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31707 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31711 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31768 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43184 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43203 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43212 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43245 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43258 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43336 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43373 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43377 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43384 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43476 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43495 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-45935 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45956 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45958 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46006 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46011 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46031 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46058 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46062 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46110 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46112 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46124 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46129 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46164 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46175 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46177 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46198 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46205 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46206 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46208 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46212 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46218 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46232 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46238 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46328 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-47326 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-124.124 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-47327 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-124.124 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-47328 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-124.124 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-47332 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-124.124 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-47334 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-124.124 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-47335 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-124.124 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-47337 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-124.124 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52919 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52922 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52931 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-137.137 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52934 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53024 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53025 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53041 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53045 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53368 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53383 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-53387 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53389 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53390 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53401 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63796 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63805 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63811 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63812 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63814 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63816 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63817 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63818 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63819 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63825 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-63828 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63833 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63834 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63835 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63836 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63861 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63862 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63895 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63905 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63908 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63909 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-63915 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-63930 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63931 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63933 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63934 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63949 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63959 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63960 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63967 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64010 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64022 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64023 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64033 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64055 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64056 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-64082 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64084 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64086 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64088 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64089 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-64095 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64096 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64108 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64138 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64148 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64218 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64318 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64389 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64391 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64392 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64394 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64395 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64397 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64398 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64399 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64400 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64420 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64443 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64444 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64445 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64461 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64462 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64468 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64469 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64484 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64493 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64494 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64495 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64497 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64500 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64503 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64504 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64505 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64518 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-139.139 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64528 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64532 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64533 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64536 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64550 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64568 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64580 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64581 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64584 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64585 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64586 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64587 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64590 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64593 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64594 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64599 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64602 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64603 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64604 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68081 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68082 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68083 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68084 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68088 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68097 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68151 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68179 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68192 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68203 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68213 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68220 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68221 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68223 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68225 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68280 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68302 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68303 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68327 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68340 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68359 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68361 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68476 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72140 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72306 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72378 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72501 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74564 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74690 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74691 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-80555 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80727 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80730 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80731 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80732 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80733 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80737 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80738 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80739 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80742 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80743 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80744 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80747 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80752 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80754 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80755 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80756 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80757 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80761 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80762 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80763 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80764 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80765 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80766 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80767 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80768 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80770 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80771 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80772 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80774 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80780 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80781 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80782 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80783 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80784 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80785 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80786 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80789 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80790 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80791 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80792 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80793 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80794 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80795 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80796 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80797 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80798 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80799 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80800 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80801 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80802 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80803 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80805 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80806 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80807 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80808 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80809 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80812 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80814 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80815 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80817 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80819 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80820 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80822 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80823 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80824 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80825 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80826 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80827 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80828 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80829 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80830 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80831 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80832 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80833 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80834 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80835 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80836 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80837 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80838 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80839 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80840 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80841 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80842 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80843 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80844 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80846 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80847 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80848 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80849 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80850 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80851 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80852 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80854 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80855 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80856 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80861 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80864 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80865 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80866 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80867 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80870 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80872 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80875 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80876 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80877 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80878 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80879 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80880 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80881 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80883 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80884 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80886 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80887 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80888 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80890 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80891 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80892 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80893 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80899 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80901 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80902 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80904 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80905 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80906 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80907 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80908 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80909 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80910 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80911 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80912 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80913 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80914 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80916 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80917 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80918 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80920 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80921 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80922 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80923 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80925 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-81003 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-81007 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89562 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89618 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39986 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39988 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40202 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40262 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40266 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-106.106 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31396 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31587 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31761 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43207 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43232 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43249 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43256 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43283 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43291 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43324 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43497 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46250 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46265 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46270 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-47329 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-124.124 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-47330 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-124.124 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-47336 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-124.124 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53160 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53161 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53216 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53217 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53247 | NONE0 | linux-libc-dev 6.8.0-79.79 fixed in 6.8.0-138.138 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53273 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63827 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64449 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64583 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64598 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-68124 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-68314 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68370 | NONE0 | linux-libc-dev 6.8.0-79.79 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-7017 | NONE0 | perl 5.38.2-3.2ubuntu0.2 fixed in 5.38.2-3.2ubuntu0.4 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-7017 | NONE0 | perl-base 5.38.2-3.2ubuntu0.2 fixed in 5.38.2-3.2ubuntu0.4 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-7017 | NONE0 | perl-modules-5.38 5.38.2-3.2ubuntu0.2 fixed in 5.38.2-3.2ubuntu0.4 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-85091 | NONE0 | zlib1g 1:1.3.dfsg-3.1ubuntu2.2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-85091 | NONE0 | zlib1g-dev 1:1.3.dfsg-3.1ubuntu2.2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-0913 | NONE0 | stdlib v1.23.4 fixed in 1.23.10, 1.24.4 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-58188 | NONE0 | stdlib v1.23.4 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Not Applicable |
Which CVEs are actually reachable — is the vulnerable code even linked and callable.
Live-container probes: default user, writable paths, capabilities, exposed ports.
Base-image lineage, package provenance and signatures — nothing slipped in unnoticed.
A step-by-step hardened build plan, with parity tests proving nothing breaks.
Want to check another image? Run a full scan with the Docker Security Scanner.