Last scanned:
This image is safe for production use. It has 57 exposed and 51 post-exploit-only findings in the stats, but none reach severity 6.0; the maximums are 5.5 and 3.3 respectively. Trust signals are strong from an nvidia community image that is popular, reliable, and pinned by digest. No top findings or CVE IDs were provided, so there is no specific high-severity vulnerability to drive a higher verdict.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2017-13716 | MEDIUM5.5 | libbinutils 2.38-4ubuntu2.12 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010204 | MEDIUM5.5 | libbinutils 2.38-4ubuntu2.12 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libctf-nobfd0 2.38-4ubuntu2.12 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010204 | MEDIUM5.5 | libctf-nobfd0 2.38-4ubuntu2.12 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libctf0 2.38-4ubuntu2.12 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010204 | MEDIUM5.5 | libctf0 2.38-4ubuntu2.12 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-46195 | MEDIUM4.67 | libasan6 11.4.0-1ubuntu1~22.04.3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libasan6 11.4.0-1ubuntu1~22.04.3 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libatomic1 12.3.0-1ubuntu1~22.04.3 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libbinutils 2.38-4ubuntu2.12 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libbinutils 2.38-4ubuntu2.12 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2022-48064 | MEDIUM4.67 | libbinutils 2.38-4ubuntu2.12 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libcc1-0 12.3.0-1ubuntu1~22.04.3 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libctf-nobfd0 2.38-4ubuntu2.12 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libctf-nobfd0 2.38-4ubuntu2.12 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2022-48064 | MEDIUM4.67 | libctf-nobfd0 2.38-4ubuntu2.12 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libctf0 2.38-4ubuntu2.12 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libctf0 2.38-4ubuntu2.12 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2022-48064 | MEDIUM4.67 | libctf0 2.38-4ubuntu2.12 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2021-46195 | MEDIUM4.67 | libgcc-11-dev 11.4.0-1ubuntu1~22.04.3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libgcc-11-dev 11.4.0-1ubuntu1~22.04.3 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libgcc-s1 12.3.0-1ubuntu1~22.04.3 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libgomp1 12.3.0-1ubuntu1~22.04.3 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libitm1 12.3.0-1ubuntu1~22.04.3 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | liblsan0 12.3.0-1ubuntu1~22.04.3 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libquadmath0 12.3.0-1ubuntu1~22.04.3 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2021-46195 | MEDIUM4.67 | libstdc++-11-dev 11.4.0-1ubuntu1~22.04.3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libstdc++-11-dev 11.4.0-1ubuntu1~22.04.3 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libstdc++6 12.3.0-1ubuntu1~22.04.3 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2021-46195 | MEDIUM4.67 | libtsan0 11.4.0-1ubuntu1~22.04.3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libtsan0 11.4.0-1ubuntu1~22.04.3 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libubsan1 12.3.0-1ubuntu1~22.04.3 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.17 | libc-bin 2.35-0ubuntu3.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.17 | libc6 2.35-0ubuntu3.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.17 | libc6-dev 2.35-0ubuntu3.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | LOW3.57 | libc-bin 2.35-0ubuntu3.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | LOW3.57 | libc6 2.35-0ubuntu3.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | LOW3.57 | libc6-dev 2.35-0ubuntu3.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2017-13716 | LOW3.3 | binutils 2.38-4ubuntu2.12 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010204 | LOW3.3 | binutils 2.38-4ubuntu2.12 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2017-13716 | LOW3.3 | binutils-x86-64-linux-gnu 2.38-4ubuntu2.12 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010204 | LOW3.3 | binutils-x86-64-linux-gnu 2.38-4ubuntu2.12 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2019-20633 | LOW3.3 | patch 2.7.6-7build2 No fix yet | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1152 | LOW3.15 | libbinutils 2.38-4ubuntu2.12 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libctf-nobfd0 2.38-4ubuntu2.12 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libctf0 2.38-4ubuntu2.12 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | LOW2.8 | binutils 2.38-4ubuntu2.12 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW2.8 | binutils 2.38-4ubuntu2.12 No fix yet | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2022-48064 | LOW2.8 | binutils 2.38-4ubuntu2.12 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | binutils-x86-64-linux-gnu 2.38-4ubuntu2.12 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW2.8 | binutils-x86-64-linux-gnu 2.38-4ubuntu2.12 No fix yet | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2022-48064 | LOW2.8 | binutils-x86-64-linux-gnu 2.38-4ubuntu2.12 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2021-46195 | LOW2.8 | cpp-11 11.4.0-1ubuntu1~22.04.3 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW2.8 | cpp-11 11.4.0-1ubuntu1~22.04.3 No fix yet | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2026-102473 | LOW2.8 | dash 0.5.11+git20210903+057cd650a4ed-3build1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2021-46195 | LOW2.8 | g++-11 11.4.0-1ubuntu1~22.04.3 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW2.8 | g++-11 11.4.0-1ubuntu1~22.04.3 No fix yet | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2021-46195 | LOW2.8 | gcc-11 11.4.0-1ubuntu1~22.04.3 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW2.8 | gcc-11 11.4.0-1ubuntu1~22.04.3 No fix yet | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2021-45261 | LOW2.8 | patch 2.7.6-7build2 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-56288 | LOW2.8 | patch 2.7.6-7build2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-56289 | LOW2.8 | patch 2.7.6-7build2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW2.8 | libbinutils 2.38-4ubuntu2.12 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libctf-nobfd0 2.38-4ubuntu2.12 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libctf0 2.38-4ubuntu2.12 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libsystemd0 249.11-0ubuntu3.23 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libudev1 249.11-0ubuntu3.23 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-41409 | LOW2.7 | libpcre2-8-0 10.39-3ubuntu0.1 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2022-4899 | LOW2.7 | libzstd1 1.4.8+dfsg-3build1 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2018-6952 | LOW2.7 | patch 2.7.6-7build2 No fix yet | 8.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-86145 | LOW2.51 | libpcre2-8-0 10.39-3ubuntu0.1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-18374 | LOW2.5 | libc-dev-bin 2.35-0ubuntu3.15 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-89161 | LOW2.39 | libpcre2-8-0 10.39-3ubuntu0.1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW2.38 | libbinutils 2.38-4ubuntu2.12 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libctf-nobfd0 2.38-4ubuntu2.12 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libctf0 2.38-4ubuntu2.12 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-3826 | LOW2.34 | cpp-11 11.4.0-1ubuntu1~22.04.3 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2021-3826 | LOW2.34 | g++-11 11.4.0-1ubuntu1~22.04.3 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2021-3826 | LOW2.34 | gcc-11 11.4.0-1ubuntu1~22.04.3 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2021-3826 | LOW2.34 | libasan6 11.4.0-1ubuntu1~22.04.3 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2021-3826 | LOW2.34 | libgcc-11-dev 11.4.0-1ubuntu1~22.04.3 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2021-3826 | LOW2.34 | libstdc++-11-dev 11.4.0-1ubuntu1~22.04.3 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2021-3826 | LOW2.34 | libtsan0 11.4.0-1ubuntu1~22.04.3 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2026-103111 | LOW2.33 | libpcre2-8-0 10.39-3ubuntu0.1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-89157 | LOW2.26 | libpcre2-8-0 10.39-3ubuntu0.1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-18477 | LOW2.24 | tar 1.34+dfsg-1ubuntu0.1.22.04.6 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-18508 | LOW2.24 | tar 1.34+dfsg-1ubuntu0.1.22.04.6 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-89092 | LOW2.14 | libc-dev-bin 2.35-0ubuntu3.15 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-102474 | LOW2.04 | dash 0.5.11+git20210903+057cd650a4ed-3build1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-89158 | LOW1.99 | libpcre2-8-0 10.39-3ubuntu0.1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-89160 | LOW1.99 | libpcre2-8-0 10.39-3ubuntu0.1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils 2.38-4ubuntu2.12 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils-x86-64-linux-gnu 2.38-4ubuntu2.12 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2024-56433 | LOW1.84 | passwd 1:4.8.1-2ubuntu2.2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-89156 | LOW1.81 | libpcre2-8-0 10.39-3ubuntu0.1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils 2.38-4ubuntu2.12 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils-x86-64-linux-gnu 2.38-4ubuntu2.12 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-29383 | LOW1.68 | passwd 1:4.8.1-2ubuntu2.2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.43 | binutils 2.38-4ubuntu2.12 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.43 | binutils-x86-64-linux-gnu 2.38-4ubuntu2.12 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-68457 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-68809 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74744 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74752 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89676 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68159 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72323 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89495 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89656 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89674 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-99999 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80586 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80844 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-68315 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89526 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89631 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-93787 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-72318 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89653 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-90011 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-89633 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89524 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74509 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37777 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-48771 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48998 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49359 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49910 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49935 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50095 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-50212 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50213 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50234 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50240 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52452 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53072 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53187 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-40954 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41045 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46833 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49991 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50246 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53179 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-56604 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21812 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21927 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-21945 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-21967 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-22040 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-22041 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-37899 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2025-37926 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-37947 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-37952 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-38349 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38437 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-38552 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-39952 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71073 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23111 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-23171 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23208 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23226 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-23245 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23378 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31678 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31729 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43049 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53262 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64556 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68108 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89638 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93817 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98260 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2013-7445 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 2.8% Low-Moderate Risk | Not Applicable |
| CVE-2020-14356 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2022-3238 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50071 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50090 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50163 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-50303 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-0030 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-26242 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53037 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53218 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54151 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54187 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35932 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36012 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36914 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38556 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-47745 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50063 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37903 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37928 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-38369 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38734 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-23447 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23448 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43250 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46068 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64270 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64341 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64348 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68138 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-72098 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72255 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74582 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74746 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80536 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80951 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-81000 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89508 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89617 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89725 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89736 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89761 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93288 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98116 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2017-13165 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2018-12930 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-12931 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-19378 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2019-19814 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 3.3% Low-Moderate Risk | Not Applicable |
| CVE-2021-26934 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-48744 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2022-49471 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49722 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49980 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50256 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50406 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50492 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50518 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-2007 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-33053 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-52624 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-52837 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52916 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53052 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53320 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53510 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53544 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26742 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26983 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35868 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-40989 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41069 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42118 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42147 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43842 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46729 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46811 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46813 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49992 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50217 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-56609 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57887 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21734 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21915 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22083 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23133 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37861 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37957 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38069 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38117 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38118 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38131 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38239 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38259 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38361 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38422 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38485 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38595 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38702 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39797 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39810 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39859 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71152 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23068 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23361 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31493 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31500 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31527 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31702 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46075 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46241 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53089 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53115 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53117 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53120 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53129 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53156 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64001 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64272 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64305 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64424 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89465 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89972 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-93827 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80590 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-74345 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-38501 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2025-68806 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64396 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68136 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-0400 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2022-25836 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-97417 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-98417 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2019-20426 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2024-36347 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40170 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74631 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89783 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2019-14899 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-68426 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-53781 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97415 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68278 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72099 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-72243 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80863 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93262 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93813 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97505 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-6610 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-26954 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-36013 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-41013 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49861 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50164 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53147 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21946 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-22039 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2025-37879 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-38728 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40064 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43042 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52968 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64078 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68198 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74510 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89481 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-97493 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97497 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-49234 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50551 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-14040 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-35939 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36915 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41935 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57982 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-21985 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22038 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-38679 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23315 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31568 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45893 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53179 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89596 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89779 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89846 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-93812 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97422 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49172 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49218 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49518 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53254 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53376 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53751 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-57945 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22104 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38081 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39744 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39901 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40358 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68183 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68324 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43126 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45957 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53303 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53330 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97425 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97494 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97495 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50286 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-63940 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72399 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89530 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89652 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89659 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89708 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-98365 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-37776 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40135 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-40158 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-40168 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-23050 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23191 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31663 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43116 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46181 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46242 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 4.4% Low-Moderate Risk | Not Applicable |
| CVE-2026-52991 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53005 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53185 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63958 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64015 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64025 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64026 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64098 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64320 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-64539 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64557 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68100 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68162 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68236 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68245 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68257 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68323 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68329 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68343 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68401 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68404 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68427 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68470 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-72284 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72288 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72338 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72405 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74310 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74378 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74506 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74537 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74677 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74684 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74700 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74714 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74724 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80710 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80837 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80841 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80852 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80864 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80982 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89448 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89528 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89537 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89550 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89564 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89580 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89637 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89675 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89680 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89685 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89707 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-90092 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90093 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90104 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-90111 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90227 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90237 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90313 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90343 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97429 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97555 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-97557 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-97564 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97988 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98033 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98041 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98222 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98229 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98283 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98333 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98341 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98364 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2021-3864 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2022-1247 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-2961 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52586 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50106 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-53216 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57876 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40354 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23054 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45859 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-45942 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46199 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46324 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52956 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-53000 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53009 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53091 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63962 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64048 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64280 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64561 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-68118 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68161 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-68202 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68253 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68289 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68374 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68453 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-72045 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72053 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72057 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72065 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72069 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72157 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-72242 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72252 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72253 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72320 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-72382 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72398 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72473 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-74436 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74474 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74496 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74575 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74594 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74621 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74637 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74662 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74666 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74668 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74695 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74737 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-74743 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80528 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80540 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80552 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80553 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80558 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80561 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80584 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80792 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80824 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80840 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80842 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80848 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80921 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80944 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80947 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80952 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80971 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80973 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80976 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-80977 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80978 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80989 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-80994 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-81001 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-81002 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-81003 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-81008 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89440 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89444 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89456 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89458 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89476 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89477 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89478 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89479 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89480 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89482 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89485 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89487 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89488 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89510 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89532 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89533 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89538 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89540 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89541 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89542 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89545 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89548 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89551 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89553 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89555 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89559 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89560 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89563 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89569 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89575 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89582 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89606 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89607 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89609 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89625 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89642 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89643 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89649 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89650 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89655 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89662 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89663 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89665 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89666 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89669 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89671 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89672 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89684 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89686 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89693 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89694 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89697 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89704 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89706 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89712 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89729 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89741 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89777 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89894 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89930 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89932 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90049 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90071 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90099 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90102 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-90110 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-90128 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90146 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90151 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-90203 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90207 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90234 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-90263 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90284 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90292 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90294 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-90303 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90307 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90334 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90347 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93189 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-93283 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93800 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97476 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97524 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-97561 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97563 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97573 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-97608 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97611 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97612 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97926 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97931 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97940 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97954 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97957 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97965 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97975 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97991 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98014 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98015 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98016 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98023 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98025 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98066 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98068 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98069 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-98070 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-98075 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98108 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98123 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98130 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-98154 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98176 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98186 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98196 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98197 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98201 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98204 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98205 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98217 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98221 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98236 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98241 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98251 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98252 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98254 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98255 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98257 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-98262 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98265 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98266 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98276 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98282 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98284 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98287 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98290 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98299 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98306 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98312 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98314 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98320 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98323 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-98330 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98331 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98339 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98342 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98343 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98347 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98357 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-98358 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98362 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98367 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98370 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98374 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98377 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98379 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98380 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98381 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98383 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98401 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98426 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98428 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-45885 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49855 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-39759 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39826 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71192 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45894 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46054 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53053 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53230 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53374 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53384 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63826 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64109 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64378 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68086 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68093 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68448 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72051 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72329 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72342 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72436 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72469 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74271 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74289 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74391 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74405 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74441 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74672 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80698 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89543 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89632 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89636 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89648 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89654 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89682 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89702 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89709 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89713 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89719 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90036 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-90180 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90185 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90189 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90206 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90235 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-90315 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90336 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93200 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97427 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97431 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97496 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97531 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-97532 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97901 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97933 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97935 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97938 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97949 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97986 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98156 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98174 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-98175 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98213 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98245 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98264 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98375 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98403 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98430 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90414 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-15794 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2022-50616 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53095 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-57795 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21714 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50851 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21759 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 7.8% Low-Moderate Risk | Not Applicable |
| CVE-2026-53267 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89640 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2021-3826 | NONE0 | gcc-11-base 11.4.0-1ubuntu1~22.04.3 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2023-50495 | NONE0 | libncurses6 6.3-2ubuntu0.3 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-50495 | NONE0 | libncursesw6 6.3-2ubuntu0.3 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-50495 | NONE0 | libtinfo6 6.3-2ubuntu0.3 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-53785 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98167 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-1193 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-89511 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89696 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-0564 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | ncurses-base 6.3-2ubuntu0.3 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-50495 | NONE0 | ncurses-bin 6.3-2ubuntu0.3 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2025-39978 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40074 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31502 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31516 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53033 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53036 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68399 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-90333 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-44032 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-44033 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-44034 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-45888 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-68371 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53078 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-57893 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40307 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89965 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54081 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80788 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98185 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40146 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40190 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68103 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40071 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40355 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68342 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68343 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68736 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89778 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89786 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-90054 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90068 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53850 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40080 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74515 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-52481 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-68246 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-98432 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-3714 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2018-1121 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 4.2% Low-Moderate Risk | Not Applicable |
| CVE-2024-35870 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-40242 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98271 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23239 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23240 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-23271 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31426 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46113 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31392 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49138 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-49569 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-36350 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-36357 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69651 | NONE0 | binutils-common 2.38-4ubuntu2.12 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2017-13716 | NONE0 | binutils-common 2.38-4ubuntu2.12 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010204 | NONE0 | binutils-common 2.38-4ubuntu2.12 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2022-27943 | NONE0 | binutils-common 2.38-4ubuntu2.12 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2022-48064 | NONE0 | binutils-common 2.38-4ubuntu2.12 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2021-46195 | NONE0 | gcc-11-base 11.4.0-1ubuntu1~22.04.3 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2022-27943 | NONE0 | gcc-11-base 11.4.0-1ubuntu1~22.04.3 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2022-27943 | NONE0 | gcc-12-base 12.3.0-1ubuntu1~22.04.3 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2023-53867 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-90162 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2022-38457 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2022-40133 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2022-48673 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-48887 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49203 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49317 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49531 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49829 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49997 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-50167 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-50554 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50746 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50815 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52569 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52676 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52857 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52920 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52981 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53382 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-53846 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54019 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-54237 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-26656 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26853 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-27032 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27062 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35839 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35971 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-40972 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41030 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41062 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-43832 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47736 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49568 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-49988 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-50187 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50285 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-52560 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53079 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53234 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56591 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-56692 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58053 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-58098 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58100 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21738 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21792 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21944 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21955 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-22037 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 69.5% Actively Exploited | Not Applicable |
| CVE-2025-22043 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-22072 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22113 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37856 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37956 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-37959 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-38162 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38191 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2025-38264 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-38449 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38615 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38692 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38716 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39800 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39933 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39942 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40075 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40099 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40347 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-68283 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-68378 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71202 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71315 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23265 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23347 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23385 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23449 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31403 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31410 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31548 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31557 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-31692 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43009 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43016 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43048 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43091 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43153 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43213 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43214 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43318 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43437 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43456 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45940 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45944 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46012 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52946 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53375 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64077 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68085 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-68098 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68259 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68445 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68447 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-72110 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72162 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72196 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72198 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72213 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72369 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72373 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72375 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72380 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-72383 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72390 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72413 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72434 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72464 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72470 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72472 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72478 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72493 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-72494 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-74257 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74268 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-74302 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74317 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74334 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74341 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74347 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74350 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-74386 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74387 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74388 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74454 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74470 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74522 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-74565 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74723 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-80551 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80554 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80631 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-80634 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-80637 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-80671 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80937 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80980 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-80991 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89492 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89520 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89531 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89544 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89565 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89622 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89837 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90108 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90148 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90149 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-90150 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90152 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90155 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90199 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90200 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90204 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90205 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90320 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90321 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93192 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93196 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93199 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93282 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-93790 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93796 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93806 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-93824 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93828 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97442 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-97513 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97530 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97562 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-97565 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97581 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97615 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97906 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98017 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98019 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98056 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-98104 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98107 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98164 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98332 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98359 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98420 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2015-7837 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2016-8660 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-4095 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-47432 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-0480 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-4543 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2022-48766 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48979 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49069 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49133 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49178 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49303 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49469 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49504 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49516 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49534 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49547 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49552 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49622 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49699 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49759 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-49764 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49783 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49810 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49858 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49932 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-4994 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49940 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50224 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50380 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50425 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50527 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50871 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-0160 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31082 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-52582 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52590 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52591 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52625 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52632 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52671 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52700 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52732 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-53002 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53068 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53149 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53221 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53231 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53240 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53247 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53248 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53323 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53366 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53538 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53540 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53561 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53584 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53588 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53620 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53635 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-53685 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53822 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-53829 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54280 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-26691 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26740 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26759 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26844 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26948 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26953 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-27014 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27025 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27400 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27418 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35784 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35799 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35826 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35908 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35946 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36000 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36021 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36244 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36900 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38554 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38564 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41001 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41008 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41023 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41036 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-41088 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42239 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42273 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43872 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-43899 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43912 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44963 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-45010 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-45015 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46720 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46727 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46728 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46765 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46802 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46848 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47141 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47658 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-47678 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-47683 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47703 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47728 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47794 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49893 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49898 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49899 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49905 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49906 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49908 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49912 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49914 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49918 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49920 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49921 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49922 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49923 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49940 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49978 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-50138 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50271 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50298 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-52559 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53091 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53187 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53190 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53195 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53196 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53210 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53220 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53687 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-54683 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56592 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56611 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56641 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-56647 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56665 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56703 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-56709 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57895 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-57975 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57976 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58089 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58096 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-58097 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58241 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21649 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21682 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21696 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21768 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21891 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21972 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22042 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-22057 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22090 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22103 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22105 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22109 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22125 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23130 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23155 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37747 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37775 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37806 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37820 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-37852 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37880 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37931 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37951 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37961 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38029 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38039 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38040 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38041 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38080 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38097 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38166 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38215 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38225 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38261 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38272 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38300 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38331 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-38333 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38359 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38436 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38520 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38544 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38590 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-38644 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39677 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39716 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39720 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-39732 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39747 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39779 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39850 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39851 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-39886 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39925 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39947 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40102 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40104 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40196 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40339 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68219 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68223 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68334 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68379 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68794 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-68822 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71080 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-71160 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71184 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71227 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71285 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71289 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-71297 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-100070 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-100071 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-100075 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-100076 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-100077 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22979 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22996 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23000 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23086 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23154 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23213 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23247 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23255 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23264 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23276 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23334 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23371 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23389 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23468 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31420 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31492 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31503 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31519 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31531 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31537 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31579 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31592 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31675 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31677 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31767 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43025 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43036 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43067 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-43088 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43107 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43115 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43161 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43162 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43167 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43170 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43172 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43173 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43204 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43234 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43244 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43253 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43271 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43299 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43310 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43359 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43361 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43362 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43416 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43419 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43436 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43483 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45855 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45917 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45934 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46000 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46014 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46032 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46059 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46153 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46157 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46158 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46170 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46229 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46235 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46247 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46302 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52936 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52937 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52944 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52972 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52975 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52981 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-52988 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52990 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53018 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53034 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53056 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53066 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53076 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53083 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53107 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53122 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53220 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53317 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53327 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53353 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53376 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63846 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63847 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63848 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63854 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63855 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63856 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63858 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63882 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63963 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63973 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63983 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63999 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64006 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64076 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64079 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64097 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64106 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64190 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64192 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64210 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64294 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64345 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64405 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68096 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68109 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68110 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68112 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68113 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68114 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68130 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68132 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68146 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68205 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68206 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68235 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68241 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68242 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68246 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68251 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68252 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68254 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68255 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68277 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68279 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68312 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68367 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68386 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68412 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68418 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68431 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68434 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72015 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72017 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72023 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72035 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72041 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-72058 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72063 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72070 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72073 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72077 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72087 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72096 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72142 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72148 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-72152 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72155 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72168 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72170 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72191 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72200 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72203 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72216 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72236 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72260 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72290 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72299 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72305 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72308 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72321 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72333 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72376 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72379 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72402 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72404 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72416 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72420 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72438 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-72444 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-72488 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74261 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74278 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74290 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74294 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74296 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74308 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74318 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74337 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74342 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74377 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74406 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74417 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74445 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74479 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74484 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74487 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74494 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74550 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74592 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74595 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74599 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74601 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74623 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74626 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74628 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74632 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74647 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74663 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74735 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74739 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74740 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74747 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74748 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80526 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80527 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80539 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80541 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80547 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80548 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80550 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80557 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80559 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80560 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80562 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80565 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80567 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80568 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80569 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80570 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80573 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80574 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80576 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80583 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80587 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80669 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80670 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-80684 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80694 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-80695 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80697 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80715 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80797 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80843 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80855 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80856 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80928 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80930 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80931 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80932 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80938 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80941 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80949 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80963 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80964 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80965 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80966 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80967 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80968 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80969 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80972 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80983 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80987 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80988 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80992 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80996 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-81017 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89457 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89461 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89463 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89464 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89469 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89470 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89471 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89474 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89475 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89483 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89484 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89489 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89490 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89491 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89493 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89494 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89496 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89497 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89498 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89504 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89512 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89515 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89525 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89527 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89549 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89554 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89557 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89561 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89566 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89567 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89573 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89576 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89585 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89586 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89594 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89595 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89597 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89598 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89599 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89601 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89605 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89608 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89615 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89616 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89621 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89623 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89626 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89627 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89628 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89644 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89645 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89647 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89673 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89699 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89710 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89711 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89720 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89723 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89724 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89726 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89730 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89732 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89733 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89742 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89749 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89752 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89753 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89759 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89765 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89816 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89872 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89881 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89896 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89923 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89924 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89925 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89953 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89982 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90007 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90015 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90053 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90055 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90056 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90058 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90061 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90062 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90063 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90067 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-90070 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90072 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90073 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90074 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90075 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90076 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90078 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90081 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90083 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90088 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90090 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90098 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90103 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-90107 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90109 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90114 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90119 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90125 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90126 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90138 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90139 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90140 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90141 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90143 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90154 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90157 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90160 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90166 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90179 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90183 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90198 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90202 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90209 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90213 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90214 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90216 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90218 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90219 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90221 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90222 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90223 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90224 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90225 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90226 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90228 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-90245 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90248 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90249 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90250 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90251 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90257 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90264 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90273 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90274 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90281 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90283 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90285 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90286 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90289 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90290 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90293 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-90295 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90296 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90297 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90298 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90300 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90302 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90314 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90316 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90318 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90319 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90327 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90330 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90341 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90345 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90348 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90361 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90362 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90378 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90407 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90411 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90415 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90434 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92494 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92504 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-92524 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93056 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93102 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93130 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93145 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93151 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-93159 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93161 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93185 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93188 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93191 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93203 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-93204 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93228 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-93261 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93264 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93268 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93269 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93271 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93274 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93275 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93278 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93279 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93280 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-93286 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93287 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93782 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93785 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93789 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93791 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93793 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93794 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93795 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93798 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93799 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93801 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93802 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93803 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93804 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93805 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93807 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93808 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93811 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93815 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93816 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93819 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93820 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93821 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93822 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93823 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93825 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93826 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93830 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-97407 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97408 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97411 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97413 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-97416 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97418 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97419 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97420 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97421 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97430 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97432 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97433 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-97434 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97435 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97436 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97437 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97438 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97439 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97440 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97441 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97443 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97444 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97446 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97448 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97451 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97455 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97456 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97472 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97475 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97481 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97482 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97483 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97484 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97485 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97486 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97487 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97488 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97489 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97490 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97491 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97492 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97498 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97500 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97502 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97506 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97507 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97508 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97509 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97510 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97511 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97514 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97515 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97516 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97517 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97518 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97523 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-97529 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97558 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97566 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97572 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97576 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97582 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97592 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97596 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97597 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97598 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97601 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97604 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97899 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97904 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97905 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97909 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97910 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97923 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97927 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97930 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97939 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97948 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97951 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97952 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97953 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-97958 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97959 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97963 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97964 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97969 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97970 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97981 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97982 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97984 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97985 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97993 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97995 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97997 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97998 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98006 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98009 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98010 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98011 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98012 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98013 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98021 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98022 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98026 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98027 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98030 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98031 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98043 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98044 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98058 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98063 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98064 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98071 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98072 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98074 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98080 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98087 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98092 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98103 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98111 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98113 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98114 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98121 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98126 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98127 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98157 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98158 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98160 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98162 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98170 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98177 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98180 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98187 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98188 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98189 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98190 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98191 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98193 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98194 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98195 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98199 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98202 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98203 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98207 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98208 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98209 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98210 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98227 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98233 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98234 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98237 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98253 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98269 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98272 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98279 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98288 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98292 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98298 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98302 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98303 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98304 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98308 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98311 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98319 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98321 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98322 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98327 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98328 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98329 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98334 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98335 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98337 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98340 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98344 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98345 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98348 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98349 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98351 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98352 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98369 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98386 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98388 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98389 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98393 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98394 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98398 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98404 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98406 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98407 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98413 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98419 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98421 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98422 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98427 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2017-13693 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-12928 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-12929 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-47658 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48628 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48929 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48976 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49108 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49124 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49134 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49161 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49173 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49177 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49306 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49333 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49342 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49420 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49476 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49484 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49533 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49539 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49543 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49562 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49651 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49766 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49833 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49901 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49955 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50002 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50166 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50178 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50195 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50230 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50232 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50236 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50260 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50266 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50284 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50304 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50316 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50357 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50390 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50407 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50461 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50464 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50467 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50500 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50539 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50550 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50571 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50704 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50748 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50772 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-4133 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52576 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52653 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52660 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52761 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52879 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52888 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52905 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52939 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53008 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53009 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53010 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53042 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53093 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53105 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53115 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53152 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53168 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53261 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53332 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53347 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53348 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53353 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53355 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53367 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53370 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53371 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53383 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53424 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53429 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53438 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53460 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53466 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53491 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-53509 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53529 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53539 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53562 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53574 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53602 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53627 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53647 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53651 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53682 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53694 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53743 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53753 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53765 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53780 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53806 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53849 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54023 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54028 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54052 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54067 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54088 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54121 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54129 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-54190 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54234 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-54324 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26595 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26605 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26714 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26756 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26807 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26866 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26876 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27002 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27005 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27010 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27011 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27035 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27041 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27056 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27435 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-35794 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35801 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35803 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35808 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35875 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-35924 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35931 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35945 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35956 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35995 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35999 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-36009 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36478 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-36479 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36917 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36920 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36924 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36951 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-37021 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38543 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38557 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38594 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38608 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38625 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-40966 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40977 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-40998 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40999 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-41082 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42110 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-42122 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42128 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42129 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42139 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42319 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42320 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42321 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43823 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43824 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43831 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44950 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46678 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46681 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46716 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46726 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46730 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46733 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46754 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46775 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46806 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46808 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46834 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46857 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46860 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47661 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47662 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47664 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47704 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49891 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49901 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49910 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49911 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49915 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49916 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49917 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49919 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49929 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49932 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49939 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49945 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49970 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50009 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50017 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50028 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50098 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50146 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50166 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50284 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-50289 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53056 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53093 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-53175 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53219 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53224 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-56544 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56565 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56566 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56583 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56588 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56660 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56707 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56712 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56718 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-56722 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57809 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57872 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57888 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57924 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-57993 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57999 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58012 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58094 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58095 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58237 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21629 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-21634 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21635 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21645 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21656 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21658 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21673 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-21693 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21723 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21750 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21801 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21816 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21831 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21838 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21872 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21881 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21885 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-21894 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21899 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21918 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21931 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21976 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22028 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22053 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22127 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-23132 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-23160 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37800 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37807 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37833 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37834 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37842 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37853 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37938 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37945 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37980 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38014 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38015 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38038 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38042 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38059 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38062 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38063 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38064 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38071 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38096 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38126 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38127 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38140 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38207 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38275 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38334 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38409 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38426 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38438 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38491 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38643 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38665 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38705 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38709 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39692 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39705 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39706 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39707 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39746 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39762 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39763 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39770 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-39789 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39819 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39827 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39829 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39833 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39932 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-39940 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39989 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39990 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40057 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40100 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40160 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40251 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40325 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68171 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68173 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68188 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68231 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68236 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68310 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68345 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68363 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68778 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71095 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-71109 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71183 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-71268 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71269 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71272 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71273 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71313 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-100072 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23069 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23088 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23137 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23138 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23214 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23267 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23287 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23292 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23310 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23330 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23374 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23465 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23472 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31391 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31412 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31441 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31453 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31462 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31486 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31487 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31496 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31560 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31595 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31606 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31704 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31722 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31723 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31724 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31725 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31771 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31777 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43072 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43073 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43101 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-43118 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43119 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43143 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43288 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43308 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43309 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43317 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43338 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43344 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43352 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43353 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43409 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43410 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43413 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43421 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43424 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45858 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45872 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45877 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45923 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45961 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45981 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45997 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46083 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46147 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46200 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46225 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46226 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46245 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46254 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46280 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46312 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53015 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53017 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53035 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53063 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53070 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53106 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53111 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53147 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53207 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53226 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53229 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53232 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53236 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53237 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53258 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53284 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53289 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53292 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53313 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53314 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53349 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64112 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64144 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64213 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64231 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64241 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64388 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64463 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64513 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68102 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68105 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68107 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68207 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68210 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68233 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68238 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68258 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68286 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68287 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-68288 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68396 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68436 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68441 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68454 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-72028 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72062 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72075 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72106 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72144 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72147 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72179 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72312 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72324 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72335 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72336 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72337 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72384 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72397 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72425 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72439 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72454 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72487 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74291 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74307 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74365 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74374 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-74380 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74389 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74397 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74401 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-74450 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74514 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74521 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74527 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74543 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74544 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74553 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74653 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74687 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74689 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74713 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74725 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74729 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74754 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80556 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80572 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80579 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80580 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80611 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80616 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80623 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80628 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80629 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80635 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80643 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80650 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80653 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80654 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80660 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80676 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80678 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80689 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80704 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80948 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80974 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80990 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80999 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89437 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89441 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89452 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89462 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89468 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89472 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89539 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89552 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89574 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89718 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89722 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89738 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89740 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89744 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89756 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89762 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89763 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89824 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89862 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89877 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89912 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89944 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89996 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90021 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90060 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90084 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90097 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90105 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90106 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90112 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90116 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90174 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90182 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90184 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90186 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90187 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90188 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90194 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90196 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90208 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90247 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90259 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90267 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90301 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-90311 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90322 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90328 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90335 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90337 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93072 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93186 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93202 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93272 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93285 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93786 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-93788 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93809 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93814 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93818 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93829 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97409 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97410 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97412 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97414 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97423 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97424 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97426 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97428 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97473 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97474 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97477 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97478 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97479 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97480 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97499 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97501 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97503 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97504 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97512 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97519 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97521 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97534 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97535 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97536 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-97537 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97539 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97540 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97541 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97554 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97556 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97559 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97599 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97600 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97609 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97616 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97619 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97908 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97918 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97922 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97925 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97929 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97950 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97973 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97978 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97987 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97989 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97992 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97994 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98003 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98008 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98046 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98067 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98073 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98124 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98131 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98142 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98148 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98161 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98169 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-98172 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98182 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98192 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98198 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98212 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98248 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98285 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98294 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98307 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98309 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98325 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98326 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98338 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98387 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98399 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98400 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98409 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98423 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98424 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98425 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-3523 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2023-54181 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98300 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50700 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-71225 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64391 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-50721 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23035 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80793 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71193 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-1205 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-50350 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-53816 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-54035 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-57857 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21947 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-37920 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38717 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39726 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39977 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40039 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40139 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68745 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-71074 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23004 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68081 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52589 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53401 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-54071 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-54185 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36024 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36949 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39508 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42107 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46870 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-49859 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57974 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21732 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21825 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38234 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38524 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-39754 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39825 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39927 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68742 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23110 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23207 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23212 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43448 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45949 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53108 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80534 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98354 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2017-0537 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2022-49967 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-52749 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53178 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53447 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53452 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53794 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-54201 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54323 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26869 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27408 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42253 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43866 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50135 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50183 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21651 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39961 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68296 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23118 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23126 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23302 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23348 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43053 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45905 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68084 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98181 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2019-15213 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-49934 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2018-17977 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-53733 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54263 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38628 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40123 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40198 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40206 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68768 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68337 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98078 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98363 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2020-14304 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-50720 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54253 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26662 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26672 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26757 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26758 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98101 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98273 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-41848 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-81005 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98416 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48646 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93117 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98286 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-1152 | NONE0 | binutils-common 2.38-4ubuntu2.12 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-56433 | NONE0 | login 1:4.8.1-2ubuntu2.2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2020-35501 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69652 | NONE0 | binutils-common 2.38-4ubuntu2.12 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52926 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50211 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48667 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48668 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50811 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53992 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54145 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47738 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40268 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50628 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52561 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50057 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40303 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40341 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-29383 | NONE0 | login 1:4.8.1-2ubuntu2.2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69645 | NONE0 | binutils-common 2.38-4ubuntu2.12 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42155 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-67693 | NONE0 | libgnutls30 3.7.3-4ubuntu1.9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-88647 | NONE0 | libgnutls30 3.7.3-4ubuntu1.9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-95184 | NONE0 | libgnutls30 3.7.3-4ubuntu1.9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-95209 | NONE0 | libgnutls30 3.7.3-4ubuntu1.9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-95210 | NONE0 | libgnutls30 3.7.3-4ubuntu1.9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-107161 | NONE0 | libsasl2-2 2.1.27+dfsg2-3ubuntu1.2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-107161 | NONE0 | libsasl2-modules-db 2.1.27+dfsg2-3ubuntu1.2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63825 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90037 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-93221 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40025 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40137 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40286 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40333 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23393 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31432 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-31477 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-31536 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-31612 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-31706 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-43379 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43490 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-46218 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53024 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53178 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53198 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53401 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63819 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64138 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64257 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-64392 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64393 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64394 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64395 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64397 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64398 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64399 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64580 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68083 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80883 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80891 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80905 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89788 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89803 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89810 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89913 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89922 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90003 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90048 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-90057 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90167 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90169 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90375 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90392 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90398 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-90417 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92499 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92507 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92509 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92510 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-92511 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-92512 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93105 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93154 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93175 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93210 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93792 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98085 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98171 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-53707 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53742 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53748 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40054 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40077 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40084 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40107 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40247 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40285 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40288 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40289 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40311 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40337 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-68190 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68322 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68772 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68786 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31611 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31707 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31768 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43377 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63805 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63959 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64389 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64400 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-64581 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64585 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64586 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64590 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68082 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68097 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68476 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-80555 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80737 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80739 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80742 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80743 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80744 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80752 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80754 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80756 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80757 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80765 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80766 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80767 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80768 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80781 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80782 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80783 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80789 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80790 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80794 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80795 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80796 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80798 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80799 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80800 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80801 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80802 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80803 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80805 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80806 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80807 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80808 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80809 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80812 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80814 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80819 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80823 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80826 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80827 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80828 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80829 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80830 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80831 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80832 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80833 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80834 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80846 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80847 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80854 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80861 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80866 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80888 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80889 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80901 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80904 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80906 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80907 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80908 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80909 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80910 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80912 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80913 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80916 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80917 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80918 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80923 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80925 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-81007 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89562 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89780 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89781 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89782 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89784 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89785 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89787 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89789 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89792 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89794 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89796 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89808 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89813 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89817 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89818 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89821 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89823 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89832 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89833 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89840 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89843 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89845 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89847 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89849 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89850 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89851 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89852 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89853 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89854 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89855 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89856 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89858 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89861 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89863 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89864 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89865 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89871 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89876 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89878 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89879 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89880 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89883 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89887 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89888 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89890 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89891 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89892 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89893 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89895 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89897 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89901 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89926 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89927 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89936 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89937 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89939 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89945 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89946 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89947 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89948 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89949 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89951 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89952 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89954 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89964 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89968 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-89969 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89973 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89979 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89983 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89984 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89987 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89989 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89993 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89995 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89997 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89999 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90000 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-90016 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90017 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90018 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90019 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90020 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90025 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90029 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90031 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90032 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90033 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90034 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90041 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-90153 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-90156 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90329 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-90360 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90372 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90382 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90386 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90388 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90391 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90393 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90394 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90395 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90403 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-90413 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-90416 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90419 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90420 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90431 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90435 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-92476 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92480 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92496 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92498 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92500 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92501 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92508 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92520 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92521 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92522 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-92525 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93037 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93039 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93040 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93041 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93046 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93048 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93049 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93051 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93052 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93053 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93054 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93055 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93061 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93067 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93095 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93098 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93103 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93108 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93109 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93110 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93114 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93115 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93120 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93131 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93138 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93140 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93141 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93149 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93158 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93160 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93165 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93167 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93170 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93177 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93178 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93179 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93183 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93184 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93206 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93213 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93214 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93219 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93222 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93226 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93234 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93236 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93241 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93242 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93243 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93245 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93252 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93256 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93781 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93783 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93784 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93797 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97445 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97449 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97450 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97452 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97453 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97454 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97520 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97568 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98076 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98077 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98079 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98088 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98090 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98091 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98094 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98095 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98096 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-98097 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98098 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98099 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98275 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98316 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50634 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50708 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50759 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-53855 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54047 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54105 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54180 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40003 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40032 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40036 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40093 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40095 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40097 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40180 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40193 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40266 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-62626 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68755 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68781 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71067 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71198 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43249 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46175 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46265 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-53025 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53368 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63862 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64449 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68203 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68280 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68303 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74690 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80738 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80747 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80755 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80764 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80785 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80786 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80820 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80851 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80884 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89795 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89797 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89799 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89822 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89834 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89835 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89838 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89848 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89859 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89860 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89870 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89899 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89920 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89921 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89929 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89938 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89960 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89962 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89988 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90002 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90013 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90023 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90044 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90045 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90359 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90365 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90379 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90383 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90385 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90389 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90401 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90410 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90418 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90421 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90433 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92481 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92482 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93042 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-93047 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93050 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93058 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93062 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93081 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93091 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93093 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93099 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93100 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93104 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93128 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93142 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93146 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93150 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93155 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93163 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93168 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93172 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93205 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93231 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93235 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93237 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93239 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93240 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93251 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93260 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93810 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97447 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98102 | NONE0 | linux-libc-dev 5.15.0-198.208 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-85091 | NONE0 | zlib1g 1:1.2.11.dfsg-2ubuntu9.2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
Which CVEs are actually reachable — is the vulnerable code even linked and callable.
Live-container probes: default user, writable paths, capabilities, exposed ports.
Base-image lineage, package provenance and signatures — nothing slipped in unnoticed.
A step-by-step hardened build plan, with parity tests proving nothing breaks.
Want to check another image? Run a full scan with the Docker Security Scanner.