This image is acceptable for production, but remediating the identified vulnerabilities is recommended to reduce the attack surface. The top findings (CVE-2026-45447 and CVE-2026-45445) affect OpenSSL and could lead to remote code execution or confidentiality loss, but they are only exploitable if the container's application uses the specific vulnerable APIs (PKCS7_verify or EVP_Cipher with AES-OCB). Reviewing the application's OpenSSL usage and disabling unnecessary features fully mitigates these risks. The majority of the 75 exposed vulnerabilities are low severity, and the 56 post-exploit vulnerabilities pose minimal threat with a max severity of 3.3.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-45447 | MEDIUM6.48 | libssl3t64 3.0.13-0ubuntu3.9 fixed in 3.0.13-0ubuntu3.11 | 1.4% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2026-45445 | MEDIUM6.18 | libssl3t64 3.0.13-0ubuntu3.9 fixed in 3.0.13-0ubuntu3.11 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2017-13716 | MEDIUM5.5 | libbinutils 2.42-4ubuntu2.10 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libctf-nobfd0 2.42-4ubuntu2.10 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libctf0 2.42-4ubuntu2.10 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libgprofng0 2.42-4ubuntu2.10 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libsframe1 2.42-4ubuntu2.10 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-40226 | MEDIUM5.44 | libsystemd0 255.4-1ubuntu8.15 fixed in 255.4-1ubuntu8.16 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40226 | MEDIUM5.44 | libudev1 255.4-1ubuntu8.15 fixed in 255.4-1ubuntu8.16 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34182 | MEDIUM5.03 | libssl3t64 3.0.13-0ubuntu3.9 fixed in 3.0.13-0ubuntu3.11 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2024-2236 | MEDIUM4.72 | libgcrypt20 1.10.3-2ubuntu0.1 No fix yet | 1.1% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2025-69651 | MEDIUM4.67 | libbinutils 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libctf-nobfd0 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libctf0 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libgprofng0 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libsframe1 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-7383 | MEDIUM4.67 | libssl3t64 3.0.13-0ubuntu3.9 fixed in 3.0.13-0ubuntu3.11 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc-dev-bin 2.39-0ubuntu8.7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc6 2.39-0ubuntu8.7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc6-dev 2.39-0ubuntu8.7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42766 | MEDIUM4.5 | libssl3t64 3.0.13-0ubuntu3.9 fixed in 3.0.13-0ubuntu3.11 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42767 | MEDIUM4.5 | libssl3t64 3.0.13-0ubuntu3.9 fixed in 3.0.13-0ubuntu3.11 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM4.42 | libc-bin 2.39-0ubuntu8.7 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-4437 | MEDIUM4.42 | libc6 2.39-0ubuntu8.7 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-34180 | MEDIUM4.25 | libssl3t64 3.0.13-0ubuntu3.9 fixed in 3.0.13-0ubuntu3.11 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libblkid1 2.39.3-9ubuntu6.5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libmount1 2.39.3-9ubuntu6.5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libsmartcols1 2.39.3-9ubuntu6.5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libuuid1 2.39.3-9ubuntu6.5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | libc-bin 2.39-0ubuntu8.7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | libc-dev-bin 2.39-0ubuntu8.7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | libc6 2.39-0ubuntu8.7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | libc6-dev 2.39-0ubuntu8.7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2017-13716 | LOW3.3 | binutils 2.42-4ubuntu2.10 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2017-13716 | LOW3.3 | binutils-common 2.42-4ubuntu2.10 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2017-13716 | LOW3.3 | binutils-x86-64-linux-gnu 2.42-4ubuntu2.10 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1152 | LOW3.15 | libbinutils 2.42-4ubuntu2.10 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libctf-nobfd0 2.42-4ubuntu2.10 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libctf0 2.42-4ubuntu2.10 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libgprofng0 2.42-4ubuntu2.10 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libsframe1 2.42-4ubuntu2.10 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-45446 | LOW3.15 | libssl3t64 3.0.13-0ubuntu3.9 fixed in 3.0.13-0ubuntu3.11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42770 | LOW3.01 | libssl3t64 3.0.13-0ubuntu3.9 fixed in 3.0.13-0ubuntu3.11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-9076 | LOW3.01 | libssl3t64 3.0.13-0ubuntu3.9 fixed in 3.0.13-0ubuntu3.11 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-45447 | LOW2.92 | openssl 3.0.13-0ubuntu3.9 fixed in 3.0.13-0ubuntu3.11 | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2025-45582 | LOW2.86 | tar 1.35+dfsg-3build1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | binutils 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | binutils-common 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | binutils-x86-64-linux-gnu 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-7383 | LOW2.8 | openssl 3.0.13-0ubuntu3.9 fixed in 3.0.13-0ubuntu3.11 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-45261 | LOW2.8 | patch 2.7.6-7build3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW2.8 | libbinutils 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libbinutils 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libbinutils 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libctf-nobfd0 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libctf-nobfd0 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libctf-nobfd0 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libctf0 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libctf0 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libctf0 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libgprofng0 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libgprofng0 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libgprofng0 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libsframe1 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libsframe1 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libsframe1 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libsystemd0 255.4-1ubuntu8.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libudev1 255.4-1ubuntu8.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45445 | LOW2.78 | openssl 3.0.13-0ubuntu3.9 fixed in 3.0.13-0ubuntu3.11 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2018-6952 | LOW2.7 | patch 2.7.6-7build3 No fix yet | 8.7% Low-Moderate Risk | Post-Exploit |
| CVE-2026-4046 | LOW2.7 | libc-bin 2.39-0ubuntu8.7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34743 | LOW2.7 | 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-42766 | LOW2.7 | openssl 3.0.13-0ubuntu3.9 fixed in 3.0.13-0ubuntu3.11 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-42767 | LOW2.7 | openssl 3.0.13-0ubuntu3.9 fixed in 3.0.13-0ubuntu3.11 | 0.3% 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-2026-34180 | LOW2.55 | openssl 3.0.13-0ubuntu3.9 fixed in 3.0.13-0ubuntu3.11 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | bsdutils 1:2.39.3-9ubuntu6.5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | mount 2.39.3-9ubuntu6.5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | util-linux 2.39.3-9ubuntu6.5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69644 | LOW2.38 | libbinutils 2.42-4ubuntu2.10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libbinutils 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libbinutils 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW2.38 | libctf-nobfd0 2.42-4ubuntu2.10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libctf-nobfd0 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libctf-nobfd0 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW2.38 | libctf0 2.42-4ubuntu2.10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libctf0 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libctf0 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW2.38 | libgprofng0 2.42-4ubuntu2.10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libgprofng0 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libgprofng0 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW2.38 | libsframe1 2.42-4ubuntu2.10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libsframe1 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libsframe1 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-34182 | LOW2.26 | openssl 3.0.13-0ubuntu3.9 fixed in 3.0.13-0ubuntu3.11 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6238 | LOW1.99 | libc-bin 2.39-0ubuntu8.7 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-4437 | LOW1.99 | libc-dev-bin 2.39-0ubuntu8.7 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6238 | LOW1.99 | libc-dev-bin 2.39-0ubuntu8.7 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6238 | LOW1.99 | libc6 2.39-0ubuntu8.7 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-4437 | LOW1.99 | libc6-dev 2.39-0ubuntu8.7 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6238 | LOW1.99 | libc6-dev 2.39-0ubuntu8.7 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils 2.42-4ubuntu2.10 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils-common 2.42-4ubuntu2.10 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils-x86-64-linux-gnu 2.42-4ubuntu2.10 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-45446 | LOW1.89 | openssl 3.0.13-0ubuntu3.9 fixed in 3.0.13-0ubuntu3.11 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56433 | LOW1.84 | login 1:4.13+dfsg1-4ubuntu3.2 No fix yet | 0.4% 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-5435 | LOW1.81 | libc-bin 2.39-0ubuntu8.7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-5435 | LOW1.81 | libc-dev-bin 2.39-0ubuntu8.7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-5435 | LOW1.81 | libc6 2.39-0ubuntu8.7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-5435 | LOW1.81 | libc6-dev 2.39-0ubuntu8.7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-42770 | LOW1.81 | openssl 3.0.13-0ubuntu3.9 fixed in 3.0.13-0ubuntu3.11 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-9076 | LOW1.81 | openssl 3.0.13-0ubuntu3.9 fixed in 3.0.13-0ubuntu3.11 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.68 | binutils 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.68 | binutils 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.68 | binutils-common 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.68 | binutils-common 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils-common 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.68 | binutils-x86-64-linux-gnu 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.68 | binutils-x86-64-linux-gnu 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils-x86-64-linux-gnu 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69644 | LOW1.43 | binutils 2.42-4ubuntu2.10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.43 | binutils 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.43 | binutils 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69644 | LOW1.43 | binutils-common 2.42-4ubuntu2.10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.43 | binutils-common 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.43 | binutils-common 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69644 | LOW1.43 | binutils-x86-64-linux-gnu 2.42-4ubuntu2.10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.43 | binutils-x86-64-linux-gnu 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.43 | binutils-x86-64-linux-gnu 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-43037 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-23395 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31788 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31402 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-23428 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43284 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-124.124 | 92.2% Actively Exploited | Not Applicable |
| CVE-2026-43378 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43500 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-124.124 | 94.0% Actively Exploited | Not Applicable |
| CVE-2026-46274 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46300 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-124.124 | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2026-46323 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-124.124 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46333 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-124.124 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2013-7445 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 2.7% Low-Moderate Risk | Not Applicable |
| CVE-2020-14356 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2022-3238 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50090 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50240 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-0030 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-26242 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27022 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38581 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-40954 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-44932 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44951 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44964 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46820 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46833 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53098 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21687 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37882 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38069 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38082 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38091 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38187 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38206 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38421 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38563 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-38565 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39859 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39862 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39896 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39958 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40014 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71073 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71152 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71238 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23171 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23208 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23221 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23226 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-23227 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23233 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23234 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23319 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23343 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23344 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23359 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23361 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23378 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23387 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23390 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23412 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23413 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23447 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23448 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31399 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31452 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31455 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31474 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31485 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31488 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31489 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31493 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31500 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31506 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31527 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31530 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31532 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31566 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31576 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31578 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31580 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31581 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31582 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31583 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31686 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31688 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31696 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31702 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31709 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31715 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31720 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31729 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31730 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31731 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31747 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31748 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31759 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31776 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43007 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43015 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43020 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43027 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43049 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43120 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43128 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43150 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43196 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43205 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43250 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43328 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43426 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43458 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45946 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45984 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45989 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45996 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45998 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-124.124 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46004 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46047 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46163 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46180 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46189 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46219 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46234 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46241 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46243 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46331 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2017-13165 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2018-12930 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-12931 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-19378 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2019-19814 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 3.3% Low-Moderate Risk | Not Applicable |
| CVE-2021-26934 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-33053 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-50217 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46246 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46267 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43501 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31669 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43186 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-46195 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-0400 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2022-25836 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40210 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43110 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43190 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-20426 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2025-40170 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2019-14899 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-43038 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31607 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-23243 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43074 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43248 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46244 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46135 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-23455 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46259 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50551 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53216 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58015 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21985 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22104 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38204 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38329 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38330 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38340 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38636 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40064 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68324 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68356 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71231 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23235 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23244 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23315 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23318 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23325 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23327 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23363 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23388 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23397 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31430 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31568 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31613 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31614 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31685 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31778 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43040 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43051 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43052 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43056 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43126 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43141 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43241 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43281 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43330 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43380 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43386 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43427 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43449 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43450 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43453 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45957 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45994 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46022 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46033 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46053 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46056 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46120 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46150 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46191 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46203 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46209 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43414 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43304 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46043 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43198 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43341 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43493 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-45972 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46119 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46185 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46275 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46319 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2021-3864 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2022-1247 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-2961 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50106 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37776 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39905 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40135 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40158 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40168 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71203 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71221 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23270 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23392 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23454 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31408 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31508 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31586 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31663 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31694 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31772 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43023 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43050 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43116 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43158 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43226 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43233 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43303 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43329 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43332 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43334 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43339 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43491 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43494 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-124.124 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43503 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-124.124 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45840 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45852 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45856 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45858 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45859 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-45860 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-45861 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45886 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45892 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45894 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45899 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45910 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45912 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45934 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45942 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45970 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46015 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46052 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46054 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46069 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46076 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46084 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46090 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46099 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46114 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46116 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46117 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46121 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46123 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46125 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46132 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46133 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-46139 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46145 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46149 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46152 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46173 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46174 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46176 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46181 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46227 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46242 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46266 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46306 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46324 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46325 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46330 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-45885 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46251 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46294 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2019-15794 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2023-6238 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-45991 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2015-8553 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-1193 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2025-40336 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68729 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31470 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31588 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43239 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-0564 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-23450 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-40074 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23383 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23456 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31502 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31516 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31525 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45932 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-44034 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40146 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23253 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40190 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40355 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68736 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31449 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31464 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31505 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31511 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31570 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31700 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31708 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43044 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43134 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43321 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43197 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31649 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-3714 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-23246 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2018-1121 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 4.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-23240 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31414 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40203 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40340 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23239 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23271 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23317 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31392 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31426 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43279 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46065 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46113 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46024 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31637 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-45988 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-71315 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31436 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43083 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43084 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43406 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43407 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46273 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46304 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46320 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2015-7837 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2016-8660 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-0480 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-4543 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2022-48846 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48929 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49940 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50230 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50232 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50332 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50380 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-0160 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31082 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-52879 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53642 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-54190 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-14027 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27025 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-35895 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35948 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35995 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41008 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42125 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42139 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43844 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43872 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-46742 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46748 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47729 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49904 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49908 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49910 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49916 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49932 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49940 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49970 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49990 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50003 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50034 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50102 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-52560 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53056 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53064 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53207 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56368 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56544 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56591 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56617 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56639 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56671 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56702 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56712 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57809 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57852 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57875 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57922 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57950 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57976 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58012 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58089 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58094 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58095 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-58098 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-58100 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-58241 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21693 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21696 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21709 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21730 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21751 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21752 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21817 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21819 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21907 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22002 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22043 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22077 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-22108 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-22109 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-22116 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22127 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-23131 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-23132 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-23135 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23162 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37743 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37746 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37747 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37806 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37807 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37833 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37834 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37855 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37870 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37876 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37877 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37880 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37907 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38029 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38033 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38036 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38038 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38041 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38042 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38047 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38064 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38070 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38092 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38096 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38132 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38140 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38168 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38188 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38189 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38199 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38203 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38205 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38207 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38237 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38261 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38272 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38311 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38353 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38359 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38360 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38372 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38426 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38438 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38498 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38597 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38605 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38621 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39677 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39745 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39762 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39764 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39771 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39789 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39833 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39908 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39910 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39925 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39933 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39990 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40005 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40040 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40075 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40086 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40102 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40195 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40334 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40362 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68188 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68193 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68209 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68211 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68212 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68236 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68251 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68281 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68304 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68309 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68317 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68333 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68334 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68353 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68730 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68802 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68822 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71115 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71158 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71161 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71202 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71204 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71223 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71227 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71229 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71232 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71233 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71235 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71236 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71237 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71239 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71265 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71266 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71267 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71269 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71272 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71273 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71285 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71286 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71287 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71288 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71289 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71290 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71291 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71292 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71293 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71294 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71295 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71297 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71299 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71300 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71302 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71305 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-22981 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22985 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22993 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23017 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23066 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23100 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23104 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23137 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23138 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23152 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23154 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23157 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23196 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23201 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23217 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23220 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23222 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23228 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23229 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23230 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23236 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23237 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23238 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23241 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23242 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-23247 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23248 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23249 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23255 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23259 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23265 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23266 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23267 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23272 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23276 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23277 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23278 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23279 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23284 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23285 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23286 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23287 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23289 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23290 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23291 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23292 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23293 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23296 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23298 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23300 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23303 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23304 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23306 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23307 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23308 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23310 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23312 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23313 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23321 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23324 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23330 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23334 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23335 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23336 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23339 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23340 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23346 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23347 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23352 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23356 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23357 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23360 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23362 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23365 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23367 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23368 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23369 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23370 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23371 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23374 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23375 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23377 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23379 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23381 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23382 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23386 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23389 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23391 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23396 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23398 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23399 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23401 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23414 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23418 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23419 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23420 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23426 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23434 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23438 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23439 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23442 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23444 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23446 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23449 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23460 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23461 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23462 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-23464 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23465 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23468 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23470 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23472 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23474 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23475 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31391 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31394 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31400 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31403 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31407 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31410 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31411 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31412 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31415 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31416 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31418 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31420 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31421 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31422 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31423 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31424 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31425 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31427 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31428 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31429 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31434 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31438 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31439 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31440 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31441 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31446 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31447 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31450 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31451 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31453 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31454 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31458 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31461 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31462 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31467 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31469 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31473 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31479 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31480 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31482 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31483 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31486 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31487 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31492 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31495 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31496 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31497 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31498 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31499 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31503 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31507 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31509 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31510 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31512 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31515 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31518 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31519 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31520 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31521 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31522 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31524 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31526 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31528 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31531 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31537 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31540 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31542 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31545 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31546 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31548 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31549 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31550 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31551 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31552 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31554 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31555 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31556 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31557 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31560 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31565 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31575 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31577 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31579 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31585 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31590 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31592 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31594 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31595 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31596 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31599 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31603 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31604 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31605 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31606 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31610 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31615 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31616 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31617 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31618 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31619 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31623 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31624 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31625 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31628 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31630 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31634 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31638 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31639 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31642 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31645 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31646 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31648 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31651 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31655 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31658 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31660 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31661 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31662 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31664 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31665 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31667 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31670 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31671 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31672 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31673 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31674 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31675 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31676 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-124.124 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31677 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31678 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31679 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31680 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31681 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31682 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31684 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31687 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31689 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31692 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31693 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31698 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31699 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31701 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31704 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31714 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31721 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31722 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31723 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31724 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31725 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31726 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31737 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31738 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31740 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31741 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31749 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31752 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31754 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31755 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31756 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31758 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31762 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31763 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31767 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31770 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31771 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31773 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31777 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31779 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31781 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43009 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43010 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43012 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43013 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43014 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43016 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43017 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43018 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43019 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43021 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43022 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43024 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43025 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43026 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43028 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43029 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43030 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43032 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43034 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43035 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43036 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43041 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43042 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43043 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43045 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43046 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43048 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43054 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43057 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43058 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43059 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43060 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43061 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43062 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43064 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43065 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43066 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43068 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43069 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43072 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43073 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43079 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43080 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43081 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43082 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43085 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43086 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43088 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43089 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43091 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43092 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43093 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43094 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43098 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43099 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43101 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43103 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43104 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43105 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43107 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43109 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43111 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43112 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43113 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43114 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43115 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43118 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43119 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43123 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43124 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43127 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43129 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43130 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43131 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43132 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43133 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43135 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43136 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43137 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43139 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43140 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43143 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43145 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43147 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43148 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43149 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43152 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43153 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43156 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43157 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43159 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43161 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43162 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43165 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43167 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43168 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43169 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43170 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43171 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43172 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43173 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43175 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43176 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43180 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43182 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43183 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43187 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43189 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43191 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43194 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43195 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43199 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43200 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43201 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43202 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43204 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43209 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43211 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43213 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43214 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43215 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43216 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43218 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43219 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43220 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43221 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43223 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43225 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43227 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43228 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43229 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43230 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43231 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43234 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43238 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43240 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43242 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43243 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43244 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43246 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43251 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43252 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43253 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43255 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43257 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43261 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43262 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43264 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43265 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43266 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43267 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43268 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43269 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43270 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43271 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43273 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43277 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43278 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43287 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43288 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43289 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43292 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43294 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43295 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43296 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43297 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43298 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43299 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43300 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43301 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43302 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43305 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43306 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43308 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43309 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43310 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43311 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43312 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43313 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43314 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43315 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43316 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43317 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43318 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43319 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43320 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43327 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43331 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43333 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43338 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43340 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43343 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43344 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43345 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43350 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43352 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43353 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43355 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43357 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43359 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43360 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43361 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43362 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43363 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43365 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43366 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43371 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43372 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43381 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43382 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43387 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43395 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43397 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43398 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43400 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43405 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43408 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43409 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43410 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43411 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43412 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43413 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43416 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43419 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43420 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43421 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43424 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43425 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43428 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43429 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43432 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43436 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43437 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43441 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43443 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43445 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43451 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43452 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43455 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43456 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43457 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43459 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43463 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43464 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43466 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43467 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43468 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43469 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43471 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43472 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43473 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43474 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43475 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43483 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43484 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43488 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43492 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43496 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43502 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45834 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45835 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45836 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45838 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45841 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45842 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45843 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-45844 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45845 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45846 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45847 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45851 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45855 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45857 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45862 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45868 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45870 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45871 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45872 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45873 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45877 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45880 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45891 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45895 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45897 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45901 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45904 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45905 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45911 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45913 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45914 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45915 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45917 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45919 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45920 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45923 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45941 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45943 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45944 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45947 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45948 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45954 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45960 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45961 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45962 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45963 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45964 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45965 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45968 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45969 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45973 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45974 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45976 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45978 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45981 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45982 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45983 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45985 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45986 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45987 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45997 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45999 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46000 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-124.124 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46002 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46003 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46005 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46007 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46009 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46012 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46014 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46016 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46018 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46019 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46021 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46023 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46026 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46027 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46032 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46037 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46038 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46040 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46041 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46044 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46046 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46049 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46050 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46051 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46059 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46061 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46063 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46064 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46066 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46068 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46070 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46071 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46078 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46079 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46082 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46083 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46086 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46088 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46089 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46092 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46094 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46101 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46102 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46103 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46106 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46107 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46111 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46115 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46126 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46127 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46130 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46131 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46136 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46137 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46138 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46144 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46146 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46148 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46151 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46153 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46157 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46158 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46160 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46161 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46167 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46168 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46169 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46170 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46171 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46172 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46178 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46179 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46184 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46186 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46190 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46193 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46196 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46200 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46201 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46207 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46211 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46214 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46220 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46225 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46226 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46229 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46231 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46233 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46235 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46236 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46247 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46260 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46289 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46302 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46315 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46321 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46322 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2017-13693 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-12928 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-12929 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-71313 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31448 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43071 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43465 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46147 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46245 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46249 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46252 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46253 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46254 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46255 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46261 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46280 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46291 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46292 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46299 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46307 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46312 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23457 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40217 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40338 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40344 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39293 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-42107 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56552 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-56788 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-57857 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21984 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37906 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38242 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38440 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38717 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39754 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39884 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40139 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68239 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68296 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68745 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71074 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71274 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23004 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23118 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23169 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23181 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23207 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23302 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23348 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23440 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23441 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23452 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23463 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23469 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31389 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31393 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31466 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31523 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31697 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31728 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31751 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43047 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43053 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43163 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43275 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43342 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43383 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43415 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43430 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43439 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43448 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45949 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46159 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46187 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46194 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2017-0537 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-46272 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2019-15213 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-4010 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-68360 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2018-17977 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-68768 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23458 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2020-14304 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-41848 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2020-35501 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31668 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43011 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43185 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-54518 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31405 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31413 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31478 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31536 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31657 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31659 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31705 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-47331 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-124.124 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-47333 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-124.124 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-54105 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54187 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40003 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40012 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40025 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40054 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40065 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40073 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40097 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40098 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40136 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40150 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40208 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40247 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40274 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40332 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40335 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40354 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40356 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-54505 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-62626 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68174 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68175 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68196 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68230 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68318 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68338 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68376 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68781 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71304 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23245 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23281 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23364 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-23372 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23393 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31396 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31409 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31417 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31432 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31433 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-31476 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31477 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31494 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31563 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31584 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31587 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31597 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31598 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31602 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31611 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31612 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31622 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31626 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31627 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31629 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31656 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31683 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31695 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31706 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31707 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31711 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31712 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31716 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31761 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31768 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31769 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31780 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43075 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43076 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43117 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43184 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43203 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43206 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43207 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43222 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43232 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43236 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43237 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43245 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43249 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43256 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43263 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43274 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43283 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43291 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43324 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43336 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43368 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43370 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43373 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43377 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43384 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43476 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43480 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43485 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43490 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43495 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43497 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43499 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45839 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45848 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45849 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45850 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45864 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45865 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45866 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45867 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45869 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45875 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45878 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45879 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45881 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45882 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45883 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45884 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45885 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45890 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45893 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45902 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45916 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45921 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45924 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45928 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45930 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45935 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45936 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45938 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45940 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45956 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45958 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46006 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46011 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46031 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46058 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46062 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46072 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46073 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46075 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46077 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46080 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46091 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46098 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46108 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46110 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46112 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46118 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46122 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46124 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46128 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46129 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46142 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46143 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46164 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46175 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46177 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46197 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46198 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46199 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46204 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46205 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46206 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46208 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46212 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46218 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46230 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46232 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46238 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46303 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46314 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46328 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-47326 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-124.124 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-47327 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-124.124 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-47328 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-124.124 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-47332 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-124.124 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-47334 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-124.124 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-47335 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-124.124 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-47337 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-124.124 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46250 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46265 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46270 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46282 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46285 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46286 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46287 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46293 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46296 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46301 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-47329 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-124.124 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-47330 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-124.124 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-47336 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-124.124 | <0.1% Theoretical Threat | Not Applicable |