Last scanned:
This image poses a critical security risk and must not be used in production, especially as an internet-facing service. An attacker could trigger a denial-of-service via the HTTP/2 Rapid Reset attack (CVE-2023-44487) or corrupt memory through Kerberos token handling (CVE-2024-37371), leading to crashes or data leaks. Disabling HTTP/2 entirely would fully mitigate CVE-2023-44487, but CVE-2024-37371 remains unfixed in the installed krb5 package. Without immediate patching or strict network segmentation, this image is dangerously exploitable.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2023-44487 | CRITICAL9.75 | libnghttp2-14 1.52.0-1 fixed in 1.52.0-1+deb12u1 | 100.0% Actively Exploited | Directly ExposedContext importance: HIGH |
| CVE-2024-37371 | CRITICAL9.1 | libgssapi-krb5-2 1.20.1-2+deb12u1 fixed in 1.20.1-2+deb12u2 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2024-37371 | CRITICAL9.1 | libk5crypto3 1.20.1-2+deb12u1 fixed in 1.20.1-2+deb12u2 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2024-37371 | CRITICAL9.1 | libkrb5-3 1.20.1-2+deb12u1 fixed in 1.20.1-2+deb12u2 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2024-37371 | CRITICAL9.1 | libkrb5support0 1.20.1-2+deb12u1 fixed in 1.20.1-2+deb12u2 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2025-49796 | CRITICAL9.1 | libxml2 2.9.14+dfsg-1.3~deb12u1 fixed in 2.9.14+dfsg-1.3~deb12u3 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010023 | HIGH8.8 | libc-bin 2.36-9+deb12u3 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010023 | HIGH8.8 | libc-dev-bin 2.36-9+deb12u3 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010023 | HIGH8.8 | libc6 2.36-9+deb12u3 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010023 | HIGH8.8 | libc6-dev 2.36-9+deb12u3 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-31789 | HIGH8.33 | libssl3 3.0.11-1~deb12u1 fixed in 3.0.19-1~deb12u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6653 | HIGH8.33 | libxml2 2.9.14+dfsg-1.3~deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-32988 | HIGH8.2 | libgnutls30 3.7.9-2 fixed in 3.7.9-2+deb12u5 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-45447 | HIGH8.1 | libssl3 3.0.11-1~deb12u1 fixed in 3.0.20-1~deb12u2 | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2024-2961 | HIGH8 | libc6 2.36-9+deb12u3 fixed in 2.36-9+deb12u6 | 88.3% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2024-45491 | HIGH7.84 | libexpat1 2.5.0-1 fixed in 2.5.0-1+deb12u1 | 1.1% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2024-45492 | HIGH7.84 | libexpat1 2.5.0-1 fixed in 2.5.0-1+deb12u1 | 1.4% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2026-42010 | HIGH7.84 | libgnutls30 3.7.9-2 fixed in 3.7.9-2+deb12u7 | 1.1% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2024-56171 | HIGH7.84 | libxml2 2.9.14+dfsg-1.3~deb12u1 fixed in 2.9.14+dfsg-1.3~deb12u2 | 1.1% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2023-6246 | HIGH7.8 | libc-bin 2.36-9+deb12u3 fixed in 2.36-9+deb12u4 | 4.8% Low-Moderate Risk | Directly Exposed |
| CVE-2023-6246 | HIGH7.8 | libc-dev-bin 2.36-9+deb12u3 fixed in 2.36-9+deb12u4 | 4.8% Low-Moderate Risk | Directly Exposed |
| CVE-2023-6246 | HIGH7.8 | libc6 2.36-9+deb12u3 fixed in 2.36-9+deb12u4 | 4.8% Low-Moderate Risk | Directly Exposed |
| CVE-2023-6246 | HIGH7.8 | libc6-dev 2.36-9+deb12u3 fixed in 2.36-9+deb12u4 | 4.8% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7245 | HIGH7.8 | libpcre3 2:8.39-15 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7246 | HIGH7.8 | libpcre3 2:8.39-15 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2024-6119 | HIGH7.8 | libssl3 3.0.11-1~deb12u1 fixed in 3.0.14-1~deb12u2 | 66.6% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2023-50387 | HIGH7.8 | libsystemd0 252.17-1~deb12u1 fixed in 252.23-1~deb12u1 | 100.0% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2023-50868 | HIGH7.8 | libsystemd0 252.17-1~deb12u1 fixed in 252.23-1~deb12u1 | 81.7% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2026-33845 | HIGH7.73 | libgnutls30 3.7.9-2 fixed in 3.7.9-2+deb12u7 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-45445 | HIGH7.73 | libssl3 3.0.11-1~deb12u1 fixed in 3.0.20-1~deb12u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-49794 | HIGH7.73 | libxml2 2.9.14+dfsg-1.3~deb12u1 fixed in 2.9.14+dfsg-1.3~deb12u3 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-33599 | HIGH7.6 | libc-bin 2.36-9+deb12u3 fixed in 2.36-9+deb12u7 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33599 | HIGH7.6 | libc-dev-bin 2.36-9+deb12u3 fixed in 2.36-9+deb12u7 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33599 | HIGH7.6 | libc6 2.36-9+deb12u3 fixed in 2.36-9+deb12u7 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33599 | HIGH7.6 | libc6-dev 2.36-9+deb12u3 fixed in 2.36-9+deb12u7 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2023-6779 | HIGH7.5 | libc-bin 2.36-9+deb12u3 fixed in 2.36-9+deb12u4 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc-bin 2.36-9+deb12u3 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc-bin 2.36-9+deb12u3 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-6779 | HIGH7.5 | libc-dev-bin 2.36-9+deb12u3 fixed in 2.36-9+deb12u4 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc-dev-bin 2.36-9+deb12u3 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc-dev-bin 2.36-9+deb12u3 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-6779 | HIGH7.5 | libc6 2.36-9+deb12u3 fixed in 2.36-9+deb12u4 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc6 2.36-9+deb12u3 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc6 2.36-9+deb12u3 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-6779 | HIGH7.5 | libc6-dev 2.36-9+deb12u3 fixed in 2.36-9+deb12u4 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc6-dev 2.36-9+deb12u3 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc6-dev 2.36-9+deb12u3 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-52425 | HIGH7.5 | libexpat1 2.5.0-1 fixed in 2.5.0-1+deb12u2 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2024-45490 | HIGH7.5 | libexpat1 2.5.0-1 fixed in 2.5.0-1+deb12u1 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2024-8176 | HIGH7.5 | libexpat1 2.5.0-1 fixed in 2.5.0-1+deb12u2 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2024-28757 | HIGH7.5 | libexpat1 2.5.0-1 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2018-6829 | HIGH7.5 | libgcrypt20 1.10.1-3 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2024-0553 | HIGH7.5 | libgnutls30 3.7.9-2 fixed in 3.7.9-2+deb12u2 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2024-0567 | HIGH7.5 | libgnutls30 3.7.9-2 fixed in 3.7.9-2+deb12u2 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-33846 | HIGH7.5 | libgnutls30 3.7.9-2 fixed in 3.7.9-2+deb12u7 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42009 | HIGH7.5 | libgnutls30 3.7.9-2 fixed in 3.7.9-2+deb12u7 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libgssapi-krb5-2 1.20.1-2+deb12u1 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libk5crypto3 1.20.1-2+deb12u1 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libkrb5-3 1.20.1-2+deb12u1 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libkrb5support0 1.20.1-2+deb12u1 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-2953 | HIGH7.5 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2015-3276 | HIGH7.5 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 5.3% Low-Moderate Risk | Directly Exposed |
| CVE-2017-17740 | HIGH7.5 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 7.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-2953 | HIGH7.5 | libldap-common 2.5.13+dfsg-5 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2015-3276 | HIGH7.5 | libldap-common 2.5.13+dfsg-5 No fix yet | 5.3% Low-Moderate Risk | Directly Exposed |
| CVE-2017-17740 | HIGH7.5 | libldap-common 2.5.13+dfsg-5 No fix yet | 7.0% Low-Moderate Risk | Directly Exposed |
| CVE-2017-11164 | HIGH7.5 | libpcre3 2:8.39-15 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-20838 | HIGH7.5 | libpcre3 2:8.39-15 No fix yet | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2023-5363 | HIGH7.5 | libssl3 3.0.11-1~deb12u1 fixed in 3.0.11-1~deb12u2 | 3.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-25062 | HIGH7.5 | libxml2 2.9.14+dfsg-1.3~deb12u1 fixed in 2.9.14+dfsg-1.3~deb12u2 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2025-27113 | HIGH7.5 | libxml2 2.9.14+dfsg-1.3~deb12u1 fixed in 2.9.14+dfsg-1.3~deb12u2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2025-6021 | HIGH7.5 | libxml2 2.9.14+dfsg-1.3~deb12u1 fixed in 2.9.14+dfsg-1.3~deb12u3 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-32990 | MEDIUM6.97 | libgnutls30 3.7.9-2 fixed in 3.7.9-2+deb12u5 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-42013 | MEDIUM6.97 | libgnutls30 3.7.9-2 fixed in 3.7.9-2+deb12u7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5260 | MEDIUM6.97 | libgnutls30 3.7.9-2 fixed in 3.7.9-2+deb12u7 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-28182 | MEDIUM6.89 | libnghttp2-14 1.52.0-1 fixed in 1.52.0-1+deb12u2 | 85.0% Actively Exploited | Directly Exposed |
| CVE-2026-0861 | MEDIUM6.88 | libc-bin 2.36-9+deb12u3 fixed in 2.36-9+deb12u14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0861 | MEDIUM6.88 | libc-dev-bin 2.36-9+deb12u3 fixed in 2.36-9+deb12u14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0861 | MEDIUM6.88 | libc6 2.36-9+deb12u3 fixed in 2.36-9+deb12u14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0861 | MEDIUM6.88 | libc6-dev 2.36-9+deb12u3 fixed in 2.36-9+deb12u14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-28387 | MEDIUM6.88 | libssl3 3.0.11-1~deb12u1 fixed in 3.0.19-1~deb12u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-25210 | MEDIUM6.63 | libexpat1 2.5.0-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6020 | MEDIUM6.63 | libpam-modules 1.5.2-6+deb12u1 fixed in 1.5.2-6+deb12u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-6020 | MEDIUM6.63 | libpam-modules-bin 1.5.2-6+deb12u1 fixed in 1.5.2-6+deb12u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-6020 | MEDIUM6.63 | libpam-runtime 1.5.2-6+deb12u1 fixed in 1.5.2-6+deb12u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-6020 | MEDIUM6.63 | libpam0g 1.5.2-6+deb12u1 fixed in 1.5.2-6+deb12u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-29111 | MEDIUM6.63 | libsystemd0 252.17-1~deb12u1 fixed in 252.39-1~deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69720 | MEDIUM6.63 | libtinfo6 6.4-4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-29111 | MEDIUM6.63 | libudev1 252.17-1~deb12u1 fixed in 252.39-1~deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-49043 | MEDIUM6.63 | libxml2 2.9.14+dfsg-1.3~deb12u1 fixed in 2.9.14+dfsg-1.3~deb12u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11979 | MEDIUM6.63 | libxml2 2.9.14+dfsg-1.3~deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-24928 | MEDIUM6.54 | libxml2 2.9.14+dfsg-1.3~deb12u1 fixed in 2.9.14+dfsg-1.3~deb12u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-6129 | MEDIUM6.5 | libssl3 3.0.11-1~deb12u1 fixed in 3.0.13-1~deb12u1 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-45186 | MEDIUM6.38 | libexpat1 2.5.0-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-41989 | MEDIUM6.38 | libgcrypt20 1.10.1-3 fixed in 1.10.1-3+deb12u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-37370 | MEDIUM6.38 | libgssapi-krb5-2 1.20.1-2+deb12u1 fixed in 1.20.1-2+deb12u2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM6.38 | libgssapi-krb5-2 1.20.1-2+deb12u1 fixed in 1.20.1-2+deb12u5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM6.38 | libgssapi-krb5-2 1.20.1-2+deb12u1 fixed in 1.20.1-2+deb12u5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-37370 | MEDIUM6.38 | libk5crypto3 1.20.1-2+deb12u1 fixed in 1.20.1-2+deb12u2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM6.38 | libk5crypto3 1.20.1-2+deb12u1 fixed in 1.20.1-2+deb12u5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM6.38 | libk5crypto3 1.20.1-2+deb12u1 fixed in 1.20.1-2+deb12u5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-37370 | MEDIUM6.38 | libkrb5-3 1.20.1-2+deb12u1 fixed in 1.20.1-2+deb12u2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM6.38 | libkrb5-3 1.20.1-2+deb12u1 fixed in 1.20.1-2+deb12u5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM6.38 | libkrb5-3 1.20.1-2+deb12u1 fixed in 1.20.1-2+deb12u5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-37370 | MEDIUM6.38 | libkrb5support0 1.20.1-2+deb12u1 fixed in 1.20.1-2+deb12u2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM6.38 | libkrb5support0 1.20.1-2+deb12u1 fixed in 1.20.1-2+deb12u5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM6.38 | libkrb5support0 1.20.1-2+deb12u1 fixed in 1.20.1-2+deb12u5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-31115 | MEDIUM6.38 | liblzma5 5.4.1-0.2 fixed in 5.4.1-1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-27135 | MEDIUM6.38 | libnghttp2-14 1.52.0-1 fixed in 1.52.0-1+deb12u3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-69421 | MEDIUM6.38 | libssl3 3.0.11-1~deb12u1 fixed in 3.0.18-1~deb12u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-28388 | MEDIUM6.38 | libssl3 3.0.11-1~deb12u1 fixed in 3.0.19-1~deb12u2 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-28389 | MEDIUM6.38 | libssl3 3.0.11-1~deb12u1 fixed in 3.0.19-1~deb12u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-28390 | MEDIUM6.38 | libssl3 3.0.11-1~deb12u1 fixed in 3.0.19-1~deb12u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-32414 | MEDIUM6.38 | libxml2 2.9.14+dfsg-1.3~deb12u1 fixed in 2.9.14+dfsg-1.3~deb12u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-32415 | MEDIUM6.38 | libxml2 2.9.14+dfsg-1.3~deb12u1 fixed in 2.9.14+dfsg-1.3~deb12u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-3833 | MEDIUM6.29 | libgnutls30 3.7.9-2 fixed in 3.7.9-2+deb12u7 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42011 | MEDIUM6.29 | libgnutls30 3.7.9-2 fixed in 3.7.9-2+deb12u7 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-69419 | MEDIUM6.29 | libssl3 3.0.11-1~deb12u1 fixed in 3.0.18-1~deb12u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34182 | MEDIUM6.29 | libssl3 3.0.11-1~deb12u1 fixed in 3.0.20-1~deb12u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-54369 | MEDIUM6.03 | libacl1 2.3.1-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42012 | MEDIUM6.03 | libgnutls30 3.7.9-2 fixed in 3.7.9-2+deb12u7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-4802 | MEDIUM5.95 | libc-bin 2.36-9+deb12u3 fixed in 2.36-9+deb12u11 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-4802 | MEDIUM5.95 | libc-dev-bin 2.36-9+deb12u3 fixed in 2.36-9+deb12u11 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-4802 | MEDIUM5.95 | libc6 2.36-9+deb12u3 fixed in 2.36-9+deb12u11 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-4802 | MEDIUM5.95 | libc6-dev 2.36-9+deb12u3 fixed in 2.36-9+deb12u11 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4878 | MEDIUM5.95 | libcap2 1:2.66-4 fixed in 1:2.66-4+deb12u3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5222 | MEDIUM5.95 | libicu72 72.1-3 fixed in 72.1-3+deb12u1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50602 | MEDIUM5.9 | libexpat1 2.5.0-1 fixed in 2.5.0-1+deb12u2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-2236 | MEDIUM5.9 | libgcrypt20 1.10.1-3 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-5981 | MEDIUM5.9 | libgnutls30 3.7.9-2 fixed in 3.7.9-2+deb12u1 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libgssapi-krb5-2 1.20.1-2+deb12u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libk5crypto3 1.20.1-2+deb12u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libkrb5-3 1.20.1-2+deb12u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libkrb5support0 1.20.1-2+deb12u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-6237 | MEDIUM5.9 | libssl3 3.0.11-1~deb12u1 fixed in 3.0.13-1~deb12u1 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-5535 | MEDIUM5.9 | libssl3 3.0.11-1~deb12u1 fixed in 3.0.15-1~deb12u1 | 5.6% Low-Moderate Risk | Directly Exposed |
| CVE-2025-13151 | MEDIUM5.9 | libtasn1-6 4.19.0-2 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-56132 | MEDIUM5.87 | libexpat1 2.5.0-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56403 | MEDIUM5.87 | libexpat1 2.5.0-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56404 | MEDIUM5.87 | libexpat1 2.5.0-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56405 | MEDIUM5.87 | libexpat1 2.5.0-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56406 | MEDIUM5.87 | libexpat1 2.5.0-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56410 | MEDIUM5.87 | libexpat1 2.5.0-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56411 | MEDIUM5.87 | libexpat1 2.5.0-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22185 | MEDIUM5.78 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22185 | MEDIUM5.78 | libldap-common 2.5.13+dfsg-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4105 | MEDIUM5.7 | libsystemd0 252.17-1~deb12u1 fixed in 252.39-1~deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4105 | MEDIUM5.7 | libudev1 252.17-1~deb12u1 fixed in 252.39-1~deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42014 | MEDIUM5.61 | libgnutls30 3.7.9-2 fixed in 3.7.9-2+deb12u7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-9230 | MEDIUM5.6 | libssl3 3.0.11-1~deb12u1 fixed in 3.0.17-1~deb12u3 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2024-4741 | MEDIUM5.6 | libssl3 3.0.11-1~deb12u1 fixed in 3.0.14-1~deb12u1 | 2.9% Low-Moderate Risk | Directly Exposed |
| CVE-2011-3389 | MEDIUM5.59 | libgnutls30 3.7.9-2 No fix yet | 73.3% Actively Exploited | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | libc-bin 2.36-9+deb12u3 fixed in 2.36-9+deb12u14 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc-bin 2.36-9+deb12u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | libc-dev-bin 2.36-9+deb12u3 fixed in 2.36-9+deb12u14 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc-dev-bin 2.36-9+deb12u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | libc6 2.36-9+deb12u3 fixed in 2.36-9+deb12u14 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc6 2.36-9+deb12u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | libc6-dev 2.36-9+deb12u3 fixed in 2.36-9+deb12u14 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc6-dev 2.36-9+deb12u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-6395 | MEDIUM5.52 | libgnutls30 3.7.9-2 fixed in 3.7.9-2+deb12u5 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-24528 | MEDIUM5.52 | libgssapi-krb5-2 1.20.1-2+deb12u1 fixed in 1.20.1-2+deb12u3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-24528 | MEDIUM5.52 | libk5crypto3 1.20.1-2+deb12u1 fixed in 1.20.1-2+deb12u3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-24528 | MEDIUM5.52 | libkrb5-3 1.20.1-2+deb12u1 fixed in 1.20.1-2+deb12u3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-24528 | MEDIUM5.52 | libkrb5support0 1.20.1-2+deb12u1 fixed in 1.20.1-2+deb12u3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-50495 | MEDIUM5.52 | libtinfo6 6.4-4 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2023-39615 | MEDIUM5.52 | libxml2 2.9.14+dfsg-1.3~deb12u1 fixed in 2.9.14+dfsg-1.3~deb12u2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-45322 | MEDIUM5.52 | libxml2 2.9.14+dfsg-1.3~deb12u1 fixed in 2.9.14+dfsg-1.3~deb12u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-0727 | MEDIUM5.5 | libssl3 3.0.11-1~deb12u1 fixed in 3.0.13-1~deb12u1 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-34459 | MEDIUM5.5 | libxml2 2.9.14+dfsg-1.3~deb12u1 fixed in 2.9.14+dfsg-1.3~deb12u2 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-40225 | MEDIUM5.44 | libsystemd0 252.17-1~deb12u1 fixed in 252.39-1~deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40226 | MEDIUM5.44 | libsystemd0 252.17-1~deb12u1 fixed in 252.39-1~deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40225 | MEDIUM5.44 | libudev1 252.17-1~deb12u1 fixed in 252.39-1~deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40226 | MEDIUM5.44 | libudev1 252.17-1~deb12u1 fixed in 252.39-1~deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-54370 | MEDIUM5.35 | libacl1 2.3.1-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-54371 | MEDIUM5.35 | libattr1 1:2.5.1-4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-6780 | MEDIUM5.3 | libc-bin 2.36-9+deb12u3 fixed in 2.36-9+deb12u4 | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33600 | MEDIUM5.3 | libc-bin 2.36-9+deb12u3 fixed in 2.36-9+deb12u7 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc-bin 2.36-9+deb12u3 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc-bin 2.36-9+deb12u3 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2023-6780 | MEDIUM5.3 | libc-dev-bin 2.36-9+deb12u3 fixed in 2.36-9+deb12u4 | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33600 | MEDIUM5.3 | libc-dev-bin 2.36-9+deb12u3 fixed in 2.36-9+deb12u7 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc-dev-bin 2.36-9+deb12u3 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc-dev-bin 2.36-9+deb12u3 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2023-6780 | MEDIUM5.3 | libc6 2.36-9+deb12u3 fixed in 2.36-9+deb12u4 | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33600 | MEDIUM5.3 | libc6 2.36-9+deb12u3 fixed in 2.36-9+deb12u7 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc6 2.36-9+deb12u3 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc6 2.36-9+deb12u3 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2023-6780 | MEDIUM5.3 | libc6-dev 2.36-9+deb12u3 fixed in 2.36-9+deb12u4 | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33600 | MEDIUM5.3 | libc6-dev 2.36-9+deb12u3 fixed in 2.36-9+deb12u7 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc6-dev 2.36-9+deb12u3 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc6-dev 2.36-9+deb12u3 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-59375 | MEDIUM5.3 | libexpat1 2.5.0-1 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-12243 | MEDIUM5.3 | libgnutls30 3.7.9-2 fixed in 3.7.9-2+deb12u4 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2025-32989 | MEDIUM5.3 | libgnutls30 3.7.9-2 fixed in 3.7.9-2+deb12u5 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-5678 | MEDIUM5.3 | libssl3 3.0.11-1~deb12u1 fixed in 3.0.13-1~deb12u1 | 4.5% Low-Moderate Risk | Directly Exposed |
| CVE-2024-4603 | MEDIUM5.3 | libssl3 3.0.11-1~deb12u1 fixed in 3.0.14-1~deb12u1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-12133 | MEDIUM5.3 | libtasn1-6 4.19.0-2 fixed in 4.19.0-2+deb12u1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-13757 | MEDIUM5.27 | libp11-kit0 0.24.1-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-1757 | MEDIUM5.27 | libxml2 2.9.14+dfsg-1.3~deb12u1 fixed in 2.9.14+dfsg-1.3~deb12u6 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libblkid1 2.38.1-5+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1390 | MEDIUM5.18 | libcap2 1:2.66-4 fixed in 1:2.66-4+deb12u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libmount1 2.38.1-5+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libsmartcols1 2.38.1-5+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libuuid1 2.38.1-5+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc-bin 2.36-9+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | libc-bin 2.36-9+deb12u3 fixed in 2.36-9+deb12u14 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc-dev-bin 2.36-9+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | libc-dev-bin 2.36-9+deb12u3 fixed in 2.36-9+deb12u14 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc6 2.36-9+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | libc6 2.36-9+deb12u3 fixed in 2.36-9+deb12u14 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc6-dev 2.36-9+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | libc6-dev 2.36-9+deb12u3 fixed in 2.36-9+deb12u14 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-50219 | MEDIUM5.02 | libexpat1 2.5.0-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56412 | MEDIUM5.02 | libexpat1 2.5.0-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-3576 | MEDIUM5.02 | libgssapi-krb5-2 1.20.1-2+deb12u1 fixed in 1.20.1-2+deb12u4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libgssapi-krb5-2 1.20.1-2+deb12u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-3576 | MEDIUM5.02 | libk5crypto3 1.20.1-2+deb12u1 fixed in 1.20.1-2+deb12u4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libk5crypto3 1.20.1-2+deb12u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-3576 | MEDIUM5.02 | libkrb5-3 1.20.1-2+deb12u1 fixed in 1.20.1-2+deb12u4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkrb5-3 1.20.1-2+deb12u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-3576 | MEDIUM5.02 | libkrb5support0 1.20.1-2+deb12u1 fixed in 1.20.1-2+deb12u4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkrb5support0 1.20.1-2+deb12u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-31790 | MEDIUM5.02 | libssl3 3.0.11-1~deb12u1 fixed in 3.0.19-1~deb12u2 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2025-69420 | MEDIUM5.02 | libssl3 3.0.11-1~deb12u1 fixed in 3.0.18-1~deb12u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-22796 | MEDIUM5.02 | libssl3 3.0.11-1~deb12u1 fixed in 3.0.18-1~deb12u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42770 | MEDIUM5.02 | libssl3 3.0.11-1~deb12u1 fixed in 3.0.20-1~deb12u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-9076 | MEDIUM5.02 | libssl3 3.0.11-1~deb12u1 fixed in 3.0.20-1~deb12u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-7008 | MEDIUM5.02 | libsystemd0 252.17-1~deb12u1 fixed in 252.21-1~deb12u1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-7008 | MEDIUM5.02 | libudev1 252.17-1~deb12u1 fixed in 252.21-1~deb12u1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-0990 | MEDIUM5.02 | libxml2 2.9.14+dfsg-1.3~deb12u1 fixed in 2.9.14+dfsg-1.3~deb12u6 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-45447 | MEDIUM4.86 | openssl 3.0.11-1~deb12u1 fixed in 3.0.20-1~deb12u2 | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2024-2511 | MEDIUM4.81 | libssl3 3.0.11-1~deb12u1 fixed in 3.0.14-1~deb12u1 | 54.0% Actively Exploited | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | gcc-12-base 12.2.0-14 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2023-49582 | MEDIUM4.67 | libapr1 1.7.2-3 fixed in 1.7.2-3+deb12u1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libblkid1 2.38.1-5+b1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-0395 | MEDIUM4.67 | libc-bin 2.36-9+deb12u3 fixed in 2.36-9+deb12u10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-0395 | MEDIUM4.67 | libc-dev-bin 2.36-9+deb12u3 fixed in 2.36-9+deb12u10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-0395 | MEDIUM4.67 | libc6 2.36-9+deb12u3 fixed in 2.36-9+deb12u10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-0395 | MEDIUM4.67 | libc6-dev 2.36-9+deb12u3 fixed in 2.36-9+deb12u10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66382 | MEDIUM4.67 | libexpat1 2.5.0-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32776 | MEDIUM4.67 | libexpat1 2.5.0-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-32777 | MEDIUM4.67 | libexpat1 2.5.0-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32778 | MEDIUM4.67 | libexpat1 2.5.0-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-52426 | MEDIUM4.67 | libexpat1 2.5.0-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libgcc-s1 12.2.0-14 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-26462 | MEDIUM4.67 | libgssapi-krb5-2 1.20.1-2+deb12u1 fixed in 1.20.1-2+deb12u3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-26462 | MEDIUM4.67 | libk5crypto3 1.20.1-2+deb12u1 fixed in 1.20.1-2+deb12u3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-26462 | MEDIUM4.67 | libkrb5-3 1.20.1-2+deb12u1 fixed in 1.20.1-2+deb12u3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-26462 | MEDIUM4.67 | libkrb5support0 1.20.1-2+deb12u1 fixed in 1.20.1-2+deb12u3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libmount1 2.38.1-5+b1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-22365 | MEDIUM4.67 | libpam-modules 1.5.2-6+deb12u1 fixed in 1.5.2-6+deb12u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-22365 | MEDIUM4.67 | libpam-modules-bin 1.5.2-6+deb12u1 fixed in 1.5.2-6+deb12u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-22365 | MEDIUM4.67 | libpam-runtime 1.5.2-6+deb12u1 fixed in 1.5.2-6+deb12u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-22365 | MEDIUM4.67 | libpam0g 1.5.2-6+deb12u1 fixed in 1.5.2-6+deb12u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2017-16231 | MEDIUM4.67 | libpcre3 2:8.39-15 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libsmartcols1 2.38.1-5+b1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-22795 | MEDIUM4.67 | libssl3 3.0.11-1~deb12u1 fixed in 3.0.18-1~deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-7383 | MEDIUM4.67 | libssl3 3.0.11-1~deb12u1 fixed in 3.0.20-1~deb12u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libstdc++6 12.2.0-14 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libuuid1 2.38.1-5+b1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-9714 | MEDIUM4.67 | libxml2 2.9.14+dfsg-1.3~deb12u1 fixed in 2.9.14+dfsg-1.3~deb12u5 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27171 | MEDIUM4.67 | zlib1g 1:1.2.13.dfsg-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-7598 | MEDIUM4.64 | libssh2-1 1.10.0-3+b1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-45445 | MEDIUM4.64 | openssl 3.0.11-1~deb12u1 fixed in 3.0.20-1~deb12u2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-42496 | MEDIUM4.64 | perl-base 5.36.0-7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-5363 | MEDIUM4.5 | openssl 3.0.11-1~deb12u1 fixed in 3.0.11-1~deb12u2 | 3.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-13595 | MEDIUM4.5 | libblkid1 2.38.1-5+b1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libblkid1 2.38.1-5+b1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM4.5 | libc-bin 2.36-9+deb12u3 fixed in 2.36-9+deb12u14 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc-bin 2.36-9+deb12u3 fixed in 2.36-9+deb12u14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM4.5 | libc-dev-bin 2.36-9+deb12u3 fixed in 2.36-9+deb12u14 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc-dev-bin 2.36-9+deb12u3 fixed in 2.36-9+deb12u14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM4.5 | libc6 2.36-9+deb12u3 fixed in 2.36-9+deb12u14 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc6 2.36-9+deb12u3 fixed in 2.36-9+deb12u14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM4.5 | libc6-dev 2.36-9+deb12u3 fixed in 2.36-9+deb12u14 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc6-dev 2.36-9+deb12u3 fixed in 2.36-9+deb12u14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-28834 | MEDIUM4.5 | libgnutls30 3.7.9-2 fixed in 3.7.9-2+deb12u3 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-14831 | MEDIUM4.5 | libgnutls30 3.7.9-2 fixed in 3.7.9-2+deb12u6 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42015 | MEDIUM4.5 | libgnutls30 3.7.9-2 fixed in 3.7.9-2+deb12u7 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-34743 | MEDIUM4.5 | liblzma5 5.4.1-0.2 fixed in 5.4.1-1+deb12u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libmount1 2.38.1-5+b1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libmount1 2.38.1-5+b1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libsmartcols1 2.38.1-5+b1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libsmartcols1 2.38.1-5+b1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42766 | MEDIUM4.5 | libssl3 3.0.11-1~deb12u1 fixed in 3.0.20-1~deb12u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42767 | MEDIUM4.5 | libssl3 3.0.11-1~deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | MEDIUM4.5 | libsystemd0 252.17-1~deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | MEDIUM4.5 | libsystemd0 252.17-1~deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | MEDIUM4.5 | libsystemd0 252.17-1~deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | MEDIUM4.5 | libudev1 252.17-1~deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | MEDIUM4.5 | libudev1 252.17-1~deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | MEDIUM4.5 | libudev1 252.17-1~deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libuuid1 2.38.1-5+b1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libuuid1 2.38.1-5+b1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-7264 | MEDIUM4.48 | libcurl4 7.88.1-10+deb12u4 fixed in 7.88.1-10+deb12u7 | 17.3% High Exploitation Risk | Post-Exploit |
| CVE-2024-28085 | MEDIUM4.4 | libblkid1 2.38.1-5+b1 fixed in 2.38.1-5+deb12u1 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-28085 | MEDIUM4.4 | libmount1 2.38.1-5+b1 fixed in 2.38.1-5+deb12u1 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-28085 | MEDIUM4.4 | libsmartcols1 2.38.1-5+b1 fixed in 2.38.1-5+deb12u1 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-28085 | MEDIUM4.4 | libuuid1 2.38.1-5+b1 fixed in 2.38.1-5+deb12u1 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42250 | MEDIUM4.25 | libbz2-1.0 1.0.8-5+b1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc-bin 2.36-9+deb12u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc-bin 2.36-9+deb12u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc-dev-bin 2.36-9+deb12u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc-dev-bin 2.36-9+deb12u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc6 2.36-9+deb12u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc6 2.36-9+deb12u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc6-dev 2.36-9+deb12u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc6-dev 2.36-9+deb12u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-28835 | MEDIUM4.25 | libgnutls30 3.7.9-2 fixed in 3.7.9-2+deb12u3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libgssapi-krb5-2 1.20.1-2+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libk5crypto3 1.20.1-2+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libkrb5-3 1.20.1-2+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libkrb5support0 1.20.1-2+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-34180 | MEDIUM4.25 | libssl3 3.0.11-1~deb12u1 fixed in 3.0.20-1~deb12u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-55200 | MEDIUM4.23 | libssh2-1 1.10.0-3+b1 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2020-15719 | MEDIUM4.2 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-15719 | MEDIUM4.2 | libldap-common 2.5.13+dfsg-5 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-8286 | MEDIUM4.13 | libcurl4 7.88.1-10+deb12u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | MEDIUM4.13 | libcurl4 7.88.1-10+deb12u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-28387 | MEDIUM4.13 | openssl 3.0.11-1~deb12u1 fixed in 3.0.19-1~deb12u2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2024-2961 | MEDIUM4.12 | libc-bin 2.36-9+deb12u3 fixed in 2.36-9+deb12u6 | 88.3% Actively Exploited | Post-Exploit |
| CVE-2024-2961 | MEDIUM4.12 | libc-dev-bin 2.36-9+deb12u3 fixed in 2.36-9+deb12u6 | 88.3% Actively Exploited | Post-Exploit |
| CVE-2024-2961 | MEDIUM4.12 | libc6-dev 2.36-9+deb12u3 fixed in 2.36-9+deb12u6 | 88.3% Actively Exploited | Post-Exploit |
| CVE-2023-4039 | MEDIUM4.08 | gcc-12-base 12.2.0-14 fixed in 12.2.0-14+deb12u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | libgcc-s1 12.2.0-14 fixed in 12.2.0-14+deb12u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-54411 | MEDIUM4.08 | libpam-modules 1.5.2-6+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54411 | MEDIUM4.08 | libpam-modules-bin 1.5.2-6+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54411 | MEDIUM4.08 | libpam-runtime 1.5.2-6+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54411 | MEDIUM4.08 | libpam0g 1.5.2-6+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | libstdc++6 12.2.0-14 fixed in 12.2.0-14+deb12u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-15467 | MEDIUM4.06 | libssl3 3.0.11-1~deb12u1 fixed in 3.0.18-1~deb12u2 | 47.6% High Exploitation Risk | Post-Exploit |
| CVE-2025-15467 | MEDIUM4.06 | openssl 3.0.11-1~deb12u1 fixed in 3.0.18-1~deb12u2 | 47.6% High Exploitation Risk | Post-Exploit |
| CVE-2026-27456 | MEDIUM4 | libblkid1 2.38.1-5+b1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2017-14159 | MEDIUM4 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2017-14159 | MEDIUM4 | libldap-common 2.5.13+dfsg-5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libmount1 2.38.1-5+b1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-10041 | MEDIUM4 | libpam-modules 1.5.2-6+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-10041 | MEDIUM4 | libpam-modules-bin 1.5.2-6+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-10041 | MEDIUM4 | libpam-runtime 1.5.2-6+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-10041 | MEDIUM4 | libpam0g 1.5.2-6+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libsmartcols1 2.38.1-5+b1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-13176 | MEDIUM4 | libssl3 3.0.11-1~deb12u1 fixed in 3.0.16-1~deb12u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-68160 | MEDIUM4 | libssl3 3.0.11-1~deb12u1 fixed in 3.0.18-1~deb12u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-4598 | MEDIUM4 | libsystemd0 252.17-1~deb12u1 fixed in 252.38-1~deb12u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-4598 | MEDIUM4 | libudev1 252.17-1~deb12u1 fixed in 252.38-1~deb12u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libuuid1 2.38.1-5+b1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc-bin 2.36-9+deb12u3 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33601 | MEDIUM4 | libc-bin 2.36-9+deb12u3 fixed in 2.36-9+deb12u7 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc-dev-bin 2.36-9+deb12u3 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33601 | MEDIUM4 | libc-dev-bin 2.36-9+deb12u3 fixed in 2.36-9+deb12u7 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc6 2.36-9+deb12u3 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33601 | MEDIUM4 | libc6 2.36-9+deb12u3 fixed in 2.36-9+deb12u7 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc6-dev 2.36-9+deb12u3 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33601 | MEDIUM4 | libc6-dev 2.36-9+deb12u3 fixed in 2.36-9+deb12u7 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-69720 | LOW3.98 | ncurses-bin 6.4-4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-47038 | LOW3.98 | perl-base 5.36.0-7 fixed in 5.36.0-7+deb12u1 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-48962 | LOW3.98 | perl-base 5.36.0-7 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-46218 | LOW3.9 | libcurl4 7.88.1-10+deb12u4 fixed in 7.88.1-10+deb12u5 | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2024-9681 | LOW3.9 | libcurl4 7.88.1-10+deb12u4 fixed in 7.88.1-10+deb12u9 | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-11856 | LOW3.9 | libcurl4 7.88.1-10+deb12u4 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2023-6129 | LOW3.9 | openssl 3.0.11-1~deb12u1 fixed in 3.0.13-1~deb12u1 | 2.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-41992 | LOW3.82 | gzip 1.12-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-12064 | LOW3.82 | libcurl4 7.88.1-10+deb12u4 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-5773 | LOW3.82 | libcurl4 7.88.1-10+deb12u4 fixed in 7.88.1-10+deb12u15 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW3.82 | libcurl4 7.88.1-10+deb12u4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW3.82 | libcurl4 7.88.1-10+deb12u4 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-8932 | LOW3.82 | libcurl4 7.88.1-10+deb12u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-55199 | LOW3.82 | libssh2-1 1.10.0-3+b1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-69421 | LOW3.82 | openssl 3.0.11-1~deb12u1 fixed in 3.0.18-1~deb12u2 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-28388 | LOW3.82 | openssl 3.0.11-1~deb12u1 fixed in 3.0.19-1~deb12u2 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-28389 | LOW3.82 | openssl 3.0.11-1~deb12u1 fixed in 3.0.19-1~deb12u2 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-28390 | LOW3.82 | openssl 3.0.11-1~deb12u1 fixed in 3.0.19-1~deb12u2 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-42497 | LOW3.82 | perl-base 5.36.0-7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9538 | LOW3.82 | perl-base 5.36.0-7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9547 | LOW3.77 | libcurl4 7.88.1-10+deb12u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-69419 | LOW3.77 | openssl 3.0.11-1~deb12u1 fixed in 3.0.18-1~deb12u2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-34182 | LOW3.77 | openssl 3.0.11-1~deb12u1 fixed in 3.0.20-1~deb12u2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56406 | LOW3.72 | perl-base 5.36.0-7 fixed in 5.36.0-7+deb12u2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2011-3374 | LOW3.7 | libapt-pkg6.0 2.6.1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-9143 | LOW3.7 | libssl3 3.0.11-1~deb12u1 fixed in 3.0.15-1~deb12u1 | 6.0% Low-Moderate Risk | Directly Exposed |
| CVE-2005-2541 | LOW3.6 | tar 1.34+dfsg-1.2 No fix yet | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2025-68973 | LOW3.57 | gpgv 2.2.40-1.1 fixed in 2.2.40-1.1+deb12u2 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-8058 | LOW3.57 | libc-bin 2.36-9+deb12u3 fixed in 2.36-9+deb12u13 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8058 | LOW3.57 | libc-dev-bin 2.36-9+deb12u3 fixed in 2.36-9+deb12u13 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8058 | LOW3.57 | libc6 2.36-9+deb12u3 fixed in 2.36-9+deb12u13 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8058 | LOW3.57 | libc6-dev 2.36-9+deb12u3 fixed in 2.36-9+deb12u13 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-11053 | LOW3.54 | libcurl4 7.88.1-10+deb12u4 fixed in 7.88.1-10+deb12u10 | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2023-6237 | LOW3.54 | openssl 3.0.11-1~deb12u1 fixed in 3.0.13-1~deb12u1 | 2.3% Low-Moderate Risk | Post-Exploit |
| CVE-2024-5535 | LOW3.54 | openssl 3.0.11-1~deb12u1 fixed in 3.0.15-1~deb12u1 | 5.6% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc-bin 2.36-9+deb12u3 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc-dev-bin 2.36-9+deb12u3 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc6 2.36-9+deb12u3 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc6-dev 2.36-9+deb12u3 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2023-45853 | LOW3.53 | zlib1g 1:1.2.13.dfsg-1 No fix yet | 2.9% Low-Moderate Risk | Post-Exploit |
| CVE-2023-50387 | LOW3.51 | libudev1 252.17-1~deb12u1 fixed in 252.23-1~deb12u1 | 100.0% Actively Exploited | Post-Exploit |
| CVE-2023-50868 | LOW3.51 | libudev1 252.17-1~deb12u1 fixed in 252.23-1~deb12u1 | 81.7% Actively Exploited | Post-Exploit |
| CVE-2024-6119 | LOW3.51 | openssl 3.0.11-1~deb12u1 fixed in 3.0.14-1~deb12u2 | 66.6% Actively Exploited | Post-Exploit |
| CVE-2026-1965 | LOW3.47 | libcurl4 7.88.1-10+deb12u4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-14819 | LOW3.47 | libcurl4 7.88.1-10+deb12u4 fixed in 7.88.1-10+deb12u15 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2024-33602 | LOW3.4 | libc-bin 2.36-9+deb12u3 fixed in 2.36-9+deb12u7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | libc-bin 2.36-9+deb12u3 fixed in 2.36-9+deb12u14 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-33602 | LOW3.4 | libc-dev-bin 2.36-9+deb12u3 fixed in 2.36-9+deb12u7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | libc-dev-bin 2.36-9+deb12u3 fixed in 2.36-9+deb12u14 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-33602 | LOW3.4 | libc6 2.36-9+deb12u3 fixed in 2.36-9+deb12u7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | libc6 2.36-9+deb12u3 fixed in 2.36-9+deb12u14 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-33602 | LOW3.4 | libc6-dev 2.36-9+deb12u3 fixed in 2.36-9+deb12u7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | libc6-dev 2.36-9+deb12u3 fixed in 2.36-9+deb12u14 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-9820 | LOW3.4 | libgnutls30 3.7.9-2 fixed in 3.7.9-2+deb12u6 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69418 | LOW3.4 | libssl3 3.0.11-1~deb12u1 fixed in 3.0.18-1~deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-9230 | LOW3.36 | openssl 3.0.11-1~deb12u1 fixed in 3.0.17-1~deb12u3 | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2024-4741 | LOW3.36 | openssl 3.0.11-1~deb12u1 fixed in 3.0.14-1~deb12u1 | 2.9% Low-Moderate Risk | Post-Exploit |
| CVE-2016-2781 | LOW3.31 | coreutils 9.1-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-8096 | LOW3.31 | libcurl4 7.88.1-10+deb12u4 fixed in 7.88.1-10+deb12u8 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-3784 | LOW3.31 | libcurl4 7.88.1-10+deb12u4 fixed in 7.88.1-10+deb12u15 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW3.31 | libcurl4 7.88.1-10+deb12u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW3.31 | libcurl4 7.88.1-10+deb12u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | libcurl4 7.88.1-10+deb12u4 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-14524 | LOW3.31 | libcurl4 7.88.1-10+deb12u4 fixed in 7.88.1-10+deb12u15 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-15661 | LOW3.31 | libssh2-1 1.10.0-3+b1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-50495 | LOW3.31 | ncurses-bin 6.4-4 No fix yet | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2025-15649 | LOW3.31 | perl-base 5.36.0-7 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-0727 | LOW3.3 | openssl 3.0.11-1~deb12u1 fixed in 3.0.13-1~deb12u1 | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2022-48303 | LOW3.3 | tar 1.34+dfsg-1.2 fixed in 1.34+dfsg-1.2+deb12u1 | 4.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-13221 | LOW3.28 | perl-base 5.36.0-7 No fix yet | — | Post-Exploit |
| CVE-2024-2379 | LOW3.24 | libcurl4 7.88.1-10+deb12u4 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2026-5958 | LOW3.21 | sed 4.9-1 fixed in 4.9-1+deb12u1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-46219 | LOW3.18 | libcurl4 7.88.1-10+deb12u4 fixed in 7.88.1-10+deb12u5 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2024-2004 | LOW3.18 | libcurl4 7.88.1-10+deb12u4 fixed in 7.88.1-10+deb12u6 | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2023-5678 | LOW3.18 | openssl 3.0.11-1~deb12u1 fixed in 3.0.13-1~deb12u1 | 4.5% Low-Moderate Risk | Post-Exploit |
| CVE-2024-4603 | LOW3.18 | openssl 3.0.11-1~deb12u1 fixed in 3.0.14-1~deb12u1 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-41080 | LOW3.15 | libexpat1 2.5.0-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5419 | LOW3.15 | libgnutls30 3.7.9-2 fixed in 3.7.9-2+deb12u7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-45446 | LOW3.15 | libssl3 3.0.11-1~deb12u1 fixed in 3.0.20-1~deb12u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-0989 | LOW3.15 | libxml2 2.9.14+dfsg-1.3~deb12u1 fixed in 2.9.14+dfsg-1.3~deb12u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | LOW3.11 | bsdutils 1:2.38.1-5+b1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | mount 2.38.1-5+b1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | util-linux 2.38.1-5+b1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | util-linux-extra 2.38.1-5+b1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-2398 | LOW3.1 | libcurl4 7.88.1-10+deb12u4 fixed in 7.88.1-10+deb12u6 | 36.1% High Exploitation Risk | Post-Exploit |
| CVE-2025-9232 | LOW3.1 | libssl3 3.0.11-1~deb12u1 fixed in 3.0.17-1~deb12u3 | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-57432 | LOW3.02 | perl-base 5.36.0-7 No fix yet | — | Post-Exploit |
| CVE-2025-10966 | LOW3.01 | libcurl4 7.88.1-10+deb12u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-31790 | LOW3.01 | openssl 3.0.11-1~deb12u1 fixed in 3.0.19-1~deb12u2 | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2025-69420 | LOW3.01 | openssl 3.0.11-1~deb12u1 fixed in 3.0.18-1~deb12u2 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-22796 | LOW3.01 | openssl 3.0.11-1~deb12u1 fixed in 3.0.18-1~deb12u2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-42770 | LOW3.01 | openssl 3.0.11-1~deb12u1 fixed in 3.0.20-1~deb12u2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-9076 | LOW3.01 | openssl 3.0.11-1~deb12u1 fixed in 3.0.20-1~deb12u2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-40909 | LOW3.01 | perl-base 5.36.0-7 fixed in 5.36.0-7+deb12u3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-31789 | LOW3 | openssl 3.0.11-1~deb12u1 fixed in 3.0.19-1~deb12u2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-8376 | LOW3 | perl-base 5.36.0-7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-31484 | LOW2.92 | perl-base 5.36.0-7 fixed in 5.36.0-7+deb12u3 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2023-31486 | LOW2.92 | perl-base 5.36.0-7 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2026-3783 | LOW2.91 | libcurl4 7.88.1-10+deb12u4 fixed in 7.88.1-10+deb12u15 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-2511 | LOW2.89 | openssl 3.0.11-1~deb12u1 fixed in 3.0.14-1~deb12u1 | 54.0% Actively Exploited | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | bsdutils 1:2.38.1-5+b1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-4641 | LOW2.8 | login 1:4.13+dfsg1-1+b1 fixed in 1:4.13+dfsg1-1+deb12u1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | mount 2.38.1-5+b1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-22795 | LOW2.8 | openssl 3.0.11-1~deb12u1 fixed in 3.0.18-1~deb12u2 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-7383 | LOW2.8 | openssl 3.0.11-1~deb12u1 fixed in 3.0.20-1~deb12u2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-4641 | LOW2.8 | passwd 1:4.13+dfsg1-1+b1 fixed in 1:4.13+dfsg1-1+deb12u1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5704 | LOW2.8 | tar 1.34+dfsg-1.2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | util-linux 2.38.1-5+b1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | util-linux-extra 2.38.1-5+b1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2013-4392 | LOW2.8 | libsystemd0 252.17-1~deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libsystemd0 252.17-1~deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6141 | LOW2.8 | libtinfo6 6.4-4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libudev1 252.17-1~deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libudev1 252.17-1~deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8732 | LOW2.8 | libxml2 2.9.14+dfsg-1.3~deb12u1 fixed in 2.9.14+dfsg-1.3~deb12u6 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | LOW2.7 | bsdutils 1:2.38.1-5+b1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | bsdutils 1:2.38.1-5+b1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-4873 | LOW2.7 | libcurl4 7.88.1-10+deb12u4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW2.7 | libcurl4 7.88.1-10+deb12u4 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-7168 | LOW2.7 | libcurl4 7.88.1-10+deb12u4 fixed in 7.88.1-10+deb12u15 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | mount 2.38.1-5+b1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | mount 2.38.1-5+b1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42766 | LOW2.7 | openssl 3.0.11-1~deb12u1 fixed in 3.0.20-1~deb12u2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-42767 | LOW2.7 | openssl 3.0.11-1~deb12u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-12087 | LOW2.7 | perl-base 5.36.0-7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | util-linux 2.38.1-5+b1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | util-linux 2.38.1-5+b1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | util-linux-extra 2.38.1-5+b1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | util-linux-extra 2.38.1-5+b1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-28085 | LOW2.64 | bsdutils 1:2.38.1-5+b1 fixed in 2.38.1-5+deb12u1 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2024-28085 | LOW2.64 | mount 2.38.1-5+b1 fixed in 2.38.1-5+deb12u1 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2024-28085 | LOW2.64 | util-linux 2.38.1-5+b1 fixed in 2.38.1-5+deb12u1 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2024-28085 | LOW2.64 | util-linux-extra 2.38.1-5+b1 fixed in 2.38.1-5+deb12u1 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-34180 | LOW2.55 | openssl 3.0.11-1~deb12u1 fixed in 3.0.20-1~deb12u2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-48959 | LOW2.55 | perl-base 5.36.0-7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-48961 | LOW2.55 | perl-base 5.36.0-7 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2007-5686 | LOW2.5 | login 1:4.13+dfsg1-1+b1 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2007-5686 | LOW2.5 | passwd 1:4.13+dfsg1-1+b1 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-0992 | LOW2.46 | libxml2 2.9.14+dfsg-1.3~deb12u1 fixed in 2.9.14+dfsg-1.3~deb12u6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-10148 | LOW2.45 | libcurl4 7.88.1-10+deb12u4 fixed in 7.88.1-10+deb12u15 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.45 | libcurl4 7.88.1-10+deb12u4 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | bsdutils 1:2.38.1-5+b1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2017-18018 | LOW2.4 | coreutils 9.1-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gpgv 2.2.40-1.1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gpgv 2.2.40-1.1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-41991 | LOW2.4 | gzip 1.12-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-10536 | LOW2.4 | libcurl4 7.88.1-10+deb12u4 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | libcurl4 7.88.1-10+deb12u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | mount 2.38.1-5+b1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-13176 | LOW2.4 | openssl 3.0.11-1~deb12u1 fixed in 3.0.16-1~deb12u1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-68160 | LOW2.4 | openssl 3.0.11-1~deb12u1 fixed in 3.0.18-1~deb12u2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | util-linux 2.38.1-5+b1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | util-linux-extra 2.38.1-5+b1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-0725 | LOW2.4 | libcurl4 7.88.1-10+deb12u4 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2025-5278 | LOW2.24 | coreutils 9.1-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2011-3374 | LOW2.22 | apt 2.6.1 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2024-9143 | LOW2.22 | openssl 3.0.11-1~deb12u1 fixed in 3.0.15-1~deb12u1 | 6.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-24515 | LOW2.12 | libexpat1 2.5.0-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6170 | LOW2.12 | libxml2 2.9.14+dfsg-1.3~deb12u1 fixed in 2.9.14+dfsg-1.3~deb12u3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69418 | LOW2.04 | openssl 3.0.11-1~deb12u1 fixed in 3.0.18-1~deb12u2 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45446 | LOW1.89 | openssl 3.0.11-1~deb12u1 fixed in 3.0.20-1~deb12u2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-9232 | LOW1.86 | openssl 3.0.11-1~deb12u1 fixed in 3.0.17-1~deb12u3 | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2024-56433 | LOW1.84 | login 1:4.13+dfsg1-1+b1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-56433 | LOW1.84 | passwd 1:4.13+dfsg1-1+b1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpgv 2.2.40-1.1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-29383 | LOW1.68 | login 1:4.13+dfsg1-1+b1 fixed in 1:4.13+dfsg1-1+deb12u1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-6141 | LOW1.68 | ncurses-bin 6.4-4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-29383 | LOW1.68 | passwd 1:4.13+dfsg1-1+b1 fixed in 1:4.13+dfsg1-1+deb12u1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2011-4116 | LOW1.68 | perl-base 5.36.0-7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-39804 | LOW1.68 | tar 1.34+dfsg-1.2 fixed in 1.34+dfsg-1.2+deb12u1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW1.48 | gpgv 2.2.40-1.1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23112 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.164-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-47685 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2026-43037 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-5178 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 9.1% Low-Moderate Risk | Not Applicable |
| CVE-2024-25744 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.69-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-47659 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-8805 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-23395 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-10263 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31788 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-39191 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-58087 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43112 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43114 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-52434 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-43133 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2013-7445 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 2.7% Low-Moderate Risk | Not Applicable |
| CVE-2019-19449 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2019-19814 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 3.3% Low-Moderate Risk | Not Applicable |
| CVE-2021-3847 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-2176 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52436 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52438 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52439 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52444 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52445 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52451 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52452 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52457 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52464 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52469 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52475 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52482 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52483 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52491 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52494 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52509 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52510 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52515 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52524 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52530 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52531 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52572 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52594 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52599 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52600 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52603 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52604 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52612 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52614 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52621 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52624 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-52637 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52642 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52664 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52667 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52669 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52679 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52691 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52748 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52751 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52752 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52755 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 26.9% High Exploitation Risk | Not Applicable |
| CVE-2023-52757 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52764 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52772 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52775 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.66-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52777 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52795 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52796 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52799 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52804 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52805 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52807 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52812 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52816 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52818 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52835 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52836 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52837 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52840 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52846 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52851 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52852 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52854 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52859 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52864 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52867 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52868 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52916 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52927 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-53194 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53218 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53363 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.137-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-5345 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-53510 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-54285 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-5633 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-5717 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-6111 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-6817 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.69-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-0646 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.69-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-0841 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-1085 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-1086 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 28.1% High Exploitation Risk | Not Applicable |
| CVE-2024-21803 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-22705 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-23307 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-26581 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2024-26582 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26588 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26589 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26592 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-26598 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26599 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26610 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26622 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26625 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26689 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26704 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26736 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26739 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.137-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26742 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26748 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26749 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26753 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26754 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26782 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26793 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26800 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26836 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26856 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26865 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26882 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-26883 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26884 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26885 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26895 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26898 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26907 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26913 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26914 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26928 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26933 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26934 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26936 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26944 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26951 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26952 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-26955 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26956 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26957 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26958 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26961 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26965 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26981 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26983 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26988 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26989 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26996 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27000 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27008 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27018 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27022 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27024 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27043 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27045 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27065 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27075 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27395 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27396 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27398 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-35789 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-35791 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35847 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35855 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35861 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35862 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35863 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35864 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35866 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35867 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-35868 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35886 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-35887 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35905 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35932 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36012 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36015 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-36880 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36886 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2024-36898 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36904 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-36906 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36914 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36934 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-36940 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36971 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 2.7% Low-Moderate Risk | Not Applicable |
| CVE-2024-36973 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36974 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-36978 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-36979 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38545 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38552 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38555 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38556 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38568 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38569 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38570 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38577 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38578 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38581 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38583 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38586 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38588 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38610 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38627 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38630 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38667 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39277 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39463 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-39480 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-39494 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-39495 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-39496 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-39502 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-39510 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40899 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40900 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40901 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40902 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40903 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40906 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40913 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40920 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40927 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40935 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40939 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40940 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40954 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40956 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40958 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40974 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40989 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40994 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40996 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41000 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41011 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41028 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41039 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41042 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41045 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41046 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41050 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41051 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41058 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41069 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41070 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41073 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41074 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41087 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41092 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.98-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41096 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42086 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42092 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42104 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.98-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42105 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.98-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42118 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42119 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.98-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42120 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.98-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42121 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.98-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42136 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42138 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42147 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42148 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.98-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42159 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42160 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42271 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42280 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42284 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42285 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42301 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42302 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42313 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42314 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43830 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43839 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-43842 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43858 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43873 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43900 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44934 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44940 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44941 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44942 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44949 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44951 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44967 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44974 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-44977 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-44985 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-44986 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44987 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-44998 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-45026 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46673 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46674 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46713 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46725 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46729 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46738 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46740 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46744 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46746 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46759 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46782 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46786 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46798 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46800 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46804 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46811 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46812 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46813 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46814 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46815 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46818 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46821 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46828 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46830 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46836 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46844 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46849 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46852 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46853 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46859 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46871 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47670 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47682 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47691 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47695 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47696 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-47697 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-47698 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-47701 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47718 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47727 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47730 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-47742 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-47745 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-47748 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47750 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47751 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49852 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49853 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49882 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49883 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49884 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49889 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49894 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49895 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49924 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49930 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49936 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49950 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49960 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49966 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49969 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49982 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49983 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49986 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49989 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49991 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49992 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49996 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50007 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50029 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50047 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50051 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50055 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50063 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50067 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50073 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50074 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50088 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50121 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50124 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50125 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50126 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50127 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50131 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50143 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50150 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50151 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50155 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50180 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50186 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50209 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50215 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50217 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50226 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50230 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50235 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50242 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50246 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50257 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50261 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50262 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50264 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-50267 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50269 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50276 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50282 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50283 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53057 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53059 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53061 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53068 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53096 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53103 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53104 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 3.3% Low-Moderate Risk | Not Applicable |
| CVE-2024-53106 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53141 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-53142 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53156 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53165 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53166 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53168 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53170 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53171 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53173 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53179 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53203 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53206 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53208 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53213 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53214 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53218 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53227 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53237 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53239 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-56538 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56548 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56551 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56570 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56581 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56582 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.124-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56595 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-56596 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56598 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56600 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56601 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56602 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56603 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56604 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56605 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56606 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56608 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56609 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.137-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56614 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-56615 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-56616 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56619 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56626 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-56628 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56631 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.128-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-56633 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-56640 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56642 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56651 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56658 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56675 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56704 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56708 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56759 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.124-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56765 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56766 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56775 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57792 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-57798 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57849 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57850 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57887 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57892 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57896 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.124-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57900 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-57904 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57917 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57951 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57980 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57998 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58002 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58034 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58055 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58069 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58072 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58093 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58240 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21631 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21671 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21680 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21687 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21692 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.128-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-21704 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-21715 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21724 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21734 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21735 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21756 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2025-21772 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21780 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21785 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-21791 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21811 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21812 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21855 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21858 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21863 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21914 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21919 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21927 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21928 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21934 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21945 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21967 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21968 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21969 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21979 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21991 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22020 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22022 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22040 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-22041 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-22056 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22083 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22088 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22126 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23133 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23142 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23158 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37738 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37750 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37752 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37777 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37778 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-37786 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37789 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37796 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37797 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.137-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37798 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37803 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.137-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37810 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.137-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37817 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.137-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37819 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37822 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37823 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.137-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37839 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37840 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37849 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37854 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37861 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37885 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.137-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37890 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37892 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37899 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-37903 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37913 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37914 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37921 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37923 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37924 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.140-1 | 9.8% Low-Moderate Risk | Not Applicable |
| CVE-2025-37926 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37927 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37928 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.140-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-37947 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37952 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37957 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37979 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.137-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37991 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38000 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38022 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38024 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38052 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38068 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38069 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38077 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38079 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38117 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38118 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38129 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38131 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38146 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38154 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38157 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38180 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38182 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38183 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38198 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38201 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38206 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38211 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38212 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38226 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38227 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38230 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38236 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38239 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38245 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38248 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38250 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38257 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38259 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38280 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38298 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38313 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38323 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38346 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38348 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38350 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38352 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2025-38361 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38369 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38375 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38377 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38385 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38389 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38396 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38401 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38403 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38415 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38416 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38422 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38425 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38428 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38437 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38443 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38456 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38459 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38464 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38471 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38476 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38485 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38488 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-38494 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38500 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.148-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38512 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38527 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38535 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38538 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38548 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38550 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38552 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38555 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.148-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38563 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.148-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-38565 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.148-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38572 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.148-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38574 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.148-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38579 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.148-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38582 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38584 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38585 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38593 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38595 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38618 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.148-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38627 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38653 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.148-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38666 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.148-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38676 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-38685 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38697 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38699 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38702 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38704 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38707 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38708 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38718 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38722 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38724 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38729 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38734 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39686 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39689 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39691 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39701 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39730 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.148-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39738 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39743 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39766 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39776 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39783 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39788 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39790 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39797 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39810 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39823 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39824 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39828 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39835 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39841 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39849 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39859 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39860 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39863 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39864 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39866 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-39870 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39871 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39873 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39877 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39880 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39881 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39911 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39913 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39944 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39945 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39951 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39952 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39955 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39957 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39967 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40149 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40364 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68817 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71068 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71071 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71073 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71075 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71078 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71082 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71086 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71089 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71091 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71123 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71137 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71152 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71162 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71220 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71238 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-22980 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23001 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23010 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23025 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23068 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23073 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23074 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23078 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23083 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23089 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23098 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23111 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.164-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-23156 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23171 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23193 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23208 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23209 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23216 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23221 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23226 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-23227 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23231 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-23234 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23262 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23281 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23319 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23343 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23359 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23361 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23378 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23408 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23410 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23411 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23422 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23428 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-23447 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23448 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31399 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31402 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31431 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 96.3% Actively Exploited | Not Applicable |
| CVE-2026-31452 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31455 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31485 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31488 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31489 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31493 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31500 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31527 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31532 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31566 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31576 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31578 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31580 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31581 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31583 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31686 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31696 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31702 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31709 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31715 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31720 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31729 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31747 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31748 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31759 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31787 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43015 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43020 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43027 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43049 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43128 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43150 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43196 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43205 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43250 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43284 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-3 | 93.2% Actively Exploited | Not Applicable |
| CVE-2026-43328 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43329 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43378 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43426 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43458 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43499 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43500 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-3 | 92.8% Actively Exploited | Not Applicable |
| CVE-2026-45839 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45866 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45867 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45879 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45885 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45891 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45902 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45914 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45916 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45920 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45936 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45946 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45984 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-45996 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46004 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46047 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46068 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46069 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46075 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46122 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46136 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46163 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46180 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46189 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46219 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46234 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46241 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46243 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.174-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46267 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46285 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46294 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46300 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.174-1 | 3.7% Low-Moderate Risk | Not Applicable |
| CVE-2026-46301 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46323 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46333 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.172-1 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2026-52943 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52962 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52969 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52992 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53004 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53129 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53136 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53137 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53143 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53148 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53156 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53157 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53195 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53262 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53272 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53294 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53296 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53359 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53362 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40258 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40277 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46274 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2019-12456 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-19378 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2020-11725 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-26934 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-25265 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2022-3238 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-26242 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-3640 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-base 6.4-4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-39971 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-46838 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2023-52340 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-6356 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2023-6535 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2023-6536 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2024-26620 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2024-42225 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.98-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-49997 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2024-50083 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2024-57791 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-38501 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.148-1 | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-22998 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-43501 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46195 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-53266 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39973 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39982 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40240 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68349 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31669 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43110 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43186 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-43190 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53071 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2019-19070 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 2.8% Low-Moderate Risk | Not Applicable |
| CVE-2022-0400 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2024-0565 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.69-1 | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2025-40170 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42093 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31607 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43038 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-53781 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39981 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40141 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40176 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40269 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40294 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40304 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68800 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23243 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43078 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43248 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-52501 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52504 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52507 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52519 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52525 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52565 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52588 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52598 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52640 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52682 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52766 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52842 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53034 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53486 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-6606 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-26593 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26594 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 78.4% Actively Exploited | Not Applicable |
| CVE-2024-26597 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26664 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26665 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26669 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26673 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26763 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26791 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26954 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26982 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27401 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-34777 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35785 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35849 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-35871 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-35896 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35937 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35939 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35963 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35964 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-35965 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35966 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-35967 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36032 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36033 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36883 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-36915 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-36916 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-36931 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36960 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-37078 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38381 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38538 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38560 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38585 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38599 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38621 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38635 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38659 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39467 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39469 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39471 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39487 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39499 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40929 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40978 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41013 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41014 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41059 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41090 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41091 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41935 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42094 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42292 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43877 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44983 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-44999 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46722 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46723 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46724 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46731 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46743 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46747 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46774 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46854 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46865 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47686 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47723 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-47757 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49860 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49861 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49900 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50033 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50035 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50115 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50128 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50164 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50193 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50247 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50250 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50268 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50278 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50279 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50301 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-52332 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53082 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53099 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53147 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53150 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2024-53155 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56597 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56627 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-56650 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-56663 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57838 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57906 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57907 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57908 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57910 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57911 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57912 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57925 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57929 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57945 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57982 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58007 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58014 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58054 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21647 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.128-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-21719 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21782 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21794 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21905 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21920 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21946 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21950 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21985 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21993 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22038 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22039 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-22079 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22104 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22107 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22121 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23156 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23157 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37739 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37749 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37780 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37785 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37879 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.137-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38004 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38027 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38081 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38088 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38103 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38111 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38153 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38159 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38204 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38249 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38286 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38320 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38342 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38395 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38445 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38482 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38483 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38497 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38502 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38529 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38530 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38556 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38616 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38636 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38652 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.148-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38670 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38677 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38679 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38680 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38713 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38714 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38715 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38728 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38736 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39682 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39683 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39685 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39687 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39710 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39719 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39735 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39744 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39757 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39760 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39806 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39817 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39839 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39853 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39869 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39883 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39891 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39901 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39943 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40082 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71093 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71112 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71116 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71133 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71136 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22984 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-23076 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23099 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23102 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23187 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23204 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23235 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23315 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23318 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23327 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23388 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23397 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31568 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31778 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43040 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43052 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43141 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43241 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43281 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43380 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43386 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43427 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43449 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43450 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43453 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45893 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45943 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45957 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45994 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46022 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46033 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46064 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46130 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46191 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46293 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52968 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53138 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53149 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53179 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53255 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53303 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53309 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-52502 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-25742 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-25743 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36013 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-53174 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53216 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56558 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58013 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21753 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21762 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21887 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40064 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40301 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40322 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40349 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40351 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68168 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68183 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68324 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68347 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68366 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68724 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23455 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31613 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31685 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31786 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43051 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43126 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43414 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46053 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46056 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46120 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46135 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46150 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46209 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46259 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2008-4609 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 32.1% High Exploitation Risk | Not Applicable |
| CVE-2023-6610 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-3864 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2023-35827 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-46813 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2023-51780 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.69-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-51781 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.69-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-51782 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.69-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52480 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52503 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52517 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52578 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52586 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52847 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-6270 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6531 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-6931 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.69-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2023-6932 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.66-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-26654 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26872 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26939 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26974 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27020 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27397 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-36899 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38561 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39503 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41040 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41049 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41057 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42162 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42228 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43882 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43883 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46858 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-47747 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49855 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49903 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49981 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50036 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50059 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50061 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50086 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50154 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50234 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50275 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50286 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-56664 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56672 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-57876 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21702 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-21718 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37776 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37915 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38051 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38102 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38107 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38108 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39702 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39749 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39759 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39826 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40186 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40248 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68287 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71221 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23191 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23454 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31419 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31663 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43050 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43125 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43198 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43494 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43503 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.174-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45852 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45972 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46054 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46099 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46116 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46181 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46227 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52989 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-52991 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52993 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53000 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53002 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53006 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53091 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-51779 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.69-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-53762 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26852 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-57984 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21703 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-21726 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21727 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21739 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21761 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21764 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21867 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22004 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39993 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40096 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40135 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40154 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40158 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40168 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40259 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40271 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-40318 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40328 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68285 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68301 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23050 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23270 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23392 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31408 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31508 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31586 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43023 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43116 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43158 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43226 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43233 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43303 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43304 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43334 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43339 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43341 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43493 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-45856 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45859 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-45860 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-45894 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45942 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45970 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46015 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46043 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46052 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46090 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46119 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46123 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46133 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-46149 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46173 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46174 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.174-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46185 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46251 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46266 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46275 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46306 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46319 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46324 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46330 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52912 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52917 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52918 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-52920 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-52924 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-52933 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52935 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52942 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52945 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.164-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-52947 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52956 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52957 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-52986 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-52998 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53005 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53009 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53011 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53016 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53036 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53049 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53053 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53062 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53072 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53073 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53075 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53078 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53089 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53131 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53132 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53133 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53182 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53185 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53189 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53209 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53212 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53223 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53224 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53228 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-53230 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53239 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53242 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53246 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53253 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53254 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53256 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53264 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53268 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53270 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53275 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53354 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53355 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53357 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53361 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-1247 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-2961 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-45884 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-45885 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-23054 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46125 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-24023 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2024-24857 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40345 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68346 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53196 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46331 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2020-36694 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-21264 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52447 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52512 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52584 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-0193 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.69-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-26586 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53095 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56678 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56693 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57795 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21714 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21731 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22035 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22097 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40257 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68237 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26828 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-5197 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-0607 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21759 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 7.2% Low-Moderate Risk | Not Applicable |
| CVE-2025-40018 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40261 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45991 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53267 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68284 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-1192 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2023-1193 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-28746 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-6240 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2024-26808 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36968 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47692 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2024-47693 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 1.0% Theoretical Threat | Not Applicable |
| CVE-2024-47726 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-50076 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-53135 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39969 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40273 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68354 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68362 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68380 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31588 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43239 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53176 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-0564 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | ncurses-base 6.4-4 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2022-45888 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-21823 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36016 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-57979 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21700 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21999 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39978 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40074 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40309 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40321 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68371 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23178 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23383 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23450 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-23456 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31502 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31516 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52910 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53033 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53074 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53090 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-44032 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-44033 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-44034 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-3397 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52644 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-24861 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26830 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27030 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38544 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41012 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42161 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57893 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.124-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40307 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68282 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31504 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53059 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-40918 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50251 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-21722 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40048 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40146 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68757 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71066 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23253 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-52497 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52810 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42224 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57874 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40019 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40071 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40080 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40190 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40279 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40355 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68245 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68342 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68343 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68736 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68764 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68815 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68819 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31449 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31464 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31505 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31570 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31700 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31708 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43134 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26843 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56662 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31649 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-52481 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-52511 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2023-52529 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26702 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26894 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-35870 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40083 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40242 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40324 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2018-1121 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 4.2% Low-Moderate Risk | Not Applicable |
| CVE-2021-3714 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2024-53197 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 3.6% Low-Moderate Risk | Not Applicable |
| CVE-2023-53706 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54107 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54141 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35910 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39994 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39998 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40111 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40118 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40167 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40194 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40201 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40214 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40272 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40323 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68742 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23239 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23240 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-23271 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23317 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31392 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31414 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31426 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43279 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46065 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46113 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52923 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-49569 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-53240 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-40319 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46024 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-23039 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-28956 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.140-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-36350 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-36357 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-68801 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68816 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40347 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68192 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68291 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68307 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-38096 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2022-48628 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48772 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49034 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-0160 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-0597 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-23005 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31082 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-37454 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-4133 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-46343 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-50431 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-5090 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-5158 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52429 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52435 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52443 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52448 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52449 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52454 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52456 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52458 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52462 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52463 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52467 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52470 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52476 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52477 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52479 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52484 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52485 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52486 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52488 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52493 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52498 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52499 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52500 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52506 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52513 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52516 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52518 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52520 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52522 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52523 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52526 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52527 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52528 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52532 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52559 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52560 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52562 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52563 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52564 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52566 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52567 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52570 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52573 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52574 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52577 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52580 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52582 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52583 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52587 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52590 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52591 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52593 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52595 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52601 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52606 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52607 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52610 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52615 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52616 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52619 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52622 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52623 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52625 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52629 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52632 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52635 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52638 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52641 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52643 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52648 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52650 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52652 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52655 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.69-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52656 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52658 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52660 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52661 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52662 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52670 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52671 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52672 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52675 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52676 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52677 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52678 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52680 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52683 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52686 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52687 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52690 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52692 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52693 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52694 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52698 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52699 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 1.0% Theoretical Threat | Not Applicable |
| CVE-2023-52750 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52753 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52754 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52761 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52762 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52763 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52767 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52770 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52773 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52774 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.66-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52778 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52780 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52781 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.66-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52784 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52787 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52788 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52789 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52791 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52792 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52797 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52803 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52806 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52808 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52809 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52813 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52814 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52815 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52817 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52821 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52825 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52826 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52828 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52831 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52832 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2023-52833 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52834 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52841 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52843 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52845 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52849 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52850 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52853 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52856 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52857 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52860 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52863 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52865 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52869 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52871 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52873 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52875 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52876 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52877 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52878 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52879 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52880 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52881 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52882 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52887 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52888 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52889 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52918 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52919 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52920 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52923 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52924 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53071 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53149 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53151 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53228 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53231 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53261 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53292 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53336 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53353 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53367 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53394 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53421 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53424 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53429 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53460 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53491 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53523 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53529 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53538 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53545 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53574 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53627 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53846 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53989 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53999 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54013 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54271 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54280 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-6039 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-6622 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.69-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-6915 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-7042 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-0340 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-0641 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-1151 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-2193 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2024-22099 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-23848 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-23849 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-23850 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-23851 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-25739 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-25740 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-25741 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26584 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26590 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26591 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26595 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26596 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26600 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26601 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26602 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26603 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26605 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26606 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26608 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26615 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26618 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26621 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26626 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26629 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26632 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26634 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26635 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26636 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26640 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26641 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26642 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26643 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26644 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26645 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26646 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26651 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26656 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26659 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26660 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26663 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26667 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26668 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26670 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26675 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26677 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26679 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26680 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26681 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26684 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26686 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26687 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26688 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26691 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26695 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26696 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26697 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26700 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26706 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26707 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26714 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26715 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26717 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26718 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26722 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26726 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26727 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26731 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-26733 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26735 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26737 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26740 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26741 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26743 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26744 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26750 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26751 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26752 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26756 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26759 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26760 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26761 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26765 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26766 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26767 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26771 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26772 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26773 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26774 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26775 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26776 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26777 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26778 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26779 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26780 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26781 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26783 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26787 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26788 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26789 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26790 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26795 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26798 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26799 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26801 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26802 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26803 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26804 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 1.0% Theoretical Threat | Not Applicable |
| CVE-2024-26805 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26807 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26809 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26811 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26812 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26813 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26814 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26815 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26816 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26817 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-26820 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26822 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26825 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26826 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26829 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26832 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26833 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26834 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26835 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26838 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26839 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26840 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26841 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26844 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26845 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26849 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26851 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26853 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26855 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26860 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26863 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26864 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-26866 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26868 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26870 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26876 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26877 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26879 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26880 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-26881 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26889 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26891 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26893 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26896 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26900 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26901 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-26902 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26903 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26906 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26916 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26917 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26919 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26920 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26921 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-26922 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26925 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26926 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-26931 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26935 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26937 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26940 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26943 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26946 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26947 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26948 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26953 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26962 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26963 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26964 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26966 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26969 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26970 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26973 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26976 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26977 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26978 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26980 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26984 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26987 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26993 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26994 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26997 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26999 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27001 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27002 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27003 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27004 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27010 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27011 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27012 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27013 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27014 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27015 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27016 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27017 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27023 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27025 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27028 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2024-27032 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27034 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27035 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27037 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27038 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27039 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27041 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27044 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27046 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27047 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27051 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27052 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27053 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2024-27054 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27056 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27057 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27059 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27062 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27072 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27074 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27076 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27077 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27078 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27079 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27388 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27389 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27390 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27391 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27399 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27400 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27402 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27403 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27405 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2024-27407 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27410 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27412 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27413 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27414 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27416 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27417 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27418 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27431 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27432 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27435 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27436 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-27437 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-31076 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-33619 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-33621 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-33847 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-34027 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35247 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35784 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35790 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35794 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35796 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35799 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35800 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35801 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35803 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35804 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35805 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35806 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35807 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-35808 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35811 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35813 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35815 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35817 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35818 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35819 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35821 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-35822 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35823 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2024-35824 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35825 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35826 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35827 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35828 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35829 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35830 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35833 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35835 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2024-35837 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35838 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35839 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35840 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35842 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35844 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35851 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35852 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-35860 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35872 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35875 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35877 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-35879 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35884 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-35885 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35890 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35891 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35892 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35893 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35895 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35897 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35898 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35899 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35900 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35902 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35904 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35907 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35908 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35909 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35912 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35915 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35916 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-35922 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35924 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35925 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35930 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35931 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35933 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35934 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35936 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35938 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35940 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35942 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35943 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35944 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35945 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35946 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35950 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35951 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35952 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35955 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2024-35956 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35958 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35959 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-35960 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2024-35961 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35962 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35969 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-35970 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-35971 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35978 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-35981 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35982 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-35983 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35984 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-35986 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35988 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35989 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35990 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35992 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35995 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35996 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35997 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35998 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35999 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36000 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36004 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36005 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36006 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36007 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36008 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36009 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36014 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36017 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36020 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36021 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36023 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36025 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36026 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36029 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36244 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36270 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-36286 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-36288 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-36476 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.124-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36478 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-36479 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36484 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-36489 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-36882 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36889 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-36890 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36891 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36893 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36897 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36900 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36901 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-36902 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-36903 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36905 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-36908 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36909 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36911 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36917 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36918 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36919 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36920 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36922 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36924 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36926 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36929 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-36930 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36933 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-36937 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36938 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36939 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36941 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36945 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36946 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-36947 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-36951 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36953 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36954 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36957 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36959 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36962 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36964 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36965 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36967 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36969 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36972 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-36975 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36977 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-37021 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-37356 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38390 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38543 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38546 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38547 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38549 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38553 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38554 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38557 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38558 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38564 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38565 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-38567 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38571 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38575 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38579 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38582 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2024-38587 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2024-38589 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38590 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38591 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38594 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38597 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38598 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38600 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38602 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38603 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38607 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38608 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38611 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38612 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2024-38615 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38618 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-38619 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38620 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38622 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38623 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-38624 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38625 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38632 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38633 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38634 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38636 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38637 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38661 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38780 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39282 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.124-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39292 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39298 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39301 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39371 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39466 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39468 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39472 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39474 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39475 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39476 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39481 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39482 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39484 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39488 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39489 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39490 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39493 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39497 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-39505 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-39506 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-39507 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-39509 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40904 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40908 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40910 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40911 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40912 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-40914 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40915 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-40916 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40919 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40921 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40924 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40931 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40932 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40934 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40937 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40938 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-40941 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40942 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40945 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40947 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40948 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-40957 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-40959 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40960 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40961 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40963 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40965 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-40966 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40967 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-40968 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40969 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-40970 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40971 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40972 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-40973 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40975 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40976 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-40977 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-40980 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-40981 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-40983 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40984 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40987 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40988 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40990 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40993 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40995 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40998 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40999 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41001 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41002 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41004 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41006 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41008 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41009 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.98-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41015 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41016 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41017 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41019 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41022 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41023 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41030 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41031 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41034 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41035 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41036 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41038 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41041 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41044 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41047 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41048 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41055 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41056 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41060 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41062 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41063 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41064 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41065 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41066 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41068 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41072 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41075 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41076 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41077 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41078 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41079 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41080 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41081 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41082 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41088 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41089 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41093 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41095 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41097 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41098 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42063 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42068 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42069 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42070 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.98-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42073 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42076 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42077 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42079 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42080 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42082 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42084 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42085 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42087 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42089 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42090 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42095 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42096 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42097 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42098 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42101 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.98-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42103 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42106 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.98-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42109 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42110 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42115 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.98-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42122 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42124 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.98-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42126 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42127 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42128 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42129 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42137 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42139 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42140 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42142 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42145 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42153 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42223 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42232 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42236 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42237 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42238 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42239 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42240 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42241 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42243 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42244 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42245 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42246 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42247 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42250 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42252 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42258 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42259 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42265 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42267 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42268 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42269 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42270 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42272 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42273 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42274 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42276 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42277 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42279 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42281 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42283 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42286 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42288 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42289 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42290 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42291 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42295 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42296 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42297 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42299 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42304 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42305 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42306 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42307 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42309 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42310 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42311 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42312 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42315 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42316 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42317 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42318 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42319 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42320 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42321 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42322 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43098 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43817 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43818 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43819 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43823 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43824 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43828 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43829 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43831 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43832 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43833 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43834 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43835 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-43837 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43840 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43846 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43849 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43850 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43851 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43853 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43854 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43855 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43856 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-43859 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43860 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43861 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43863 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43867 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43868 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43869 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43870 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43871 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43872 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-43875 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43876 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43879 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43880 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43884 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-43889 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43890 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-43893 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-43894 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43897 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-3 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43899 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43901 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43902 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43904 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43905 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43907 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43908 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43909 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43912 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43913 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43914 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44931 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44935 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44938 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44939 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44944 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44946 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-44947 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2024-44948 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44950 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44958 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44960 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44963 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44965 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44966 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44968 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44969 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44970 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44971 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44982 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44988 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44989 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44990 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44991 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44995 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-45000 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-45001 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-45002 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-45006 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-45007 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-45008 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-45009 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-45010 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-45011 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-45015 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-45016 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-45018 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-45019 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-45021 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-45022 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-45025 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-45028 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-45029 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-45828 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46675 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46676 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46677 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46678 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46681 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46685 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46686 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46689 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46694 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46698 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46702 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46707 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46714 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46715 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46716 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46717 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46719 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46720 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46721 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46726 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46727 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46728 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46730 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46732 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46733 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46735 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46737 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46739 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46742 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46745 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46750 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46751 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46752 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46753 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46754 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46755 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46760 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46761 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46763 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46765 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46770 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46771 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46772 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46773 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46775 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46776 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46777 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46780 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46781 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46783 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46784 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46791 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46795 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46802 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46805 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46806 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46807 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46808 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46809 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46810 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46816 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46817 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46819 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46822 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46826 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46829 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46832 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46834 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46835 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46840 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46841 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46846 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46848 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46855 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46857 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46860 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46896 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47141 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47143 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47408 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47658 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47661 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47662 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47663 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47664 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47665 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47666 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47667 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47669 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47671 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47673 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47674 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47678 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47683 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47684 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-47690 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47699 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-47703 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47704 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47705 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47706 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47707 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47709 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47710 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47712 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47713 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-47720 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47728 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47731 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47734 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47735 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47736 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47737 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-47739 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47740 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47743 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47749 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47752 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47753 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47754 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47756 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47794 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47809 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-48881 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49568 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49571 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49850 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49851 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49856 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49858 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49863 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49867 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49868 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49870 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49871 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49875 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49877 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49878 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49879 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49881 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49886 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49890 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49891 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49892 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49893 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49896 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49897 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49898 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49899 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49901 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49902 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49905 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49906 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49907 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49908 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49909 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49910 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49911 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49912 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49913 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49914 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49915 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49916 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49917 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49918 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49919 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49920 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49921 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49922 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49923 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49925 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49926 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49927 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49929 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49933 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49935 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49937 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49938 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49939 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49940 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49944 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49945 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49946 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49948 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49949 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49951 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49952 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49954 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49955 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49957 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49958 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49959 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49961 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49962 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49963 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49965 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49968 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49970 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49973 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49974 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49975 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49977 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49978 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49985 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49988 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49994 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50000 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50001 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50002 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50003 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50008 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50009 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50012 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50013 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50015 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50017 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50019 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50022 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50024 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50026 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50028 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50031 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50038 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50039 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50040 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50041 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50045 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50046 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50048 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50049 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50056 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50058 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50060 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50062 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50069 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50072 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50077 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50078 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50085 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50087 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50093 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50095 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50096 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50098 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50099 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50101 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50103 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50108 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50110 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50111 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50116 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50117 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50133 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50134 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50136 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50138 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50141 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50142 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50145 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50146 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50147 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50148 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50153 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50156 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50160 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50162 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50163 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50166 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50167 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50168 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50171 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50176 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50179 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50182 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50184 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50185 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50187 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50188 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50189 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50194 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50195 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50196 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50198 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50199 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50200 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50201 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50202 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50205 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50208 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50210 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50218 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50229 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50232 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50233 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50236 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50237 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50243 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50244 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50245 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50248 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50249 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50252 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50255 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50256 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50258 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50259 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50265 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50271 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50272 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50273 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50284 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50285 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50287 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50289 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50290 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50292 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50295 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50296 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50298 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50299 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50302 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-50304 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-52559 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-52560 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53042 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53043 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53051 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53055 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53056 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53058 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53060 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53063 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53066 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53070 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53072 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53079 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53081 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53085 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53089 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53090 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53091 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53093 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53094 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53097 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53101 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53105 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53110 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53112 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53113 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53114 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53119 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53120 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53121 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53122 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53123 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53125 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53127 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53128 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53129 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53130 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53131 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53134 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53138 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53140 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53144 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53145 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53146 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53148 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53151 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53154 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53157 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53158 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53161 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53164 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53172 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53175 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53180 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53181 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53183 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53184 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53187 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53190 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53194 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53195 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53196 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53198 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53207 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53209 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53210 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53215 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53217 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53219 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53220 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53221 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53224 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53226 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53229 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53230 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53231 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53233 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53234 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53241 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53680 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53685 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53687 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53690 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-54031 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.124-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-54683 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-55881 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-55916 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56369 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56531 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56532 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56533 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56539 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-56544 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56546 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56549 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56557 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56562 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56565 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56566 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56567 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56569 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56572 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56574 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56575 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56578 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56579 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56583 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56584 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56585 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56586 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56587 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56588 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56589 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56590 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56591 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56592 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56593 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56594 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56599 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56610 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56611 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56622 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56623 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56625 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56629 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56630 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-56634 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-56636 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-56641 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56643 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56644 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56645 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56647 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-3 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56648 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56657 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56659 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56660 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56661 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56665 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56670 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56677 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-56679 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56681 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56683 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56687 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56688 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56690 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56691 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56692 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56694 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56698 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56700 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56701 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56703 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56705 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-56707 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56709 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56712 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56715 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56716 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56717 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56718 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56719 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56720 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56722 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56723 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56724 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56725 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56726 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56727 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56728 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56739 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56742 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56745 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56746 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56747 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56748 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56751 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56754 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56755 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56756 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56758 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56763 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56767 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56769 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56770 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-56774 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56776 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56777 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56778 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56779 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56780 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56783 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56785 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56787 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57802 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.124-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57804 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57807 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57809 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57834 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57841 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.124-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57872 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57882 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.124-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57883 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57884 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.124-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57888 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57889 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.124-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57890 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.124-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57895 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57897 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.124-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57901 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.124-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-57902 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.124-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-57903 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.124-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57916 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57922 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.128-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-57924 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57930 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.124-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57931 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.124-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57938 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.124-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57939 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57940 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57946 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57947 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57948 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57949 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57973 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57975 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57976 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57977 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57978 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57981 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57986 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57993 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57996 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57997 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57999 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58001 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58005 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58006 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58009 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58010 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58011 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58012 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58016 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58017 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58020 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58051 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58052 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58053 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58056 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58058 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58061 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58063 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58068 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58071 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-58076 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58079 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58080 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58083 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58085 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58086 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58089 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58090 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58094 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58095 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-58096 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58097 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58098 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58100 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58237 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58239 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58241 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21629 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.124-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21634 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21635 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21636 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21637 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21638 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21639 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21640 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21645 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21646 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21648 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21649 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21653 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21656 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21658 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21660 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21662 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21664 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21665 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21666 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21667 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21668 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21669 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21673 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21675 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21676 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21678 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21681 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21682 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21683 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21684 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21689 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21690 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21693 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21694 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21696 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21697 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21699 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21705 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21706 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21707 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21708 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21711 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21712 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21716 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21721 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21723 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21725 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21728 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21729 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21736 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21738 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21744 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21745 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21748 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21749 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21750 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21758 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 13.0% High Exploitation Risk | Not Applicable |
| CVE-2025-21760 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 9.1% Low-Moderate Risk | Not Applicable |
| CVE-2025-21763 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21765 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21766 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21767 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21768 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21775 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21776 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21779 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21781 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21787 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21790 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21792 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21795 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21796 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21799 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21801 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21802 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21804 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21806 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21814 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21816 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21819 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21820 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21821 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21823 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21826 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21829 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21830 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21831 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21832 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21835 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21836 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21838 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21839 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21844 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21846 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21848 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21853 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21859 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21861 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21862 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21864 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21865 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21866 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21870 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21871 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21872 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21875 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21877 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21878 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21881 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21885 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21888 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21891 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21894 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21898 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21899 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21904 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21907 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21909 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21910 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21912 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21913 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21916 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21917 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21918 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21922 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21924 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21925 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21926 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21931 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.140-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21935 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21936 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21937 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21941 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21944 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21948 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21949 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21951 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21955 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21956 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21957 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21959 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21960 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21961 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21962 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21963 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21964 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21970 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21971 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21972 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21975 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21976 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21978 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21980 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21981 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21986 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21992 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21994 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21996 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21997 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22005 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22007 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22008 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22010 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22014 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22015 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22018 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22021 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22025 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22026 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22028 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22033 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22037 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 28.2% High Exploitation Risk | Not Applicable |
| CVE-2025-22042 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22043 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22044 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22045 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22048 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22049 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22053 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-22054 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22055 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22057 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22058 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22062 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22063 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22066 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22070 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22071 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22072 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22073 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22075 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22081 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22086 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22089 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22090 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22093 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22095 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22103 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22105 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22109 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-22111 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22113 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22119 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22125 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22127 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-23129 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23130 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23131 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23132 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-23136 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23138 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23140 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23141 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23143 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23144 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.137-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23145 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23146 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23147 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23148 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23150 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23155 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23159 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23160 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23161 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-23163 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37740 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37741 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37742 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37747 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37748 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37756 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37757 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37758 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37765 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37766 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37767 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37768 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37769 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37770 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37771 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37772 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37773 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37775 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37781 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37787 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37788 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37790 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37792 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37794 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37800 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37801 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.137-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37802 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37805 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.137-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37806 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37807 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37808 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.137-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37811 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.137-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37812 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.137-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37815 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.137-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37818 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.137-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37820 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.137-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37824 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.137-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37829 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.137-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37830 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.137-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37833 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37834 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37836 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.137-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37841 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37842 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37844 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37850 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37851 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37852 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37853 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37856 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37857 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37858 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37859 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37860 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37862 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37864 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37865 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37867 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37871 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37875 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37880 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37881 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.137-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37883 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.137-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37889 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37893 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37897 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37901 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37905 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37909 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37911 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37912 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37917 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37925 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.148-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37929 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37930 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37931 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37932 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37936 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37937 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37938 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.137-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37940 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37945 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37948 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37949 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37951 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.140-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37953 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37956 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37958 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37959 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.140-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37961 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.140-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37962 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.140-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37963 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37964 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.140-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37967 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.140-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37968 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37969 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.140-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37970 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.140-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37972 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.140-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37977 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37980 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37982 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37983 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.137-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37989 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.137-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37990 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37992 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37994 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.139-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37995 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.139-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37997 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.139-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37998 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.139-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38001 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-38003 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38005 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38006 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38007 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38009 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38014 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38015 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38018 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38020 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38023 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38029 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38031 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38034 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38035 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38037 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38038 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38039 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38040 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38041 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38042 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38043 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38044 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38045 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38057 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38058 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38059 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38061 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38062 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38063 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38064 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38065 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38066 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38067 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-38071 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38072 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38074 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38075 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38080 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38084 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38086 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38090 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38094 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.140-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38095 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38096 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38097 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38100 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38105 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38113 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38115 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38119 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38120 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38122 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38124 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38125 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38126 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38127 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38132 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38135 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38136 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38138 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38140 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38142 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38143 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38145 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38147 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38148 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38151 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38152 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38158 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38160 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38161 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38162 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38163 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38165 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38166 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38167 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38170 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38173 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38174 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38177 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.139-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38181 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38184 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38185 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38190 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38191 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-38192 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38193 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38194 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38195 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38197 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38200 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38202 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38203 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38207 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38214 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38215 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38218 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38219 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38222 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38225 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38229 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38231 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38237 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38244 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38246 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38251 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38260 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38261 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38262 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38263 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38264 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38272 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38273 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38275 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38277 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38282 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38283 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38285 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38293 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38300 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38303 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38304 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38305 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38310 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38311 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38312 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38319 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38322 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38324 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38326 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38328 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38331 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38332 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38333 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38334 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38335 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.148-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38336 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38337 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38344 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38345 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38347 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38354 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38359 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38362 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38363 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38364 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38371 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38382 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38384 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38386 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38387 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38391 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38399 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38400 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38404 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38406 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38408 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38409 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38410 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38412 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38418 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38419 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38420 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38424 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38426 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38429 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38430 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38436 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38438 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38439 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38441 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38444 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38449 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38451 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38455 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38457 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38458 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38460 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38465 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38466 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38467 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38468 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38470 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38472 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38473 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38474 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38478 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38480 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38481 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38487 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38491 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38495 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38498 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38499 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38503 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38507 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38510 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38513 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38514 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38516 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38520 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.148-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38528 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38531 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38539 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38540 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38542 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38543 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38544 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38546 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38560 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.148-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38562 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.148-1 | 7.1% Low-Moderate Risk | Not Applicable |
| CVE-2025-38569 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.148-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38575 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38576 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.148-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38577 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.148-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38578 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.148-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38581 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.148-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38583 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.148-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38587 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.148-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38588 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.148-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38590 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38591 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38597 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38601 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.148-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38602 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.148-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38604 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.148-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38608 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.148-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38609 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.148-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38610 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.148-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38612 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.148-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38614 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38615 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38622 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.148-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38623 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.148-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38624 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.148-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38626 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38630 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.148-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38634 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.148-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38635 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.148-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38637 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-38639 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.148-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38643 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38644 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.148-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38645 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.148-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38650 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.148-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38659 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38663 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.148-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38664 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.148-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38665 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.148-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38668 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.148-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38671 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.148-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38678 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38683 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38684 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38691 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38692 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38693 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38694 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38695 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38696 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38698 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38700 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38701 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38705 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38706 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38709 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38710 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38711 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38712 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38716 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38721 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38723 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38725 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38727 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38732 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38735 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39675 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39676 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39677 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39681 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39684 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39692 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39693 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39694 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39703 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39705 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39706 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39707 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39709 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39714 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39715 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39716 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39718 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39720 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39721 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39724 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39728 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39731 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.148-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39732 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39734 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.148-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39736 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39737 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39742 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39746 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39747 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39748 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39752 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39756 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39762 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39763 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39764 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39767 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39770 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39772 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39773 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39779 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39782 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39787 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39789 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39794 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39795 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39798 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39800 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39801 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39805 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39808 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39812 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39819 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39827 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39829 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39833 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39838 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39842 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39843 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39844 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39845 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39846 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39847 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39848 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39850 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39851 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39857 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39865 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39876 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39885 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39886 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39889 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39894 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39902 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39907 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39909 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39910 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39914 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39916 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39920 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39923 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39925 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39929 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39931 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39932 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39933 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39934 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39937 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39938 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39940 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39942 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39946 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 8.9% Low-Moderate Risk | Not Applicable |
| CVE-2025-39947 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39949 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39953 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39989 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40005 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40020 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40026 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40027 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40029 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40030 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40040 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40044 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40051 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40053 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40070 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40075 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40078 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40102 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40104 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40109 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40115 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40140 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40153 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40160 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40164 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40171 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40211 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40231 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40251 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40264 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40280 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40283 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40284 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40292 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40293 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40297 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40300 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40325 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40339 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40363 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68176 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68185 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68188 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68209 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68211 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68223 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68229 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68231 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68236 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68259 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68261 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68265 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68283 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68304 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68310 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68331 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68337 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68340 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68358 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68365 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68372 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68379 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68725 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68774 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68776 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68803 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68814 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68821 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68823 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71064 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71077 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71079 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71081 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71083 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71084 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71085 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71087 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71088 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71094 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71095 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71096 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71097 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71098 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71102 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71104 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71105 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71108 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71109 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71113 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71114 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71118 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71119 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71120 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71121 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71125 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71126 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71127 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71129 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71130 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71131 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71132 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71138 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71144 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71147 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71150 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71154 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71160 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71161 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71163 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71180 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71182 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71183 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71184 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71185 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71186 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71188 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71189 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71190 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71191 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71200 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71202 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71222 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71227 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71232 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71233 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71235 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71236 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71237 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71265 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71266 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71267 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71268 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71269 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71272 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71273 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71285 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71287 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71288 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71289 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71291 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71292 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71295 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71297 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71304 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71305 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71313 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71315 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22976 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22977 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22979 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22982 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22990 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-22991 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-22992 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-22994 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22996 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-22997 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-22999 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23000 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23003 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-23005 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23006 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23011 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23019 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23020 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23021 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23026 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23031 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23038 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23047 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23058 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23060 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23061 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23063 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23064 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23066 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23069 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23075 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23080 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23084 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23085 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23086 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23087 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23088 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23090 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23091 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23093 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23095 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23096 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23097 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23100 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23103 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23105 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23107 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23108 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23113 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23116 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23119 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23120 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23121 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23124 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23125 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23128 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23133 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23137 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23138 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23139 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-23140 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23141 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23142 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23144 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23145 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23146 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23150 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23154 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23157 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23164 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23168 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23170 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23172 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23190 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23198 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23202 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23205 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23206 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23213 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23214 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23220 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23222 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23228 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23229 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23230 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23236 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23237 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23238 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23242 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-23247 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23255 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23256 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23257 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23258 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23264 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23265 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23266 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23267 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23272 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23273 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23274 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23276 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23277 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23278 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23279 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23284 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23286 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23287 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23289 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23290 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23291 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23292 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23293 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23296 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23298 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23300 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23303 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23304 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23306 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23307 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23310 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23312 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23321 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23324 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23330 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23335 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23336 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23339 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23340 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23346 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23351 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23352 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23356 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23357 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23362 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23365 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23367 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23368 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23370 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23371 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23374 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23379 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23381 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23382 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23389 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23391 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23396 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23398 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23399 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23401 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23403 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23404 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23405 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23409 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23414 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23419 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23420 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23426 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23434 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23438 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23439 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23442 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23444 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23446 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23449 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23460 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23462 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-23465 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23468 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23472 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23474 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23475 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31391 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31400 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31403 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31407 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31410 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31411 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31412 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31415 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31416 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31418 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31420 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31421 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31422 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31423 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31424 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31425 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31427 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31428 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31434 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31441 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31446 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31447 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31448 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31450 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31451 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31453 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31454 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31458 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31462 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31467 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31469 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31473 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31480 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31483 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31487 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31492 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31495 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31496 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31497 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31498 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31503 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31507 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31509 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31510 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31512 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31515 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31518 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31519 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31520 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31521 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31522 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31524 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31531 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31533 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31537 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31540 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31545 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31546 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31548 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31549 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31550 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31551 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31552 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31555 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31557 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31560 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31565 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31577 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31579 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31585 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31590 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31592 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31594 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31595 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31596 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31599 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31603 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31605 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31606 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31610 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31615 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31616 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31617 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31618 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31619 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31623 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31624 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31625 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31628 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31630 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31634 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31637 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31642 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31648 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31651 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31655 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31658 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31660 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31661 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31662 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31664 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31665 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31667 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31670 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31671 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31672 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31673 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31674 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31675 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31676 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31677 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31678 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31679 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31680 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31681 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31682 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31684 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31687 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31689 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31692 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31698 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31699 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31701 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31704 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31721 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31722 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31723 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31724 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31725 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31726 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31737 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31738 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31749 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31752 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31754 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31755 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31756 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31758 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31762 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31763 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31767 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31770 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31771 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31773 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31777 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31779 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31781 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43009 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43010 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43013 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43014 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43016 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43017 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43018 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43022 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43024 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43025 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43026 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43028 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43032 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43033 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43035 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43036 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43041 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43042 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43043 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43046 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43048 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43054 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43057 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43058 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43060 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43061 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43062 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43064 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43065 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43066 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43068 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43069 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43071 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43072 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43073 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43077 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43079 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43080 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43083 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43085 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43088 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43089 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43091 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43093 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43094 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43098 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43099 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43101 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43103 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43104 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43105 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43107 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43111 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43113 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43115 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43118 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43119 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43123 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43124 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43129 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43130 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43132 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43135 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43136 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43137 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43139 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43140 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43143 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43145 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43147 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43148 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43149 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43152 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43153 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43156 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43157 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43159 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43161 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43162 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43167 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43168 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43170 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43171 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43172 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43173 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43180 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43182 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43183 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43187 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43200 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43202 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43204 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43209 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43213 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43214 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43215 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43216 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43218 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43219 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43221 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43223 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43225 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43227 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43230 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43231 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43234 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43238 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43240 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43242 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43244 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43246 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43251 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43252 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43255 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43257 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43261 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43262 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43264 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43265 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43266 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43268 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43269 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43270 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43271 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43273 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43277 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43278 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43287 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43288 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43289 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43295 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43296 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43299 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43302 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43308 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43309 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43310 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43312 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43313 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43314 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43315 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43316 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43317 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43318 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43327 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43333 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43338 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43340 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43343 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43344 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43350 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43352 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43353 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43355 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43357 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43359 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43360 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43361 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43362 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43363 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43365 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43366 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43381 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43382 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43387 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43405 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43406 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43407 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43409 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43411 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43412 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43413 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43416 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43419 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43421 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43424 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43425 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43428 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43429 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43432 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43436 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43437 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43441 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43443 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43445 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43451 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43452 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43455 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43456 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43457 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43459 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43466 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43468 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43469 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43472 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43473 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43475 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43480 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43483 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43484 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43491 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43492 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43496 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43502 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45834 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45835 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45836 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45838 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45840 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45841 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45842 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45843 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-45844 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45846 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45847 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45848 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45849 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45850 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45855 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45857 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45858 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45862 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45864 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45865 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45868 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45869 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45870 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45871 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45872 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45873 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45875 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45877 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45881 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45883 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45886 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45890 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45892 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45897 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45899 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45901 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45904 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45911 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45912 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45915 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45917 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45919 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45923 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45924 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45930 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45934 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45940 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45941 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45944 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45948 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45954 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45960 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45961 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45962 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45963 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45964 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45965 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45968 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45969 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45974 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45978 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45981 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45982 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45983 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45985 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45986 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45987 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45988 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-45993 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45997 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45999 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46000 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46002 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46003 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46005 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46009 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46012 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46014 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46018 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46019 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46021 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46023 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46026 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46027 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46028 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46032 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46037 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46038 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46040 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46044 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46046 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46049 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46050 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46051 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46059 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46070 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46071 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46072 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46077 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46078 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46079 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46080 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46082 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46083 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46086 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46088 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46091 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46092 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46098 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46101 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46102 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46103 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46107 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46108 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46109 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46111 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46127 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46128 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46132 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46137 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46143 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46146 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46147 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46148 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46151 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46153 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46156 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46157 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46158 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46160 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46161 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46165 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46167 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46168 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46169 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46170 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46172 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46179 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46184 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46186 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46190 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46193 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46196 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46200 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46214 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46220 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46225 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46226 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46229 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46231 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46233 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46235 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46236 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46245 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46247 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46249 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46252 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46253 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46254 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46262 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46273 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46276 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46280 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46282 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46291 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46292 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46296 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46302 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46303 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46304 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46307 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46312 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46314 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46320 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46321 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46322 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52909 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52913 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52915 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52916 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52921 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52925 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52926 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52927 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52928 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52929 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52930 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52936 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52937 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52939 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52941 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52944 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52946 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-52948 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52954 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-52958 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-52961 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52963 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52967 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52970 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52972 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52975 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52977 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52981 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-52982 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-52984 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52985 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52988 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52990 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52995 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52999 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53001 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53003 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53012 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53015 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53017 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53018 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53021 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53022 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53023 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53027 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53034 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53035 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53037 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53039 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53047 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53050 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53052 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53061 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53069 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53070 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53076 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53077 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53086 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53096 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53108 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53115 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53117 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53118 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53120 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53122 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53128 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53134 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53135 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53139 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53146 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53147 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53150 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53158 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53159 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53163 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53167 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53168 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53177 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53181 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53183 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53184 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53199 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53207 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53208 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53213 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53218 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53219 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53220 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53221 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-53225 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53226 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53227 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53229 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53232 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53236 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53237 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53238 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53245 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53249 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53252 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53258 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53263 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53265 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53269 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53274 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53279 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53285 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53287 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53289 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53291 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53292 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53295 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53297 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53304 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53306 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53313 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53314 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53317 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53320 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53325 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53349 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53358 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2008-2544 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2011-4915 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2011-4916 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2011-4917 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2014-9892 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2014-9900 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2016-10723 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2016-8660 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2017-13693 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2017-13694 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-12928 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-12378 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-12379 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-12380 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-12381 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-12382 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-12455 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-47432 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-4543 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2022-48669 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31081 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-31085 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-4134 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52576 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52631 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52653 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52674 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52696 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-52811 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52819 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53728 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53823 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53857 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54030 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-54069 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54088 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54324 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26627 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26633 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26676 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26685 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26924 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2024-26927 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26950 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26960 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27073 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27393 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-35843 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35853 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-35854 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2024-35865 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35888 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-35947 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-35973 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-35976 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-36896 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2024-36955 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38573 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2024-38576 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-39276 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-54458 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39990 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39997 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40010 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40042 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40049 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40057 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40088 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40092 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40094 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40099 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40100 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40103 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40105 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40125 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40196 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40205 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40219 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40253 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40346 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40360 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68171 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68173 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68194 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68200 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68204 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68206 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68218 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68219 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68227 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68233 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68244 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68288 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68295 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68308 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68321 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68334 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68336 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68345 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68363 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68378 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68732 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68734 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68753 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68758 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68778 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68780 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68783 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68785 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68794 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68795 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68798 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68813 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68818 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68820 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68822 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71194 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31486 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43030 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43194 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43211 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43253 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46178 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46299 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52974 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53048 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53060 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53063 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53064 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53080 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53083 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53088 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53093 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53102 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53106 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53111 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53284 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53327 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53337 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53339 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53350 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53352 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53353 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-24858 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-24860 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-26886 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-35857 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2024-36881 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39968 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39972 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40204 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68367 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71225 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23457 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53194 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39970 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40338 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40343 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40178 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71193 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23035 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52633 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40121 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23180 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2004-0230 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 80.9% Actively Exploited | Not Applicable |
| CVE-2010-4563 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 3.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-34324 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2005-3660 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-24859 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2019-20794 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-31083 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-46862 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52478 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52489 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52505 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52568 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52589 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52602 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52608 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52609 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52639 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52645 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52654 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.69-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2023-52749 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.66-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52771 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53447 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2024-2201 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 8.6% Low-Moderate Risk | Not Applicable |
| CVE-2024-24855 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-24864 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26583 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26585 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26607 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26631 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26671 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26698 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26837 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26859 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26861 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26862 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26869 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26874 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26878 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26897 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26910 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26923 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27009 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27019 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27404 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27408 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27415 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27419 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35809 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35848 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36024 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36028 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36927 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36949 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36952 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-37354 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38580 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38596 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38601 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38613 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38662 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39500 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39508 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-40905 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40943 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-40953 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41005 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41020 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42102 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.98-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42107 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42152 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42253 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42287 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43866 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43892 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44954 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-45003 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46679 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46710 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46711 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46734 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46787 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46870 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-47660 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47668 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47679 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49859 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49866 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49998 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50006 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50010 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50082 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50135 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50183 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50192 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53088 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53100 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53124 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53136 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53176 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53178 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56568 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56576 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56637 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56729 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57857 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57913 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57974 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21651 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21655 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21688 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21701 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21732 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21825 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21892 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21938 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21943 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21947 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.133-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-22027 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-22050 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22060 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-22115 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-23151 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37920 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37985 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.137-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38048 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38078 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38083 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38085 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38104 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38112 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38232 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38234 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38365 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38393 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38448 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38461 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38462 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38477 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38515 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38524 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38561 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.148-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-38617 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.148-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-38681 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38687 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38717 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39673 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39697 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39713 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39726 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39754 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39813 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39825 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39927 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39961 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39977 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39980 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39996 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40006 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40011 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40016 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40039 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40056 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40085 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40110 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40120 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40134 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40139 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40179 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40187 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40197 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40215 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40220 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40244 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40252 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40254 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40331 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40342 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68214 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68239 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68241 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68296 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68312 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68745 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71074 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71111 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71274 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23004 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23071 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23101 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23110 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23118 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23126 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23167 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23169 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23207 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23212 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23302 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23348 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23394 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23452 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23463 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31389 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31393 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31466 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31523 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31697 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31728 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31751 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43047 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43053 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43163 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43275 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43342 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43383 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43420 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43430 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43439 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43448 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45905 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45949 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46017 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46159 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46187 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52955 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2017-0630 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2019-16230 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-16234 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-26915 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68264 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2019-15213 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-4010 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-49934 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2012-4542 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40308 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40312 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-45896 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2020-14304 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-52508 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52585 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52617 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52627 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54263 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26810 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35845 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2024-36950 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38540 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38541 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.137-1 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2024-42114 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42123 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42131 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42154 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.98-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42230 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46695 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53052 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40001 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40081 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40206 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40281 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68768 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2018-17977 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-52492 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52618 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2023-52765 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52768 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52798 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-52800 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52838 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52844 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52855 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52858 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52861 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52870 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52884 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54247 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26638 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26661 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26662 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26672 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26712 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26723 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26745 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26747 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26757 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26758 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26768 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26769 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26846 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26857 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26875 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36031 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-36894 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-36910 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36912 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2024-36913 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2024-36944 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38388 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38548 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38550 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38559 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38605 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2024-38616 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-38628 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40021 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40123 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40183 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40198 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40200 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23458 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-47233 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-6121 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2010-5321 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40275 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-41848 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2019-16089 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-52872 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36928 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42156 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42157 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42158 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42229 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40173 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2019-16229 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-16231 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-16232 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2019-16233 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-52597 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2020-35501 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68740 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68191 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2015-2877 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-52561 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52571 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52926 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54145 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54227 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54233 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54322 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26612 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26614 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26764 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26992 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35935 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41007 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41027 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-43841 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46794 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47738 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50044 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50057 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50211 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50280 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-39964 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40035 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40268 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40303 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40341 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68746 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68782 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71224 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-22978 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31668 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | ncurses-base 6.4-4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2019-11191 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-52620 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68788 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2007-3719 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42155 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| TEMP-0841856-B18BAF | NONE0 | bash 5.2.15-2+b2 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | bsdutils 1:2.38.1-5+b1 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | bsdutils 1:2.38.1-5+b1 No fix yet | — | Not Applicable |
| CVE-2026-2219 | NONE0 | dpkg 1.21.22 fixed in 1.21.23 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-6297 | NONE0 | dpkg 1.21.22 fixed in 1.21.23 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | libblkid1 2.38.1-5+b1 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libblkid1 2.38.1-5+b1 No fix yet | — | Not Applicable |
| CVE-2025-0167 | NONE0 | libcurl4 7.88.1-10+deb12u4 fixed in 7.88.1-10+deb12u11 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-8458 | NONE0 | libcurl4 7.88.1-10+deb12u4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-56131 | NONE0 | libexpat1 2.5.0-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56407 | NONE0 | libexpat1 2.5.0-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56408 | NONE0 | libexpat1 2.5.0-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56409 | NONE0 | libexpat1 2.5.0-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | libmount1 2.38.1-5+b1 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libmount1 2.38.1-5+b1 No fix yet | — | Not Applicable |
| CVE-2026-58055 | NONE0 | libnghttp2-14 1.52.0-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | libsmartcols1 2.38.1-5+b1 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libsmartcols1 2.38.1-5+b1 No fix yet | — | Not Applicable |
| CVE-2025-27587 | NONE0 | libssl3 3.0.11-1~deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | libuuid1 2.38.1-5+b1 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libuuid1 2.38.1-5+b1 No fix yet | — | Not Applicable |
| DSA-5990-1 | NONE0 | libxml2 2.9.14+dfsg-1.3~deb12u1 fixed in 2.9.14+dfsg-1.3~deb12u4 | — | Not Applicable |
| CVE-2026-43011 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43185 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-53215 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-23268 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23372 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31405 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31432 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31433 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-31476 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31478 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31536 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31627 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31656 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31657 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31659 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31695 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31705 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31706 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31712 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31716 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31780 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43075 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43076 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43206 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43236 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43370 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43490 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52911 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52914 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53040 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53043 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53046 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53068 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53130 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53186 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53198 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-53732 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53801 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54125 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54196 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54272 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36331 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.148-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-27558 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37838 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39985 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39986 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39987 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39988 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39995 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40003 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40008 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40013 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40022 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40025 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40032 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40036 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40043 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40054 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40055 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40060 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40062 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40065 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40068 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40077 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40084 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40087 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40093 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40095 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40097 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40106 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40107 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40112 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40116 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40124 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40126 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40127 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40136 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40137 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40156 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40180 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40188 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40193 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40202 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40207 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40223 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40233 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40243 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40245 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40247 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40262 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40263 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40266 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40278 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40282 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40285 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40286 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40288 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40289 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40306 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40311 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40313 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40314 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40315 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40317 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40333 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40337 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40354 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40358 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68177 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68190 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68201 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68217 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68220 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68238 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68246 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68249 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68254 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68255 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68256 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68257 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68258 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68263 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-68266 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68286 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68289 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68290 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68302 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68303 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68315 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68320 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68322 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68325 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68327 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68328 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68330 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68332 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68335 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68339 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68344 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68364 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68369 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68727 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68728 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68733 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68750 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68755 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68759 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68765 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68766 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68767 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68769 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68771 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68772 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68773 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68777 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68781 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68786 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68787 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68796 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68797 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68799 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68804 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68806 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68808 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68809 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71065 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71067 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71069 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71192 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71196 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71197 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71198 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71199 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23030 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23033 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23037 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23049 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23056 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23176 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23182 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23245 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23269 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23364 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-23393 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23406 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23407 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31396 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31409 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31417 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31477 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31494 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31563 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31597 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31598 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31602 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31611 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31612 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31622 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31626 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31629 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31683 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31707 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31711 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31768 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43117 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43184 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43203 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43212 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43258 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43336 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43373 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43377 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43476 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43495 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-45935 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45956 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45958 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46006 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46031 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46058 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46062 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46110 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46112 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46124 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46129 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46164 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46175 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46177 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46197 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46198 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46199 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46204 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46205 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46206 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46208 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46212 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46218 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46230 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46238 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46328 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52919 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52922 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52931 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52934 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53024 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53025 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53041 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53045 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53056 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53066 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53107 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53178 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53329 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53330 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53331 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53332 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53343 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53345 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53356 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31587 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31761 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43207 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43232 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43249 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43256 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43283 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43291 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43324 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43497 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46250 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46265 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46270 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53065 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53082 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53112 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53160 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53161 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53216 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53217 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53273 | NONE0 | linux-libc-dev 6.1.55-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| TEMP-0000000-F7A20F | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | — | Not Applicable |
| CVE-2023-53851 | NONE0 | linux-libc-dev 6.1.55-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | login 1:4.13+dfsg1-1+b1 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | mount 2.38.1-5+b1 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | mount 2.38.1-5+b1 No fix yet | — | Not Applicable |
| CVE-2025-27587 | NONE0 | openssl 3.0.11-1~deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | passwd 1:4.13+dfsg1-1+b1 No fix yet | — | Not Applicable |
| CVE-2026-7010 | NONE0 | perl-base 5.36.0-7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-57433 | NONE0 | perl-base 5.36.0-7 No fix yet | — | Not Applicable |
| CVE-2026-7017 | NONE0 | perl-base 5.36.0-7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| TEMP-0517018-A83CE6 | NONE0 | sysvinit-utils 3.06-4 No fix yet | — | Not Applicable |
| TEMP-0290435-0B57B5 | NONE0 | tar 1.34+dfsg-1.2 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | util-linux 2.38.1-5+b1 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | util-linux 2.38.1-5+b1 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | util-linux-extra 2.38.1-5+b1 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | util-linux-extra 2.38.1-5+b1 No fix yet | — | Not Applicable |
Want to check another image? Run a full scan with the Docker Security Scanner.