Last scanned:
··This image is safe for production use. The scan did report vulnerabilities, including 70 on the exposed surface and 29 that matter only after compromise, but all of them are low severity and none is known to be actively exploited, so they do not drive the verdict. The image exposes no network ports, which further limits how these issues could be reached in normal operation. Routine patching of the CUDA base image as new releases appear is still good practice.
Already in good shape · 2 hardening steps left
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2025-69651 | MEDIUM5.5 | libbinutils 2.42-4ubuntu2.10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM5.5 | libctf-nobfd0 2.42-4ubuntu2.10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM5.5 | libctf0 2.42-4ubuntu2.10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM5.5 | libgprofng0 2.42-4ubuntu2.10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM5.5 | libsframe1 2.42-4ubuntu2.10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.9 | libc-bin 2.39-0ubuntu8.9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.9 | libc-dev-bin 2.39-0ubuntu8.9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.9 | libc6 2.39-0ubuntu8.9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.9 | libc6-dev 2.39-0ubuntu8.9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | MEDIUM4.2 | libc-bin 2.39-0ubuntu8.9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | MEDIUM4.2 | libc-dev-bin 2.39-0ubuntu8.9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | MEDIUM4.2 | libc6 2.39-0ubuntu8.9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | MEDIUM4.2 | libc6-dev 2.39-0ubuntu8.9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-88647 | MEDIUM4.14 | libgnutls30t64 3.8.3-1.1ubuntu3.6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-88648 | MEDIUM4.14 | libgnutls30t64 3.8.3-1.1ubuntu3.6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-103111 | MEDIUM4.14 | libpcre2-8-0 10.42-4ubuntu2.2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86145 | MEDIUM4.14 | libpcre2-8-0 10.42-4ubuntu2.2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-89157 | MEDIUM4.14 | libpcre2-8-0 10.42-4ubuntu2.2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-89161 | MEDIUM4.14 | libpcre2-8-0 10.42-4ubuntu2.2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-107161 | MEDIUM4.14 | libsasl2-2 2.1.28+dfsg1-5ubuntu3.1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107161 | MEDIUM4.14 | libsasl2-modules-db 2.1.28+dfsg1-5ubuntu3.1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-89158 | LOW3.9 | libpcre2-8-0 10.42-4ubuntu2.2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89160 | LOW3.9 | libpcre2-8-0 10.42-4ubuntu2.2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2017-13716 | LOW3.9 | libbinutils 2.42-4ubuntu2.10 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | LOW3.9 | libctf-nobfd0 2.42-4ubuntu2.10 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | LOW3.9 | libctf0 2.42-4ubuntu2.10 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | LOW3.9 | libgprofng0 2.42-4ubuntu2.10 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | LOW3.9 | libsframe1 2.42-4ubuntu2.10 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-67693 | LOW3.54 | libgnutls30t64 3.8.3-1.1ubuntu3.6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89156 | LOW3.54 | libpcre2-8-0 10.42-4ubuntu2.2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | LOW3.3 | binutils 2.42-4ubuntu2.10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW3.3 | binutils-x86-64-linux-gnu 2.42-4ubuntu2.10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-102473 | LOW3.3 | dash 0.5.12-6ubuntu5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW3.3 | libbinutils 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW3.3 | libbinutils 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW3.3 | libbinutils 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW3.3 | libctf-nobfd0 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW3.3 | libctf-nobfd0 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW3.3 | libctf-nobfd0 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW3.3 | libctf0 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW3.3 | libctf0 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW3.3 | libctf0 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW3.3 | libgprofng0 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW3.3 | libgprofng0 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW3.3 | libgprofng0 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW3.3 | libsframe1 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW3.3 | libsframe1 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW3.3 | libsframe1 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW3.3 | libsystemd0 255.4-1ubuntu8.18 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW3.3 | libudev1 255.4-1ubuntu8.18 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-95184 | LOW3.18 | libgnutls30t64 3.8.3-1.1ubuntu3.6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| 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-95209 | LOW3 | libgnutls30t64 3.8.3-1.1ubuntu3.6 No fix yet | — | Directly Exposed |
| CVE-2026-95210 | LOW3 | libgnutls30t64 3.8.3-1.1ubuntu3.6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW2.8 | libbinutils 2.42-4ubuntu2.10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.8 | libbinutils 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.8 | libbinutils 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW2.8 | libctf-nobfd0 2.42-4ubuntu2.10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.8 | libctf-nobfd0 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.8 | libctf-nobfd0 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW2.8 | libctf0 2.42-4ubuntu2.10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.8 | libctf0 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.8 | libctf0 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW2.8 | libgprofng0 2.42-4ubuntu2.10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.8 | libgprofng0 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.8 | libgprofng0 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW2.8 | libsframe1 2.42-4ubuntu2.10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.8 | libsframe1 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.8 | libsframe1 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18477 | LOW2.64 | tar 1.35+dfsg-3ubuntu0.4 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-18508 | LOW2.64 | tar 1.35+dfsg-3ubuntu0.4 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-102474 | LOW2.4 | dash 0.5.12-6ubuntu5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2017-13716 | LOW2.34 | binutils 2.42-4ubuntu2.10 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2017-13716 | LOW2.34 | binutils-x86-64-linux-gnu 2.42-4ubuntu2.10 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2018-6952 | LOW2.34 | patch 2.7.6-7build3 No fix yet | 8.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-20633 | LOW2.34 | patch 2.7.6-7build3 No fix yet | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-56288 | LOW2.34 | patch 2.7.6-7build3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-56289 | LOW2.34 | patch 2.7.6-7build3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2021-45261 | LOW1.99 | patch 2.7.6-7build3 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.98 | binutils 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.98 | binutils 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.98 | binutils 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.98 | binutils-x86-64-linux-gnu 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.98 | binutils-x86-64-linux-gnu 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.98 | binutils-x86-64-linux-gnu 2.42-4ubuntu2.10 No fix yet | 0.2% 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-x86-64-linux-gnu 2.42-4ubuntu2.10 No fix yet | 0.6% 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-2025-69644 | LOW1.68 | binutils 2.42-4ubuntu2.10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.68 | binutils 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.68 | binutils 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69644 | LOW1.68 | binutils-x86-64-linux-gnu 2.42-4ubuntu2.10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.68 | binutils-x86-64-linux-gnu 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.68 | binutils-x86-64-linux-gnu 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63825 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-90037 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-93221 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74744 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74752 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89676 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80725 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89526 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89631 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-93787 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89633 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2022-50240 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38581 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-40954 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-44964 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46833 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71073 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23208 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80714 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89638 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93817 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98260 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98524 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98741 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68470 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98621 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98725 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40025 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40274 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23393 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31536 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43263 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43379 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53024 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53178 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53401 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63819 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89788 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89803 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89922 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90048 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-93792 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98084 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98171 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-98442 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98490 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-98532 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-98548 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-98573 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98805 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40170 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68426 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-97415 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38204 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40064 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43042 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64078 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68198 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-68409 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74510 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89481 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-97493 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97497 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64523 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89530 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89652 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89659 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89708 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-98365 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-37776 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40158 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-40168 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46181 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46330 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52991 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53250 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63879 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68245 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68257 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68323 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68401 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68404 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68451 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-72111 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72288 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74269 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74446 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74506 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74533 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74534 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74537 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74684 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74724 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80668 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-80681 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80693 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80700 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80702 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80710 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80716 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80718 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80837 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80841 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80852 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80864 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89528 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89537 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89550 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89564 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89580 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89637 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89675 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89680 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89685 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-90093 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90104 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-90111 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90161 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90227 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90237 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90317 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90343 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90380 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-90392 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90398 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-92511 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-92512 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93105 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93148 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93154 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97429 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97555 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-97564 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98033 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98034 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98041 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98222 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98283 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98341 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98364 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98606 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98733 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98754 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2013-7445 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 2.8% Low-Moderate Risk | Not Applicable |
| CVE-2020-14356 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2021-3864 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2022-0400 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2022-1247 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-25836 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-2961 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-3238 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50090 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50551 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-0030 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-26242 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54187 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-14040 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27022 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50106 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-53098 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53216 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40354 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68356 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31479 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31568 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46324 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52953 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52956 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-53000 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53009 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53091 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53109 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53179 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63962 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64017 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64117 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64160 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64255 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64283 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64563 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68118 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68138 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68159 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-68166 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68169 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68253 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68266 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68273 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68289 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68374 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68452 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68453 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68480 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72098 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-72398 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-72463 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-72499 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74440 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74443 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74469 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2026-74476 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74480 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-74488 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74492 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74493 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74496 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74498 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74499 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74516 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74518 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74541 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74556 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74557 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74563 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74569 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74574 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74575 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74580 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74581 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74582 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74583 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74586 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74587 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74588 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74597 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74598 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74608 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74609 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74611 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74612 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74615 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74616 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74621 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74630 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74631 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74637 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74641 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74656 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74661 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74662 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74669 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74688 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74695 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74705 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74720 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74737 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-74743 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74746 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80521 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80536 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80552 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80553 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80558 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80561 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80584 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80585 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-80586 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80590 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-80722 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80780 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80792 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80824 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80840 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80842 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80844 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80848 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80849 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80850 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80863 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80878 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80887 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80914 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80921 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80951 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80971 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80976 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-80977 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80989 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-81000 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-81002 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-81003 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89444 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89476 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89477 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89478 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89479 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89480 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89482 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89485 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89487 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89488 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89495 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89508 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89524 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89532 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89533 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89536 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89542 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89545 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89548 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89551 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89555 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89559 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89560 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89563 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89569 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89583 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89596 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89606 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89607 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89609 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89617 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89625 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89643 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89650 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89653 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89656 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89662 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89663 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89669 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89671 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89672 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89674 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89690 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89691 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89693 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89694 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89697 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89704 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89712 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89725 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89729 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89736 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89746 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89761 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89777 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89779 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89783 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89811 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89846 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89894 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89932 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89970 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-90011 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-90049 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90071 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90099 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90102 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-90110 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-90151 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-90207 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90230 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-90284 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90292 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90294 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-90307 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90347 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90399 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90413 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-90435 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-92489 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-92495 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92508 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93054 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93095 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93207 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-93262 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93283 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93288 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93800 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93812 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93813 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97417 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-97422 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97476 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97524 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-97528 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-97561 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97563 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97573 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-97575 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97583 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-97584 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97594 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97602 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97611 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97620 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97926 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97931 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97934 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97936 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97940 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97954 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97990 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97991 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98037 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98066 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98068 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98069 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-98070 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-98108 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98116 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98122 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98130 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-98155 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98173 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98176 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98186 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98197 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98204 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98205 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98216 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98221 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98230 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98236 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98238 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98239 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-98241 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98246 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98247 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98249 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98251 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98252 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98254 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98261 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-98262 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98266 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98276 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98282 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98287 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98290 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98295 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98299 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98306 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98312 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98314 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98320 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98323 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-98330 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98331 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98339 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98343 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98347 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98357 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-98358 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98362 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98366 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98367 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98368 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98370 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98373 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98374 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98378 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98379 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98380 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98417 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98426 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98428 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98429 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98550 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-98614 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98716 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98769 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98853 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98857 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99999 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-74697 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90203 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90414 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-98499 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-98612 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93125 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93144 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98589 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98590 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98591 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98599 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2019-15794 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-89579 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98808 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80945 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89640 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-90255 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-68729 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74385 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89707 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-98167 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98439 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98454 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-98457 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98479 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-98526 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98704 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98794 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98803 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98829 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-1193 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-80819 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80901 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89511 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89538 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89541 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89665 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89696 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-89973 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-98452 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98482 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98582 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98597 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98705 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40074 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-45932 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90333 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98039 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89965 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80691 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-98634 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98763 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98836 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80788 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98185 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98481 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98545 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98575 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98828 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40190 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68103 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40355 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80952 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89649 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89778 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89786 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89858 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89959 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90054 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90068 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98760 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98810 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90256 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98432 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-98491 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98561 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98570 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98586 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98792 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-3714 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2026-74474 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74624 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74692 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-93107 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-98485 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98852 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23239 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23240 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89448 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40203 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93101 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80836 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89995 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-98464 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98863 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69651 | NONE0 | binutils-common 2.42-4ubuntu2.10 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-90162 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-35948 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46742 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-52560 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56591 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-58098 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58100 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22043 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-37743 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39933 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40075 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-68251 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68304 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68730 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71202 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71315 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-100074 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23265 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23377 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23385 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31410 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31692 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43009 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43034 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43048 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43213 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43464 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-45940 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52946 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53281 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53377 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64036 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64052 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64077 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68152 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68447 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68471 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-72162 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72198 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72375 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72380 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-72413 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72423 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72472 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72493 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-72494 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74257 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74268 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-74314 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74317 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74334 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74344 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74347 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74350 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74388 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74454 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74465 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74470 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74522 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74530 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74565 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74578 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74723 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80551 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80554 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80631 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80634 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-80671 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80692 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-80721 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80891 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80905 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80937 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-80980 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-80991 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89492 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89520 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89531 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89544 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89565 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89622 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89837 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90108 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90148 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90149 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-90150 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90152 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90155 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90167 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90169 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90199 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90200 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90204 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90205 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90217 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90313 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90320 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90321 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90324 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90375 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92499 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93175 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93192 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93196 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93199 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93210 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93282 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-93790 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-93796 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93806 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-93824 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93828 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97442 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-97513 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97530 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97562 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-97565 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97581 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97603 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97615 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97906 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97960 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98017 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98019 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98056 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-98085 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98104 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98107 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98115 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98134 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98164 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98332 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98333 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98359 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98420 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98459 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98487 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98503 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98567 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98580 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98624 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98652 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98797 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98837 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98846 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2015-7837 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2016-8660 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-0480 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-4543 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2022-49940 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50380 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-0160 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31082 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-53642 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-14027 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27025 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-35895 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41008 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-43872 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-47729 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49908 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49940 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49990 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50003 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50102 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56702 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-57922 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-57976 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-58089 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58241 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21696 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-21752 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22002 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22108 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-22109 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-23162 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37747 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37806 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37880 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37907 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38029 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38041 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38188 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38189 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38199 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38205 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38237 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38261 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38272 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38359 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38360 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38372 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38498 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38525 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-39677 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39910 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39925 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40040 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40086 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40102 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68211 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68212 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68353 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68802 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68822 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71080 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-71227 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71285 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-100070 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-100071 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-100075 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-100076 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-100077 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-100078 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-100079 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23201 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23247 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23371 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31526 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31531 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31537 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31579 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31592 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31630 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43029 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43115 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43127 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43161 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43172 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43191 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43204 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43220 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43234 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43294 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43299 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43310 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43416 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43463 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45934 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45963 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46014 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46032 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46059 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46066 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46071 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46148 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46153 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46302 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52937 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52972 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52988 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52994 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53018 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53103 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53107 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53139 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53285 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53317 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63853 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63858 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63963 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63983 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63999 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64060 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64070 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64076 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64079 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64190 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64210 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68109 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68113 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68114 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68132 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68241 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68242 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68252 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68254 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68312 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68322 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68367 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68383 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68412 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68418 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68431 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-72009 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-72073 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72200 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72203 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72315 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72321 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72334 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-72345 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72402 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72404 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72438 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-72440 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-72485 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72488 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72495 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72496 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74258 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74261 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74294 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74337 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74338 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74342 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74368 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74444 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74445 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74453 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74455 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74457 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74458 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74459 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74460 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74461 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74463 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74464 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74467 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74468 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74472 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74473 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74475 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74478 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-74479 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74482 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74483 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74484 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74485 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74487 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74494 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74495 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74497 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74500 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74505 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74507 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74508 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74523 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74525 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74531 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74532 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74536 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74538 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74540 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74546 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74547 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74548 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74549 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74550 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74551 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74552 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74555 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74558 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74559 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74560 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74566 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74567 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74572 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74577 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74579 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74590 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74592 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74595 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74599 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74600 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74601 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74602 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74603 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74606 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74607 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74610 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74613 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74618 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74619 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74620 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74622 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74623 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74625 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74626 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74628 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74632 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74634 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74635 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74636 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74638 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74646 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74647 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74648 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74649 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74650 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74651 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74654 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74655 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74657 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74658 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74659 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74663 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74664 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74666 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74667 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74668 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74670 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74671 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74673 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74675 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74676 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74678 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74679 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74680 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74683 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74693 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74694 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74696 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74701 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74704 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74710 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74717 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74718 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74719 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74722 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74726 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74734 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74735 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74736 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74739 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74740 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74747 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74748 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80526 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80527 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80529 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80539 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80540 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80541 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80542 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80547 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80548 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80549 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80550 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80557 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80559 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80560 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80562 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80565 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80566 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80567 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80568 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80569 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80570 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80573 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80574 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80576 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80578 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80581 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80583 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80587 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80670 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-80684 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80686 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80694 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-80695 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80703 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80707 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-80715 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80717 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-80727 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80730 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80733 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80739 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80742 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80743 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80744 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80752 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80754 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80756 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80771 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80784 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80797 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80815 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80828 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80843 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80855 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80856 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80861 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80866 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80888 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80892 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80902 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80906 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80907 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80908 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80909 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80912 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80913 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80916 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80917 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80918 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80920 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80922 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80923 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80925 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80928 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80930 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80931 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80932 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80933 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80935 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-80938 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80939 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80941 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80949 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80963 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80964 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80965 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80966 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80967 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80968 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80969 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80972 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80978 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80983 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80984 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80987 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80988 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80992 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80996 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-81010 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | — | Not Applicable |
| CVE-2026-81012 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-81013 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-81014 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-81016 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-81017 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89438 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89439 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89442 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89443 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89451 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89457 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89461 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89463 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89464 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89466 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89467 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89469 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89470 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89471 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89473 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89474 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89475 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89483 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89484 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89489 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89490 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89491 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89493 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89494 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89496 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89497 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89498 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89500 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89502 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89503 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89504 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89512 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89515 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89525 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89527 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89549 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89554 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89557 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89561 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89562 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89566 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89567 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89572 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89573 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89575 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89576 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89582 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89585 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89586 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89587 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89588 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89594 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89595 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89597 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89598 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89599 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89601 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89604 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89605 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89608 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89615 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89616 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89618 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89621 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89623 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89624 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89626 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89627 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89628 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89644 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89645 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89647 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89673 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89699 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89706 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89710 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89711 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89717 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89720 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89723 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89724 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89726 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89730 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89731 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89732 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89733 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89735 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89742 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89743 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89749 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89750 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89751 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89752 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89753 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89755 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89757 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89759 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89765 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89771 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89780 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89784 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89796 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89800 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89802 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89808 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89813 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89816 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89845 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89851 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89855 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89856 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89863 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89864 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89872 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89874 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89876 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89881 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89884 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89896 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89900 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89901 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89909 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89923 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89924 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89925 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89926 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89927 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89930 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89933 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89953 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89955 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89958 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89961 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89975 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89979 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89982 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89989 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89993 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90007 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90015 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90019 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90020 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90024 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90031 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90034 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90035 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90053 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90055 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90056 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90058 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90061 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90062 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90063 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90066 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90067 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-90070 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90072 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90073 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90074 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90075 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90076 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90078 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90081 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90083 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90087 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90088 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90090 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90091 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90098 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90101 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90103 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-90107 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90109 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90114 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90115 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90119 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90122 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90124 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90125 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90126 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90130 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90137 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90138 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90139 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90140 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90141 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90143 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90146 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90153 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-90154 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90156 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90157 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90158 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90159 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90160 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90166 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90170 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90175 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90176 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-90178 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90179 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90183 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90190 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90198 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90202 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90209 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90213 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90214 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90216 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90218 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90219 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90220 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90221 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90222 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90223 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90224 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90225 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90226 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90228 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-90229 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90231 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90232 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90245 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90248 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90249 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90250 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90251 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90253 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90254 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90257 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90261 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90264 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90265 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90273 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90274 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90275 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90279 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90280 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90281 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90282 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90283 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90285 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90286 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90287 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90289 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90290 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90291 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90293 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-90295 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90296 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90297 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90298 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90300 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90302 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90308 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90309 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90314 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90316 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90318 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90319 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90327 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90330 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90334 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90341 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90345 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90346 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90348 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90352 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90353 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-90354 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90357 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-90358 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90360 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90361 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90362 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90364 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90366 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90368 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90370 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90372 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90374 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90378 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90382 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90386 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90387 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90388 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90390 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90391 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90394 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90395 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90397 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90400 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90403 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-90404 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90407 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90411 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90415 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90416 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90419 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90420 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90431 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90434 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92476 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92477 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92480 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92484 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92488 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-92490 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92494 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92496 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92497 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92498 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92501 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92503 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92504 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-92506 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92514 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92519 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92520 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92521 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92522 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-92523 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92524 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92525 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93037 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93039 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93040 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93041 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93046 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93048 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93049 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93051 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93052 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93053 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93055 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93056 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93061 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93063 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93064 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93065 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93067 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93073 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93083 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93084 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93085 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93086 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93089 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93090 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93092 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93097 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93098 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93102 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93103 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93108 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93109 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93110 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93113 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93114 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93115 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93118 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93120 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93126 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93130 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93131 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93136 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93138 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93140 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93141 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93145 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93149 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93151 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-93152 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93156 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93158 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93159 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93160 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93161 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93165 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93167 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93170 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93174 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93177 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93178 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93179 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93182 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93183 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93184 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93185 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93188 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93190 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93191 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93203 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-93204 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93206 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93208 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93209 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93211 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93213 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93222 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93226 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93228 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-93229 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93234 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93241 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93242 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93243 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-93244 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93247 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93256 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93261 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93264 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93268 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93269 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93271 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93273 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93274 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93275 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93278 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93279 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93280 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-93281 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93286 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93287 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93781 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93782 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93785 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93789 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93791 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93793 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-93794 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93795 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93798 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93799 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93801 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93802 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93803 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93804 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93805 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93807 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93808 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93811 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93815 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93816 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93819 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93820 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93821 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93822 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93823 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93825 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93826 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93830 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-97407 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97408 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97411 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97413 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-97416 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97418 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97419 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97420 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97421 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97430 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97432 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97433 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-97434 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97435 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97436 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97437 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97438 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97439 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97440 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97441 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97443 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97444 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97446 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97448 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97451 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97455 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97456 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97472 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97475 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97481 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97482 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97483 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97484 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97485 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97486 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97487 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97488 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97489 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97490 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97491 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97492 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97498 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97500 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97502 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97506 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97507 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97508 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97509 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97510 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97511 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97514 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97515 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97516 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97517 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97518 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97522 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97523 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-97529 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97542 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97545 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97552 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97558 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97560 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97566 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97567 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97572 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97576 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97577 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97578 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97579 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97582 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97587 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97592 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97596 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97597 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97598 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97601 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97604 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97605 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97606 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97607 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97612 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97613 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97899 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97900 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97902 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97904 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97905 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97907 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97909 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97910 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97915 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97916 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97917 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97919 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97920 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97921 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97923 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97924 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97927 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97930 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97939 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97945 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97948 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97951 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97952 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97953 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-97957 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97958 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97959 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97961 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97963 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97964 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97966 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97969 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97970 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97977 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97979 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97981 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97982 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97984 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97985 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97993 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97995 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97997 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97998 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98006 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98007 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98009 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98010 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98011 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98012 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98013 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98018 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98020 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98021 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98022 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98024 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98026 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98027 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98028 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98029 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98030 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98031 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98038 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98043 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98044 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98051 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98052 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98054 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98055 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98058 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98063 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98064 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98071 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98072 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98074 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98079 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98080 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98081 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98082 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98086 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98087 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98090 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98091 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98092 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98094 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98095 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98098 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98103 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98111 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98113 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98114 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98121 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98123 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98125 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98126 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98127 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98128 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98129 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98151 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98152 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98157 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98158 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98159 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98160 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98162 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98168 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98170 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98177 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98179 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98180 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98187 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98188 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98189 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98190 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98191 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98193 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98194 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98195 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98199 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98200 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98202 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98203 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98206 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98207 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98208 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98209 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98210 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98218 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98227 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98233 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98234 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98235 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98237 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98253 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98263 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98269 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98270 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98272 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98279 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98288 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98289 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98292 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98293 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98297 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98298 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98302 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98303 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98304 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98308 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98311 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98319 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98321 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98322 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98327 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98328 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98329 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98334 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98335 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98336 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98337 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98340 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98344 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98345 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98348 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98349 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98351 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98352 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98353 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98360 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98369 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98381 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98382 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98383 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98384 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98386 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98388 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98389 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98393 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98394 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98398 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98402 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98404 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98406 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98407 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98410 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98413 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98419 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98421 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98422 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98427 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98455 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98461 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98477 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98495 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98511 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98512 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98517 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98521 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98522 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98541 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98547 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98554 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98556 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98610 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98743 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98744 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98745 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98778 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98801 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98812 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98850 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89634 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-90086 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90092 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-98699 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98706 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98707 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98823 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98824 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98827 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80890 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89456 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89684 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89686 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89705 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89844 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89847 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89857 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89861 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-90041 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-97527 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-97595 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-97965 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98154 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98284 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98300 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98401 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-98471 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98577 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98698 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98859 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40344 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74502 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97557 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-98738 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80793 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80830 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80846 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80979 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89655 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89892 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90234 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-97975 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98501 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40054 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40247 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23459 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63805 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63811 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64082 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64389 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64400 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64581 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64586 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-68082 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-72501 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74564 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74691 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-80555 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80732 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80761 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80763 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80768 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80770 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80772 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80774 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80781 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80783 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80789 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80794 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80795 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80796 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80798 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80799 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80800 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80801 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80802 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80803 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80807 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80808 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80809 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80812 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80814 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80823 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80825 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80826 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80827 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80831 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80833 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80834 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80835 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80838 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80839 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80847 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80889 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80904 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80910 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-81007 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89776 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89781 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89782 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89785 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89787 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89789 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89792 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89793 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89794 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89801 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89806 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89817 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89818 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89819 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89821 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89827 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89830 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89832 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89833 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89839 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89840 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89842 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89843 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89849 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89850 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89852 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89865 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89866 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89868 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89871 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89878 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89880 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89883 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89887 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89888 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89890 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89893 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89895 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89902 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89903 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89904 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89906 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89908 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89931 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89934 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89936 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89937 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89939 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89945 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89946 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89947 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89948 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89949 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89950 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89951 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89952 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89954 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89957 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89964 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89968 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-89969 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89984 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89992 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89997 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89999 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90000 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90016 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90017 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90018 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90025 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90026 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90029 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90030 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90032 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90042 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-93214 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93215 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93219 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93223 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93236 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93238 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93245 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93250 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93252 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93259 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93783 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93784 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93797 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97445 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97449 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97450 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97452 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97453 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97454 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97520 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97568 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98076 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98077 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98088 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98089 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98096 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-98097 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98099 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98232 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98257 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-98275 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98436 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74535 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89897 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-90329 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-93189 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98255 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98549 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-57857 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37906 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38717 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40139 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68745 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-71074 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68081 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72383 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74677 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74700 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74714 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74715 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80982 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89810 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89913 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90003 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90057 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90417 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92507 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92509 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92510 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93176 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97988 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98229 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98441 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98462 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98515 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98568 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98625 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98642 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98708 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98709 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98734 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98735 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98737 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98742 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98752 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98800 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42107 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21984 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38242 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39754 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45949 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53108 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74589 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74594 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74614 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74660 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74730 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80528 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80534 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80589 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80731 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80737 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80762 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80767 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80806 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80854 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80893 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80911 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80944 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80947 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80994 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-81001 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-81008 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89440 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89501 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89510 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89540 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89547 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89553 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89741 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89747 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89823 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89853 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89854 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89956 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89983 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90128 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90135 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90260 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90262 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90303 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90325 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90393 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92500 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93137 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93162 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97608 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98014 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98015 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98016 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98023 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98075 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98083 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98109 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98196 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98217 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98231 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98301 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98342 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98354 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98507 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98508 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98510 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98536 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98537 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98538 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98581 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98598 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98622 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98672 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98681 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98694 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98717 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98736 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98750 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98753 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98772 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98773 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98785 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98840 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74501 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74585 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74682 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80829 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89879 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89891 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93119 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98025 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98181 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98265 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68360 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-98572 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98626 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98739 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98799 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98813 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2018-17977 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68337 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74456 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74471 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80757 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80765 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80805 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80832 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89657 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-98078 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98363 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98443 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98460 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98525 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98569 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98631 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98640 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98644 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98646 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98726 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98789 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98838 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98701 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80791 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89666 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90033 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98453 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98822 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80766 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98456 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98588 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98632 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98862 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74604 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80782 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80790 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-81005 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98416 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98494 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98816 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98761 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2017-13716 | NONE0 | binutils-common 2.42-4ubuntu2.10 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2017-0537 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2017-13165 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2017-13693 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-1121 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 4.1% Low-Moderate Risk | Not Applicable |
| CVE-2018-12928 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-12929 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-12930 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-12931 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-14899 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2019-15213 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2019-19378 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2019-19814 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 3.3% Low-Moderate Risk | Not Applicable |
| CVE-2019-20426 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2020-14304 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-26934 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-41848 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-44034 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-45885 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-48846 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48929 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50230 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50232 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-33053 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-52879 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54190 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-6238 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-0564 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-35995 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42139 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-44932 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44951 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49910 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49916 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49932 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49970 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50217 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53056 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53064 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53207 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56544 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-56617 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56712 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-57809 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58012 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-58015 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58094 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58095 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21693 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21907 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22104 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22127 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23132 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-23135 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37746 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37807 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37833 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37834 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37870 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37876 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-38036 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38038 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38042 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38064 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-38096 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38132 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38140 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38203 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38206 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38207 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38311 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38353 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38421 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38438 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38597 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38605 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38621 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38636 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39762 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39789 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39833 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39859 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39862 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-39896 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39958 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39990 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40146 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40338 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40340 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68174 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68188 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68209 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68236 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68324 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71313 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-100072 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23017 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23137 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23152 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23217 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23327 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23348 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23472 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31462 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31493 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31771 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31777 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43022 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43053 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43101 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-43118 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43126 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43229 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43298 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43301 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43308 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43309 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43344 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43352 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43353 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43410 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43443 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43485 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45894 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45961 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46054 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46130 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46147 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46171 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46245 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46272 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53017 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53053 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53089 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53102 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53104 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53106 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53113 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53118 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53120 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53129 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53142 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53189 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53207 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53258 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53272 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53284 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53292 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53297 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53313 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53330 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63978 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63979 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-64022 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64038 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64112 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64146 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64154 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64213 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64227 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64388 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64513 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64529 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68086 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68102 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68105 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68150 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68211 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68233 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68238 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68258 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68286 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68287 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-68288 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68291 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68382 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68400 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68436 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68441 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68448 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72042 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72329 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72337 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72341 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72397 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72439 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72454 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74264 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74272 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74273 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74289 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74291 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74324 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74373 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74374 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-74375 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74405 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74407 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74441 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74448 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74450 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74466 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74481 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74490 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74509 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74512 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74514 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74515 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74519 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74521 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74527 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74543 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74544 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74553 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74571 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74605 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74653 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74672 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74687 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74689 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74690 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74711 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74713 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74725 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74729 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74733 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74754 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80556 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80572 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80579 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80580 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80607 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80616 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80623 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80628 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80643 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80653 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80662 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80678 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80679 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80680 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80689 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80698 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80704 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80706 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80708 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80709 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80711 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80764 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80785 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80786 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80820 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80884 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80948 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80974 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80990 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80999 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-81011 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89437 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89441 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89452 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89462 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89465 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89468 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89472 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89539 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89543 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89552 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89574 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89632 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89636 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89648 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89654 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89682 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89702 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89709 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89713 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89718 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89719 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89722 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89738 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89740 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89744 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89756 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89762 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89763 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89795 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89822 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89824 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89835 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89848 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89860 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89862 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89877 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89899 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89912 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89920 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89929 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89944 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89972 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89996 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89998 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90021 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90023 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90036 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-90060 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90084 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90097 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90105 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90106 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90112 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90116 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90144 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90174 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90180 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90182 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90184 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90185 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90186 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90187 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90188 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90189 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90194 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90196 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90206 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90208 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90235 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-90247 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90259 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90267 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90301 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-90311 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90315 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90322 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90326 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90328 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90335 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90336 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90337 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90351 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90359 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90363 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90365 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90367 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-90379 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90383 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90385 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90389 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90408 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90410 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90418 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90421 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90422 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90433 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92481 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92482 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92493 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93042 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-93047 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93050 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93058 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93062 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93072 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93081 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93091 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93093 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93099 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93100 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93104 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93116 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93117 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93122 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93123 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93128 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93129 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93142 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93146 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93150 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93155 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93163 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93168 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93172 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93181 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93186 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93200 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93202 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93216 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93230 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93231 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93240 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93272 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93285 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93786 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-93788 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93809 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93814 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93818 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93827 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93829 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97409 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-97410 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97412 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97414 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97423 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97424 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97425 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97426 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97427 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97428 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97431 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97473 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97474 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97477 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97478 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97479 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97480 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97494 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97495 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97496 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97499 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97501 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97503 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97504 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97505 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97512 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97519 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97521 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97531 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-97532 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97534 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97535 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97536 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-97537 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97539 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97540 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97541 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97554 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97556 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97559 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97599 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97600 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97609 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97616 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97619 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97901 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97908 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97918 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97922 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97925 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97929 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97933 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97935 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97938 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97949 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97950 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97962 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97973 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97978 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97986 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97987 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97989 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97992 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97994 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98003 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98008 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98032 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98046 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98067 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98073 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98101 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98124 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98131 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98142 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98148 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98156 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98161 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98169 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-98172 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98174 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98175 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98182 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98192 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98198 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98211 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98212 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98213 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98245 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98248 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98264 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98271 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98273 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98285 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98286 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98294 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98307 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98309 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98317 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98325 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98326 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98338 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98355 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98375 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98387 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98399 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98400 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98403 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98409 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98423 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98424 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98425 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98430 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98431 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98435 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98445 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98449 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98465 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98466 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98476 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98483 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98488 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98489 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98493 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98504 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98506 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98539 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98544 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98555 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98558 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98559 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98565 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98566 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98576 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98578 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98583 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98593 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98602 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98605 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98620 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98623 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98636 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98647 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98656 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98657 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98660 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98662 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98663 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98664 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98665 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98666 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98669 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98670 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98677 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98687 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98695 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98696 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98703 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98711 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98714 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98715 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98720 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98721 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98722 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98740 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98747 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98748 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98749 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98751 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98756 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98757 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98758 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98762 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98764 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98765 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98766 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98767 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98768 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98770 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98775 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98783 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98786 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98790 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98791 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98793 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98795 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98796 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98798 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98807 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98809 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98814 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98815 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98819 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98820 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98825 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98826 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98830 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98833 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98834 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98835 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98839 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98847 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98848 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98854 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98855 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98856 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-1152 | NONE0 | binutils-common 2.42-4ubuntu2.10 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-98802 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89987 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2020-35501 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98484 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98732 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69647 | NONE0 | binutils-common 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69648 | NONE0 | binutils-common 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69652 | NONE0 | binutils-common 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89642 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89698 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90263 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92485 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98201 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98377 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98451 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-98458 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98509 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98514 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98531 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98551 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98607 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98608 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98629 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98655 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98685 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98686 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98700 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98777 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98811 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98844 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90401 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98450 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98502 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98513 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98579 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98668 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98679 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98755 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98771 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98851 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80973 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69644 | NONE0 | binutils-common 2.42-4ubuntu2.10 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69645 | NONE0 | binutils-common 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69646 | NONE0 | binutils-common 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89458 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98433 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98498 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98609 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54105 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40003 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40065 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40097 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40136 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68230 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68338 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68376 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68781 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46175 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53025 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53368 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64023 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68303 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80738 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80747 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80755 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80851 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80872 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89797 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89799 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89834 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89838 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89859 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89870 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89921 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89938 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89960 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89962 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89988 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90002 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90013 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90022 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90027 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90044 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90045 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93205 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93235 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93237 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93239 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93251 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93260 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93810 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97447 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98102 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98527 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98661 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98682 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98683 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98684 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98628 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98643 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98516 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98535 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98553 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98671 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98710 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98746 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98781 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98782 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98784 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98831 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98473 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98486 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98505 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98519 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98529 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98594 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98680 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98697 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98779 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98780 | NONE0 | linux-libc-dev 6.8.0-147.147 No fix yet | 0.2% Theoretical Threat | Not Applicable |
Want to check another image? Run a full scan with the Docker Security Scanner.