Last scanned:
This base/runtime image is a reasonable foundation, but it ships vulnerabilities worth remediating in the images built on top of it. The most relevant issue is CVE-2026-42013, a GnuTLS flaw that could let a forged certificate be accepted and enable a man-in-the-middle attack, but it only applies when a GnuTLS-based client connects to a malicious server, and the image's TLS clients may not use GnuTLS. The related DTLS flaws in CVE-2026-33846 and CVE-2026-42009 mainly risk service disruption rather than data exposure. Images inheriting this base should confirm whether any TLS workload uses GnuTLS before deciding on a fix, and the exposed-surface findings should be patched in the final image as routine hygiene. Note: this is a general-purpose base/runtime image — many findings live in components that an application built on top may never load, so actual exploitability depends on the final image. For an accurate risk picture, re-scan the final application image with context.
Hardening plan for this image · 6 steps
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-42013 | MEDIUM6.56 | libgnutls30 3.7.9-2+deb12u6 fixed in 3.7.9-2+deb12u7 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-33846 | MEDIUM6 | libgnutls30 3.7.9-2+deb12u6 fixed in 3.7.9-2+deb12u7 | 1.3% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2026-42009 | MEDIUM6 | libgnutls30 3.7.9-2+deb12u6 fixed in 3.7.9-2+deb12u7 | 1.3% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2026-3833 | MEDIUM5.92 | libgnutls30 3.7.9-2+deb12u6 fixed in 3.7.9-2+deb12u7 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-42011 | MEDIUM5.92 | libgnutls30 3.7.9-2+deb12u6 fixed in 3.7.9-2+deb12u7 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-5435 | MEDIUM5.9 | libc-bin 2.36-9+deb12u13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.9 | libc-bin 2.36-9+deb12u13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.9 | libc-bin 2.36-9+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.9 | libc-bin 2.36-9+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.9 | libc-bin 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.9 | libc-dev-bin 2.36-9+deb12u13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.9 | libc-dev-bin 2.36-9+deb12u13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.9 | libc-dev-bin 2.36-9+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.9 | libc-dev-bin 2.36-9+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.9 | libc-dev-bin 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.9 | libc6 2.36-9+deb12u13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.9 | libc6 2.36-9+deb12u13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.9 | libc6 2.36-9+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.9 | libc6 2.36-9+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.9 | libc6 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.9 | libc6-dev 2.36-9+deb12u13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.9 | libc6-dev 2.36-9+deb12u13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.9 | libc6-dev 2.36-9+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.9 | libc6-dev 2.36-9+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.9 | libc6-dev 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-31790 | MEDIUM5.9 | libssl3 3.0.18-1~deb12u2 fixed in 3.0.19-1~deb12u2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-54872 | MEDIUM5.9 | libssl3 3.0.18-1~deb12u2 fixed in 3.0.22-1~deb12u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-75805 | MEDIUM5.9 | libssl3 3.0.18-1~deb12u2 fixed in 3.0.22-1~deb12u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-77696 | MEDIUM5.9 | libssl3 3.0.18-1~deb12u2 fixed in 3.0.22-1~deb12u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42770 | MEDIUM5.9 | libssl3 3.0.18-1~deb12u2 fixed in 3.0.20-1~deb12u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-9076 | MEDIUM5.9 | libssl3 3.0.18-1~deb12u2 fixed in 3.0.20-1~deb12u2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-42010 | MEDIUM5.88 | libgnutls30 3.7.9-2+deb12u6 fixed in 3.7.9-2+deb12u7 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-31789 | MEDIUM5.88 | libssl3 3.0.18-1~deb12u2 fixed in 3.0.19-1~deb12u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-45853 | MEDIUM5.88 | zlib1g 1:1.2.13.dfsg-1 No fix yet | 3.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42012 | MEDIUM5.68 | libgnutls30 3.7.9-2+deb12u6 fixed in 3.7.9-2+deb12u7 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-6368 | MEDIUM5.5 | libc-bin 2.36-9+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM5.5 | libc-dev-bin 2.36-9+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM5.5 | libc6 2.36-9+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM5.5 | libc6-dev 2.36-9+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-7383 | MEDIUM5.5 | libssl3 3.0.18-1~deb12u2 fixed in 3.0.20-1~deb12u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-15059 | MEDIUM5.5 | libsystemd0 252.39-1~deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15059 | MEDIUM5.5 | libudev1 252.39-1~deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-33845 | MEDIUM5.46 | libgnutls30 3.7.9-2+deb12u6 fixed in 3.7.9-2+deb12u7 | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-45445 | MEDIUM5.46 | libssl3 3.0.18-1~deb12u2 fixed in 3.0.20-1~deb12u2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM5.3 | libc-bin 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM5.3 | libc-bin 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-8674 | MEDIUM5.3 | libc-bin 2.36-9+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM5.3 | libc-dev-bin 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM5.3 | libc-dev-bin 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-8674 | MEDIUM5.3 | libc-dev-bin 2.36-9+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM5.3 | libc6 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM5.3 | libc6 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-8674 | MEDIUM5.3 | libc6 2.36-9+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM5.3 | libc6-dev 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM5.3 | libc6-dev 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-8674 | MEDIUM5.3 | libc6-dev 2.36-9+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-75806 | MEDIUM5.3 | libssl3 3.0.18-1~deb12u2 fixed in 3.0.22-1~deb12u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42766 | MEDIUM5.3 | libssl3 3.0.18-1~deb12u2 fixed in 3.0.20-1~deb12u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42767 | MEDIUM5.3 | libssl3 3.0.18-1~deb12u2 fixed in 3.0.22-1~deb12u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-16742 | MEDIUM5.28 | libsystemd0 252.39-1~deb12u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-16742 | MEDIUM5.28 | libudev1 252.39-1~deb12u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42014 | MEDIUM5.28 | libgnutls30 3.7.9-2+deb12u6 fixed in 3.7.9-2+deb12u7 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-42250 | MEDIUM5 | libbz2-1.0 1.0.8-5+b1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM5 | libc-bin 2.36-9+deb12u13 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM5 | libc-bin 2.36-9+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM5 | libc-dev-bin 2.36-9+deb12u13 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM5 | libc-dev-bin 2.36-9+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM5 | libc6 2.36-9+deb12u13 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM5 | libc6 2.36-9+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM5 | libc6-dev 2.36-9+deb12u13 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM5 | libc6-dev 2.36-9+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34180 | MEDIUM5 | libssl3 3.0.18-1~deb12u2 fixed in 3.0.20-1~deb12u2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-5260 | MEDIUM4.92 | libgnutls30 3.7.9-2+deb12u6 fixed in 3.7.9-2+deb12u7 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-86145 | MEDIUM4.92 | libpcre2-8-0 10.42-1 fixed in 10.42-1+deb12u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.9 | libc-bin 2.36-9+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.9 | libc-dev-bin 2.36-9+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.9 | libc6 2.36-9+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.9 | libc6-dev 2.36-9+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0861 | MEDIUM4.86 | libc-bin 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0861 | MEDIUM4.86 | libc-dev-bin 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0861 | MEDIUM4.86 | libc6 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0861 | MEDIUM4.86 | libc6-dev 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-28387 | MEDIUM4.86 | libssl3 3.0.18-1~deb12u2 fixed in 3.0.19-1~deb12u2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-45447 | MEDIUM4.86 | libssl3 3.0.18-1~deb12u2 fixed in 3.0.20-1~deb12u2 | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-53615 | MEDIUM4.8 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53615 | MEDIUM4.8 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53615 | MEDIUM4.8 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53615 | MEDIUM4.8 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM4.74 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM4.74 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM4.74 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM4.74 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM4.74 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM4.74 | mount 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM4.74 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM4.74 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM4.68 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM4.68 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM4.68 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM4.68 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM4.68 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM4.68 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89161 | MEDIUM4.68 | libpcre2-8-0 10.42-1 fixed in 10.42-1+deb12u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM4.68 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM4.68 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM4.68 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM4.68 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM4.68 | mount 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM4.68 | mount 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-48962 | MEDIUM4.68 | perl-base 5.36.0-7+deb12u3 fixed in 5.36.0-7+deb12u4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM4.68 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM4.68 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM4.68 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM4.68 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM4.62 | gcc-12-base 12.2.0-14+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM4.62 | libasan8 12.2.0-14+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM4.62 | libatomic1 12.2.0-14+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM4.62 | libcc1-0 12.2.0-14+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM4.62 | libgcc-12-dev 12.2.0-14+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM4.62 | libgcc-s1 12.2.0-14+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM4.62 | libgomp1 12.2.0-14+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM4.62 | libitm1 12.2.0-14+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM4.62 | liblsan0 12.2.0-14+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM4.62 | libquadmath0 12.2.0-14+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM4.62 | libstdc++6 12.2.0-14+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM4.62 | libtsan2 12.2.0-14+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM4.62 | libubsan1 12.2.0-14+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-103111 | MEDIUM4.56 | libpcre2-8-0 10.42-1 fixed in 10.42-1+deb12u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-41989 | MEDIUM4.5 | libgcrypt20 1.10.1-3 fixed in 1.10.1-3+deb12u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM4.5 | libgssapi-krb5-2 1.20.1-2+deb12u4 fixed in 1.20.1-2+deb12u5 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM4.5 | libgssapi-krb5-2 1.20.1-2+deb12u4 fixed in 1.20.1-2+deb12u5 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM4.5 | libk5crypto3 1.20.1-2+deb12u4 fixed in 1.20.1-2+deb12u5 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM4.5 | libk5crypto3 1.20.1-2+deb12u4 fixed in 1.20.1-2+deb12u5 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM4.5 | libkrb5-3 1.20.1-2+deb12u4 fixed in 1.20.1-2+deb12u5 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM4.5 | libkrb5-3 1.20.1-2+deb12u4 fixed in 1.20.1-2+deb12u5 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM4.5 | libkrb5support0 1.20.1-2+deb12u4 fixed in 1.20.1-2+deb12u5 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM4.5 | libkrb5support0 1.20.1-2+deb12u4 fixed in 1.20.1-2+deb12u5 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-28388 | MEDIUM4.5 | libssl3 3.0.18-1~deb12u2 fixed in 3.0.19-1~deb12u2 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-28389 | MEDIUM4.5 | libssl3 3.0.18-1~deb12u2 fixed in 3.0.19-1~deb12u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-28390 | MEDIUM4.5 | libssl3 3.0.18-1~deb12u2 fixed in 3.0.19-1~deb12u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-63072 | MEDIUM4.5 | libssl3 3.0.18-1~deb12u2 fixed in 3.0.22-1~deb12u1 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-63076 | MEDIUM4.5 | libssl3 3.0.18-1~deb12u2 fixed in 3.0.22-1~deb12u1 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-54874 | MEDIUM4.5 | libssl3 3.0.18-1~deb12u2 fixed in 3.0.22-1~deb12u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63074 | MEDIUM4.5 | libssl3 3.0.18-1~deb12u2 fixed in 3.0.22-1~deb12u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-54874 | MEDIUM4.5 | openssl 3.0.18-1~deb12u2 fixed in 3.0.22-1~deb12u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42497 | MEDIUM4.5 | perl-base 5.36.0-7+deb12u3 fixed in 5.36.0-7+deb12u4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-57433 | MEDIUM4.5 | perl-base 5.36.0-7+deb12u3 fixed in 5.36.0-7+deb12u4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-9538 | MEDIUM4.5 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-89157 | MEDIUM4.44 | libpcre2-8-0 10.42-1 fixed in 10.42-1+deb12u1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-84782 | MEDIUM4.44 | libssl3 3.0.18-1~deb12u2 fixed in 3.0.22-1~deb12u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-34182 | MEDIUM4.44 | libssl3 3.0.18-1~deb12u2 fixed in 3.0.20-1~deb12u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-84782 | MEDIUM4.44 | openssl 3.0.18-1~deb12u2 fixed in 3.0.22-1~deb12u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-54369 | MEDIUM4.26 | libacl1 2.3.1-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42015 | MEDIUM4.24 | libgnutls30 3.7.9-2+deb12u6 fixed in 3.7.9-2+deb12u7 | 0.7% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-53613 | MEDIUM4.2 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM4.2 | cpp-12 12.2.0-14+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM4.2 | gcc-12 12.2.0-14+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM4.2 | gcc-12-base 12.2.0-14+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM4.2 | libasan8 12.2.0-14+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM4.2 | libatomic1 12.2.0-14+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM4.2 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-86805 | MEDIUM4.2 | libc-bin 2.36-9+deb12u13 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95818 | MEDIUM4.2 | libc-bin 2.36-9+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86805 | MEDIUM4.2 | libc-dev-bin 2.36-9+deb12u13 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95818 | MEDIUM4.2 | libc-dev-bin 2.36-9+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86805 | MEDIUM4.2 | libc6 2.36-9+deb12u13 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95818 | MEDIUM4.2 | libc6 2.36-9+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86805 | MEDIUM4.2 | libc6-dev 2.36-9+deb12u13 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95818 | MEDIUM4.2 | libc6-dev 2.36-9+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4878 | MEDIUM4.2 | libcap2 1:2.66-4+deb12u2+b2 fixed in 1:2.66-4+deb12u3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM4.2 | libcc1-0 12.2.0-14+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM4.2 | libgcc-12-dev 12.2.0-14+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM4.2 | libgcc-s1 12.2.0-14+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM4.2 | libgomp1 12.2.0-14+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM4.2 | libitm1 12.2.0-14+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM4.2 | liblsan0 12.2.0-14+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM4.2 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM4.2 | libquadmath0 12.2.0-14+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM4.2 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM4.2 | libstdc++6 12.2.0-14+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM4.2 | libtsan2 12.2.0-14+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM4.2 | libubsan1 12.2.0-14+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM4.2 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM4.2 | mount 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | mount 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM4.2 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM4.2 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | MEDIUM4.2 | libc-bin 2.36-9+deb12u13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | MEDIUM4.2 | libc-bin 2.36-9+deb12u13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | MEDIUM4.2 | libc-dev-bin 2.36-9+deb12u13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | MEDIUM4.2 | libc-dev-bin 2.36-9+deb12u13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | MEDIUM4.2 | libc6 2.36-9+deb12u13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | MEDIUM4.2 | libc6 2.36-9+deb12u13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | MEDIUM4.2 | libc6-dev 2.36-9+deb12u13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | MEDIUM4.2 | libc6-dev 2.36-9+deb12u13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19499 | MEDIUM4.08 | libc-bin 2.36-9+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-19499 | MEDIUM4.08 | libc-dev-bin 2.36-9+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-19499 | MEDIUM4.08 | libc6 2.36-9+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-19499 | MEDIUM4.08 | libc6-dev 2.36-9+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2011-3389 | MEDIUM4.06 | libgnutls30 3.7.9-2+deb12u6 No fix yet | 73.3% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2026-4105 | MEDIUM4.02 | libsystemd0 252.39-1~deb12u1 fixed in 252.39-1~deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4105 | MEDIUM4.02 | libudev1 252.39-1~deb12u1 fixed in 252.39-1~deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| DLA-4726-1 | MEDIUM4 | ca-certificates 20230311+deb12u1 fixed in 20250419~deb12u1 | — | Directly Exposed |
| DLA-4845-1 | MEDIUM4 | ca-certificates 20230311+deb12u1 fixed in 20250419~deb12u2 | — | Directly Exposed |
| CVE-2026-4438 | MEDIUM4 | libc-bin 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | MEDIUM4 | libc-dev-bin 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | MEDIUM4 | libc6 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | MEDIUM4 | libc6-dev 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | LOW3.9 | libc-bin 2.36-9+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | LOW3.9 | libc-dev-bin 2.36-9+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | LOW3.9 | libc6 2.36-9+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | LOW3.9 | libc6-dev 2.36-9+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | LOW3.9 | libgssapi-krb5-2 1.20.1-2+deb12u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | LOW3.9 | libk5crypto3 1.20.1-2+deb12u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | LOW3.9 | libkrb5-3 1.20.1-2+deb12u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | LOW3.9 | libkrb5support0 1.20.1-2+deb12u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-89158 | LOW3.9 | libpcre2-8-0 10.42-1 fixed in 10.42-1+deb12u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89160 | LOW3.9 | libpcre2-8-0 10.42-1 fixed in 10.42-1+deb12u1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-50495 | LOW3.9 | libtinfo6 6.4-4 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-85231 | LOW3.9 | libtirpc-common 1.3.3+ds-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-85231 | LOW3.9 | libtirpc-dev 1.3.3+ds-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-85231 | LOW3.9 | libtirpc3 1.3.3+ds-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-50495 | LOW3.9 | ncurses-base 6.4-4 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-50495 | LOW3.9 | ncurses-bin 6.4-4 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2025-15649 | LOW3.9 | perl-base 5.36.0-7+deb12u3 fixed in 5.36.0-7+deb12u4 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-19487 | LOW3.9 | perl-base 5.36.0-7+deb12u3 fixed in 5.36.0-7+deb12u4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2017-13716 | LOW3.9 | libbinutils 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20673 | LOW3.9 | libbinutils 2.40-2 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20712 | LOW3.9 | libbinutils 2.40-2 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-9996 | LOW3.9 | libbinutils 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-1153 | LOW3.9 | libbinutils 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2025-66864 | LOW3.9 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | LOW3.9 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | LOW3.9 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | LOW3.9 | libbinutils 2.40-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | LOW3.9 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-15003 | LOW3.9 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18220 | LOW3.9 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19548 | LOW3.9 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | LOW3.9 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | LOW3.9 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | LOW3.9 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6844 | LOW3.9 | libbinutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | LOW3.9 | libbinutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | LOW3.9 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90801 | LOW3.9 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90802 | LOW3.9 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90803 | LOW3.9 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90804 | LOW3.9 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90828 | LOW3.9 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90829 | LOW3.9 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90830 | LOW3.9 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90831 | LOW3.9 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91779 | LOW3.9 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91780 | LOW3.9 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91782 | LOW3.9 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2010-4756 | LOW3.9 | libc-bin 2.36-9+deb12u13 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | LOW3.9 | libc-bin 2.36-9+deb12u13 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010022 | LOW3.9 | libc-bin 2.36-9+deb12u13 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010023 | LOW3.9 | libc-bin 2.36-9+deb12u13 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | LOW3.9 | libc-bin 2.36-9+deb12u13 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | LOW3.9 | libc-bin 2.36-9+deb12u13 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | LOW3.9 | libc-bin 2.36-9+deb12u13 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | LOW3.9 | libc-dev-bin 2.36-9+deb12u13 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | LOW3.9 | libc-dev-bin 2.36-9+deb12u13 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010022 | LOW3.9 | libc-dev-bin 2.36-9+deb12u13 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010023 | LOW3.9 | libc-dev-bin 2.36-9+deb12u13 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | LOW3.9 | libc-dev-bin 2.36-9+deb12u13 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | LOW3.9 | libc-dev-bin 2.36-9+deb12u13 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | LOW3.9 | libc-dev-bin 2.36-9+deb12u13 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | LOW3.9 | libc6 2.36-9+deb12u13 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | LOW3.9 | libc6 2.36-9+deb12u13 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010022 | LOW3.9 | libc6 2.36-9+deb12u13 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010023 | LOW3.9 | libc6 2.36-9+deb12u13 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | LOW3.9 | libc6 2.36-9+deb12u13 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | LOW3.9 | libc6 2.36-9+deb12u13 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | LOW3.9 | libc6 2.36-9+deb12u13 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | LOW3.9 | libc6-dev 2.36-9+deb12u13 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | LOW3.9 | libc6-dev 2.36-9+deb12u13 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010022 | LOW3.9 | libc6-dev 2.36-9+deb12u13 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010023 | LOW3.9 | libc6-dev 2.36-9+deb12u13 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | LOW3.9 | libc6-dev 2.36-9+deb12u13 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | LOW3.9 | libc6-dev 2.36-9+deb12u13 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | LOW3.9 | libc6-dev 2.36-9+deb12u13 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | LOW3.9 | libctf-nobfd0 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20673 | LOW3.9 | libctf-nobfd0 2.40-2 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20712 | LOW3.9 | libctf-nobfd0 2.40-2 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-9996 | LOW3.9 | libctf-nobfd0 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-1153 | LOW3.9 | libctf-nobfd0 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2025-66864 | LOW3.9 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | LOW3.9 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | LOW3.9 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | LOW3.9 | libctf-nobfd0 2.40-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | LOW3.9 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-15003 | LOW3.9 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18220 | LOW3.9 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19548 | LOW3.9 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | LOW3.9 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | LOW3.9 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | LOW3.9 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6844 | LOW3.9 | libctf-nobfd0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | LOW3.9 | libctf-nobfd0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | LOW3.9 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90801 | LOW3.9 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90802 | LOW3.9 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90803 | LOW3.9 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90804 | LOW3.9 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90828 | LOW3.9 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90829 | LOW3.9 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90830 | LOW3.9 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90831 | LOW3.9 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91779 | LOW3.9 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91780 | LOW3.9 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91782 | LOW3.9 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2017-13716 | LOW3.9 | libctf0 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20673 | LOW3.9 | libctf0 2.40-2 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20712 | LOW3.9 | libctf0 2.40-2 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-9996 | LOW3.9 | libctf0 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-1153 | LOW3.9 | libctf0 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2025-66864 | LOW3.9 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | LOW3.9 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | LOW3.9 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | LOW3.9 | libctf0 2.40-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | LOW3.9 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-15003 | LOW3.9 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18220 | LOW3.9 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19548 | LOW3.9 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | LOW3.9 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | LOW3.9 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | LOW3.9 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6844 | LOW3.9 | libctf0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | LOW3.9 | libctf0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | LOW3.9 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90801 | LOW3.9 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90802 | LOW3.9 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90803 | LOW3.9 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90804 | LOW3.9 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90828 | LOW3.9 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90829 | LOW3.9 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90830 | LOW3.9 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90831 | LOW3.9 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91779 | LOW3.9 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91780 | LOW3.9 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91782 | LOW3.9 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2017-13716 | LOW3.9 | libgprofng0 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20673 | LOW3.9 | libgprofng0 2.40-2 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20712 | LOW3.9 | libgprofng0 2.40-2 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-9996 | LOW3.9 | libgprofng0 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-1153 | LOW3.9 | libgprofng0 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2025-66864 | LOW3.9 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | LOW3.9 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | LOW3.9 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | LOW3.9 | libgprofng0 2.40-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | LOW3.9 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-15003 | LOW3.9 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18220 | LOW3.9 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19548 | LOW3.9 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | LOW3.9 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | LOW3.9 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | LOW3.9 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6844 | LOW3.9 | libgprofng0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | LOW3.9 | libgprofng0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | LOW3.9 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90801 | LOW3.9 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90802 | LOW3.9 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90803 | LOW3.9 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90804 | LOW3.9 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90828 | LOW3.9 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90829 | LOW3.9 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90830 | LOW3.9 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90831 | LOW3.9 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91779 | LOW3.9 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91780 | LOW3.9 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91782 | LOW3.9 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40225 | LOW3.84 | libsystemd0 252.39-1~deb12u1 fixed in 252.39-1~deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40226 | LOW3.84 | libsystemd0 252.39-1~deb12u1 fixed in 252.39-1~deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40225 | LOW3.84 | libudev1 252.39-1~deb12u1 fixed in 252.39-1~deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40226 | LOW3.84 | libudev1 252.39-1~deb12u1 fixed in 252.39-1~deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-54370 | LOW3.78 | libacl1 2.3.1-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-54371 | LOW3.78 | libattr1 1:2.5.1-4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5958 | LOW3.78 | sed 4.9-1 fixed in 4.9-1+deb12u1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-13757 | LOW3.72 | libp11-kit0 0.24.1-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18938 | LOW3.72 | libp11-kit0 0.24.1-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2011-3374 | LOW3.7 | libapt-pkg6.0 2.6.1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-97399 | LOW3.7 | libc-bin 2.36-9+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-97399 | LOW3.7 | libc-dev-bin 2.36-9+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-97399 | LOW3.7 | libc6 2.36-9+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-97399 | LOW3.7 | libc6-dev 2.36-9+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-35189 | LOW3.7 | libssl3 3.0.18-1~deb12u2 fixed in 3.0.22-1~deb12u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-45446 | LOW3.7 | libssl3 3.0.18-1~deb12u2 fixed in 3.0.20-1~deb12u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-75803 | LOW3.7 | libssl3 3.0.18-1~deb12u2 fixed in 3.0.22-1~deb12u1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-89156 | LOW3.54 | libpcre2-8-0 10.42-1 fixed in 10.42-1+deb12u1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-13151 | LOW3.54 | libtasn1-6 4.19.0-2+deb12u1 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-31790 | LOW3.54 | openssl 3.0.18-1~deb12u2 fixed in 3.0.19-1~deb12u2 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-54872 | LOW3.54 | openssl 3.0.18-1~deb12u2 fixed in 3.0.22-1~deb12u2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-75805 | LOW3.54 | openssl 3.0.18-1~deb12u2 fixed in 3.0.22-1~deb12u2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-77696 | LOW3.54 | openssl 3.0.18-1~deb12u2 fixed in 3.0.22-1~deb12u2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42770 | LOW3.54 | openssl 3.0.18-1~deb12u2 fixed in 3.0.20-1~deb12u2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-9076 | LOW3.54 | openssl 3.0.18-1~deb12u2 fixed in 3.0.20-1~deb12u2 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-31789 | LOW3.53 | openssl 3.0.18-1~deb12u2 fixed in 3.0.19-1~deb12u2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-8376 | LOW3.53 | perl-base 5.36.0-7+deb12u3 fixed in 5.36.0-7+deb12u4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-15534 | LOW3.42 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | LOW3.31 | libbinutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-1972 | LOW3.31 | libbinutils 2.40-2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-53589 | LOW3.31 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-57360 | LOW3.31 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-0840 | LOW3.31 | libbinutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | LOW3.31 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | LOW3.31 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | LOW3.31 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | LOW3.31 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | LOW3.31 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | LOW3.31 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | LOW3.31 | libbinutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | LOW3.31 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | LOW3.31 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | LOW3.31 | libbinutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | LOW3.31 | libbinutils 2.40-2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-1179 | LOW3.31 | libbinutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | LOW3.31 | libbinutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | LOW3.31 | libbinutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | LOW3.31 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | LOW3.31 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | LOW3.31 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | LOW3.31 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | LOW3.31 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | LOW3.31 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | LOW3.31 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8224 | LOW3.31 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | LOW3.31 | libctf-nobfd0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-1972 | LOW3.31 | libctf-nobfd0 2.40-2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-53589 | LOW3.31 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-57360 | LOW3.31 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-0840 | LOW3.31 | libctf-nobfd0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | LOW3.31 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | LOW3.31 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | LOW3.31 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | LOW3.31 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | LOW3.31 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | LOW3.31 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | LOW3.31 | libctf-nobfd0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | LOW3.31 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | LOW3.31 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | LOW3.31 | libctf-nobfd0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | LOW3.31 | libctf-nobfd0 2.40-2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-1179 | LOW3.31 | libctf-nobfd0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | LOW3.31 | libctf-nobfd0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | LOW3.31 | libctf-nobfd0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | LOW3.31 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | LOW3.31 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | LOW3.31 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | LOW3.31 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | LOW3.31 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | LOW3.31 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | LOW3.31 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8224 | LOW3.31 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | LOW3.31 | libctf0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-1972 | LOW3.31 | libctf0 2.40-2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-53589 | LOW3.31 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-57360 | LOW3.31 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-0840 | LOW3.31 | libctf0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | LOW3.31 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | LOW3.31 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | LOW3.31 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | LOW3.31 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | LOW3.31 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | LOW3.31 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | LOW3.31 | libctf0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | LOW3.31 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | LOW3.31 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | LOW3.31 | libctf0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | LOW3.31 | libctf0 2.40-2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-1179 | LOW3.31 | libctf0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | LOW3.31 | libctf0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | LOW3.31 | libctf0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | LOW3.31 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | LOW3.31 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | LOW3.31 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | LOW3.31 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | LOW3.31 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | LOW3.31 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | LOW3.31 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8224 | LOW3.31 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | LOW3.31 | libgprofng0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-1972 | LOW3.31 | libgprofng0 2.40-2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-53589 | LOW3.31 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-57360 | LOW3.31 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-0840 | LOW3.31 | libgprofng0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | LOW3.31 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | LOW3.31 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | LOW3.31 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | LOW3.31 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | LOW3.31 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | LOW3.31 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | LOW3.31 | libgprofng0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | LOW3.31 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | LOW3.31 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | LOW3.31 | libgprofng0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | LOW3.31 | libgprofng0 2.40-2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-1179 | LOW3.31 | libgprofng0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | LOW3.31 | libgprofng0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | LOW3.31 | libgprofng0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | LOW3.31 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | LOW3.31 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | LOW3.31 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | LOW3.31 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | LOW3.31 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | LOW3.31 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | LOW3.31 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8224 | LOW3.31 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | LOW3.31 | libsystemd0 252.39-1~deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | LOW3.31 | libsystemd0 252.39-1~deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | LOW3.31 | libsystemd0 252.39-1~deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | LOW3.31 | libudev1 252.39-1~deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | LOW3.31 | libudev1 252.39-1~deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | LOW3.31 | libudev1 252.39-1~deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-7383 | LOW3.3 | openssl 3.0.18-1~deb12u2 fixed in 3.0.20-1~deb12u2 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-5704 | LOW3.3 | tar 1.34+dfsg-1.2+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-27171 | LOW3.3 | zlib1g 1:1.2.13.dfsg-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66861 | LOW3.3 | libbinutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66862 | LOW3.3 | libbinutils 2.40-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW3.3 | libbinutils 2.40-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW3.3 | libbinutils 2.40-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW3.3 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW3.3 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW3.3 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91781 | LOW3.3 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66861 | LOW3.3 | libctf-nobfd0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66862 | LOW3.3 | libctf-nobfd0 2.40-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW3.3 | libctf-nobfd0 2.40-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW3.3 | libctf-nobfd0 2.40-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW3.3 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW3.3 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW3.3 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91781 | LOW3.3 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66861 | LOW3.3 | libctf0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66862 | LOW3.3 | libctf0 2.40-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW3.3 | libctf0 2.40-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW3.3 | libctf0 2.40-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW3.3 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW3.3 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW3.3 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91781 | LOW3.3 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66861 | LOW3.3 | libgprofng0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66862 | LOW3.3 | libgprofng0 2.40-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW3.3 | libgprofng0 2.40-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW3.3 | libgprofng0 2.40-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW3.3 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW3.3 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW3.3 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91781 | LOW3.3 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW3.3 | libsystemd0 252.39-1~deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW3.3 | libudev1 252.39-1~deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45445 | LOW3.28 | openssl 3.0.18-1~deb12u2 fixed in 3.0.20-1~deb12u2 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-13221 | LOW3.28 | perl-base 5.36.0-7+deb12u3 fixed in 5.36.0-7+deb12u4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-42496 | LOW3.28 | perl-base 5.36.0-7+deb12u3 fixed in 5.36.0-7+deb12u4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW3.18 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | LOW3.18 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34743 | LOW3.18 | liblzma5 5.4.1-1 fixed in 5.4.1-1+deb12u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | LOW3.18 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | LOW3.18 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-85977 | LOW3.18 | libtirpc-common 1.3.3+ds-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-85977 | LOW3.18 | libtirpc-dev 1.3.3+ds-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-85977 | LOW3.18 | libtirpc3 1.3.3+ds-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | LOW3.18 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | LOW3.18 | mount 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | mount 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-75806 | LOW3.18 | openssl 3.0.18-1~deb12u2 fixed in 3.0.22-1~deb12u2 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-42766 | LOW3.18 | openssl 3.0.18-1~deb12u2 fixed in 3.0.20-1~deb12u2 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-42767 | LOW3.18 | openssl 3.0.18-1~deb12u2 fixed in 3.0.22-1~deb12u1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-12087 | LOW3.18 | perl-base 5.36.0-7+deb12u3 fixed in 5.36.0-7+deb12u4 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | LOW3.18 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | LOW3.18 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libbinutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libctf-nobfd0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libctf0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libgprofng0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-67693 | LOW3.12 | libgnutls30 3.7.9-2+deb12u6 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-88647 | LOW3.12 | libgnutls30 3.7.9-2+deb12u6 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-88648 | LOW3.12 | libgnutls30 3.7.9-2+deb12u6 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-95184 | LOW3.12 | libgnutls30 3.7.9-2+deb12u6 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-57432 | LOW3.02 | perl-base 5.36.0-7+deb12u3 fixed in 5.36.0-7+deb12u4 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-2219 | LOW3 | dpkg 1.21.22 fixed in 1.21.23 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-34180 | LOW3 | openssl 3.0.18-1~deb12u2 fixed in 3.0.20-1~deb12u2 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-48959 | LOW3 | perl-base 5.36.0-7+deb12u3 fixed in 5.36.0-7+deb12u4 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-7010 | LOW3 | perl-base 5.36.0-7+deb12u3 fixed in 5.36.0-7+deb12u4 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-7017 | LOW3 | perl-base 5.36.0-7+deb12u3 fixed in 5.36.0-7+deb12u4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-85091 | LOW3 | zlib1g 1:1.2.13.dfsg-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5419 | LOW2.96 | libgnutls30 3.7.9-2+deb12u6 fixed in 3.7.9-2+deb12u7 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-107708 | LOW2.94 | libgssapi-krb5-2 1.20.1-2+deb12u4 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | LOW2.94 | libk5crypto3 1.20.1-2+deb12u4 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | LOW2.94 | libkrb5-3 1.20.1-2+deb12u4 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | LOW2.94 | libkrb5support0 1.20.1-2+deb12u4 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-28387 | LOW2.92 | openssl 3.0.18-1~deb12u2 fixed in 3.0.19-1~deb12u2 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-45447 | LOW2.92 | openssl 3.0.18-1~deb12u2 fixed in 3.0.20-1~deb12u2 | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-53615 | LOW2.88 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | LOW2.88 | mount 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | LOW2.88 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | LOW2.88 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-54411 | LOW2.88 | libpam-modules 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-54411 | LOW2.88 | libpam-modules-bin 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-54411 | LOW2.88 | libpam-runtime 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-54411 | LOW2.88 | libpam0g 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.82 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68972 | LOW2.82 | gpgv 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-41991 | LOW2.82 | gzip 1.12-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | LOW2.82 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | LOW2.82 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | LOW2.82 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | LOW2.82 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | LOW2.82 | mount 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | LOW2.82 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | LOW2.82 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-29111 | LOW2.81 | libsystemd0 252.39-1~deb12u1 fixed in 252.39-1~deb12u2 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69720 | LOW2.81 | libtinfo6 6.4-4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-29111 | LOW2.81 | libudev1 252.39-1~deb12u1 fixed in 252.39-1~deb12u2 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69720 | LOW2.81 | ncurses-base 6.4-4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-69720 | LOW2.81 | ncurses-bin 6.4-4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-8225 | LOW2.8 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libsystemd0 252.39-1~deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libudev1 252.39-1~deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW2.8 | libbinutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.8 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.8 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW2.8 | libctf-nobfd0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.8 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.8 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW2.8 | libctf0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.8 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.8 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW2.8 | libgprofng0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.8 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.8 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | LOW2.77 | cpp-12 12.2.0-14+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-95619 | LOW2.77 | gcc-12 12.2.0-14+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-41992 | LOW2.7 | gzip 1.12-1 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-28388 | LOW2.7 | openssl 3.0.18-1~deb12u2 fixed in 3.0.19-1~deb12u2 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-28389 | LOW2.7 | openssl 3.0.18-1~deb12u2 fixed in 3.0.19-1~deb12u2 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-28390 | LOW2.7 | openssl 3.0.18-1~deb12u2 fixed in 3.0.19-1~deb12u2 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-63072 | LOW2.7 | openssl 3.0.18-1~deb12u2 fixed in 3.0.22-1~deb12u1 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-63076 | LOW2.7 | openssl 3.0.18-1~deb12u2 fixed in 3.0.22-1~deb12u1 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2026-63074 | LOW2.7 | openssl 3.0.18-1~deb12u2 fixed in 3.0.22-1~deb12u1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-34182 | LOW2.66 | openssl 3.0.18-1~deb12u2 fixed in 3.0.20-1~deb12u2 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-18477 | LOW2.64 | tar 1.34+dfsg-1.2+deb12u1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-18508 | LOW2.64 | tar 1.34+dfsg-1.2+deb12u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1148 | LOW2.63 | libbinutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libbinutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libbinutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libbinutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libbinutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW2.63 | libctf-nobfd0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libctf-nobfd0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libctf-nobfd0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libctf-nobfd0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libctf-nobfd0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW2.63 | libctf0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libctf0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libctf0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libctf0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libctf0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW2.63 | libgprofng0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libgprofng0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libgprofng0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libgprofng0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libgprofng0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-30258 | LOW2.4 | gpgv 2.2.40-1.1+deb12u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-10041 | LOW2.4 | libpam-modules 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-10041 | LOW2.4 | libpam-modules-bin 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-10041 | LOW2.4 | libpam-runtime 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-10041 | LOW2.4 | libpam0g 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| DLA-4783-1 | LOW2.4 | liblzma5 5.4.1-1 fixed in 5.4.1-1+deb12u2 | — | Directly Exposed |
| TEMP-1147318-639065 | LOW2.4 | liblzma5 5.4.1-1 fixed in 5.4.1-1+deb12u2 | — | Directly Exposed |
| CVE-2026-82560 | LOW2.4 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | LOW2.34 | libc-bin 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-4437 | LOW2.34 | libc-dev-bin 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-4437 | LOW2.34 | libc6 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-4437 | LOW2.34 | libc6-dev 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2017-13716 | LOW2.34 | binutils 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20673 | LOW2.34 | binutils 2.40-2 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20712 | LOW2.34 | binutils 2.40-2 No fix yet | 2.6% Low-Moderate Risk | Post-Exploit |
| CVE-2018-9996 | LOW2.34 | binutils 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1153 | LOW2.34 | binutils 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2025-66864 | LOW2.34 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66866 | LOW2.34 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69649 | LOW2.34 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69650 | LOW2.34 | binutils 2.40-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.34 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-15003 | LOW2.34 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-18220 | LOW2.34 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-19548 | LOW2.34 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3441 | LOW2.34 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3442 | LOW2.34 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-4647 | LOW2.34 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6844 | LOW2.34 | binutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6845 | LOW2.34 | binutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6846 | LOW2.34 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90801 | LOW2.34 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90802 | LOW2.34 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90803 | LOW2.34 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90804 | LOW2.34 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90828 | LOW2.34 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90829 | LOW2.34 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90830 | LOW2.34 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90831 | LOW2.34 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-91779 | LOW2.34 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-91780 | LOW2.34 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-91782 | LOW2.34 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2017-13716 | LOW2.34 | binutils-common 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20673 | LOW2.34 | binutils-common 2.40-2 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20712 | LOW2.34 | binutils-common 2.40-2 No fix yet | 2.6% Low-Moderate Risk | Post-Exploit |
| CVE-2018-9996 | LOW2.34 | binutils-common 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1153 | LOW2.34 | binutils-common 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2025-66864 | LOW2.34 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66866 | LOW2.34 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69649 | LOW2.34 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69650 | LOW2.34 | binutils-common 2.40-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.34 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-15003 | LOW2.34 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-18220 | LOW2.34 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-19548 | LOW2.34 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3441 | LOW2.34 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3442 | LOW2.34 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-4647 | LOW2.34 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6844 | LOW2.34 | binutils-common 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6845 | LOW2.34 | binutils-common 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6846 | LOW2.34 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90801 | LOW2.34 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90802 | LOW2.34 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90803 | LOW2.34 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90804 | LOW2.34 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90828 | LOW2.34 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90829 | LOW2.34 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90830 | LOW2.34 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90831 | LOW2.34 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-91779 | LOW2.34 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-91780 | LOW2.34 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-91782 | LOW2.34 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2017-13716 | LOW2.34 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20673 | LOW2.34 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20712 | LOW2.34 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 2.6% Low-Moderate Risk | Post-Exploit |
| CVE-2018-9996 | LOW2.34 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1153 | LOW2.34 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2025-66864 | LOW2.34 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66866 | LOW2.34 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69649 | LOW2.34 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69650 | LOW2.34 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.34 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-15003 | LOW2.34 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-18220 | LOW2.34 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-19548 | LOW2.34 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3441 | LOW2.34 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3442 | LOW2.34 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-4647 | LOW2.34 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6844 | LOW2.34 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6845 | LOW2.34 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6846 | LOW2.34 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90801 | LOW2.34 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90802 | LOW2.34 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90803 | LOW2.34 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90804 | LOW2.34 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90828 | LOW2.34 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90829 | LOW2.34 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90830 | LOW2.34 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90831 | LOW2.34 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-91779 | LOW2.34 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-91780 | LOW2.34 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-91782 | LOW2.34 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW2.34 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56391 | LOW2.34 | coreutils 9.1-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-56392 | LOW2.34 | coreutils 9.1-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-102473 | LOW2.34 | dash 0.5.12-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-102474 | LOW2.34 | dash 0.5.12-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53910 | LOW2.34 | diffutils 1:3.8-4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW2.34 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2018-6829 | LOW2.34 | libgcrypt20 1.10.1-3 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2024-2236 | LOW2.34 | libgcrypt20 1.10.1-3 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | LOW2.34 | libgssapi-krb5-2 1.20.1-2+deb12u4 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | LOW2.34 | libgssapi-krb5-2 1.20.1-2+deb12u4 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-11850 | LOW2.34 | libgssapi-krb5-2 1.20.1-2+deb12u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2018-5709 | LOW2.34 | libk5crypto3 1.20.1-2+deb12u4 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | LOW2.34 | libk5crypto3 1.20.1-2+deb12u4 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-11850 | LOW2.34 | libk5crypto3 1.20.1-2+deb12u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2018-5709 | LOW2.34 | libkrb5-3 1.20.1-2+deb12u4 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | LOW2.34 | libkrb5-3 1.20.1-2+deb12u4 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-11850 | LOW2.34 | libkrb5-3 1.20.1-2+deb12u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2018-5709 | LOW2.34 | libkrb5support0 1.20.1-2+deb12u4 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | LOW2.34 | libkrb5support0 1.20.1-2+deb12u4 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-11850 | LOW2.34 | libkrb5support0 1.20.1-2+deb12u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | LOW2.34 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | LOW2.34 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | LOW2.34 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | LOW2.34 | mount 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-31486 | LOW2.34 | perl-base 5.36.0-7+deb12u3 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2005-2541 | LOW2.34 | tar 1.34+dfsg-1.2+deb12u1 No fix yet | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2025-14104 | LOW2.34 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | LOW2.34 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2011-3374 | LOW2.22 | apt 2.6.1 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-35189 | LOW2.22 | openssl 3.0.18-1~deb12u2 fixed in 3.0.22-1~deb12u2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-45446 | LOW2.22 | openssl 3.0.18-1~deb12u2 fixed in 3.0.20-1~deb12u2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-75803 | LOW2.22 | openssl 3.0.18-1~deb12u2 fixed in 3.0.22-1~deb12u1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-105712 | LOW2.16 | gpgv 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-27587 | LOW2.12 | libssl3 3.0.18-1~deb12u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-95209 | LOW2 | libgnutls30 3.7.9-2+deb12u6 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-95210 | LOW2 | libgnutls30 3.7.9-2+deb12u6 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2021-32256 | LOW1.99 | binutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-1972 | LOW1.99 | binutils 2.40-2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2024-53589 | LOW1.99 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-57360 | LOW1.99 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-0840 | LOW1.99 | binutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-11081 | LOW1.99 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11082 | LOW1.99 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11083 | LOW1.99 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11412 | LOW1.99 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11413 | LOW1.99 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11414 | LOW1.99 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1147 | LOW1.99 | binutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-11494 | LOW1.99 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11495 | LOW1.99 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1176 | LOW1.99 | binutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1178 | LOW1.99 | binutils 2.40-2 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-1179 | LOW1.99 | binutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1181 | LOW1.99 | binutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1182 | LOW1.99 | binutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-11839 | LOW1.99 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11840 | LOW1.99 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-3198 | LOW1.99 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-5244 | LOW1.99 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW1.99 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-7545 | LOW1.99 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-7546 | LOW1.99 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8224 | LOW1.99 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-32256 | LOW1.99 | binutils-common 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-1972 | LOW1.99 | binutils-common 2.40-2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2024-53589 | LOW1.99 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-57360 | LOW1.99 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-0840 | LOW1.99 | binutils-common 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-11081 | LOW1.99 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11082 | LOW1.99 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11083 | LOW1.99 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11412 | LOW1.99 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11413 | LOW1.99 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11414 | LOW1.99 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1147 | LOW1.99 | binutils-common 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-11494 | LOW1.99 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11495 | LOW1.99 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1176 | LOW1.99 | binutils-common 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1178 | LOW1.99 | binutils-common 2.40-2 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-1179 | LOW1.99 | binutils-common 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1181 | LOW1.99 | binutils-common 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1182 | LOW1.99 | binutils-common 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-11839 | LOW1.99 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11840 | LOW1.99 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-3198 | LOW1.99 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-5244 | LOW1.99 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW1.99 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-7545 | LOW1.99 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-7546 | LOW1.99 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8224 | LOW1.99 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-32256 | LOW1.99 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-1972 | LOW1.99 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2024-53589 | LOW1.99 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-57360 | LOW1.99 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-0840 | LOW1.99 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-11081 | LOW1.99 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11082 | LOW1.99 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11083 | LOW1.99 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11412 | LOW1.99 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11413 | LOW1.99 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11414 | LOW1.99 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1147 | LOW1.99 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-11494 | LOW1.99 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11495 | LOW1.99 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1176 | LOW1.99 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1178 | LOW1.99 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-1179 | LOW1.99 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1181 | LOW1.99 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1182 | LOW1.99 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-11839 | LOW1.99 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11840 | LOW1.99 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-3198 | LOW1.99 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-5244 | LOW1.99 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW1.99 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-7545 | LOW1.99 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-7546 | LOW1.99 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8224 | LOW1.99 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW1.99 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2016-2781 | LOW1.99 | coreutils 9.1-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2017-18018 | LOW1.99 | coreutils 9.1-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-5278 | LOW1.99 | coreutils 9.1-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW1.99 | cpp-12 12.2.0-14+deb12u1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | LOW1.99 | gcc-12 12.2.0-14+deb12u1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | LOW1.99 | gcc-12-base 12.2.0-14+deb12u1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | LOW1.99 | libasan8 12.2.0-14+deb12u1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | LOW1.99 | libatomic1 12.2.0-14+deb12u1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | LOW1.99 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | LOW1.99 | libcc1-0 12.2.0-14+deb12u1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | LOW1.99 | libgcc-12-dev 12.2.0-14+deb12u1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | LOW1.99 | libgcc-s1 12.2.0-14+deb12u1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | LOW1.99 | libgomp1 12.2.0-14+deb12u1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | LOW1.99 | libgssapi-krb5-2 1.20.1-2+deb12u4 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | LOW1.99 | libitm1 12.2.0-14+deb12u1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | LOW1.99 | libk5crypto3 1.20.1-2+deb12u4 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | LOW1.99 | libkrb5-3 1.20.1-2+deb12u4 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | LOW1.99 | libkrb5support0 1.20.1-2+deb12u4 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | LOW1.99 | liblsan0 12.2.0-14+deb12u1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | LOW1.99 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | LOW1.99 | libquadmath0 12.2.0-14+deb12u1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | LOW1.99 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | LOW1.99 | libstdc++6 12.2.0-14+deb12u1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | LOW1.99 | libtsan2 12.2.0-14+deb12u1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | LOW1.99 | libubsan1 12.2.0-14+deb12u1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | LOW1.99 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2007-5686 | LOW1.99 | login 1:4.13+dfsg1-1+deb12u2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW1.99 | mount 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2007-5686 | LOW1.99 | passwd 1:4.13+dfsg1-1+deb12u2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW1.99 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | LOW1.99 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-66861 | LOW1.98 | binutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66862 | LOW1.98 | binutils 2.40-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-66863 | LOW1.98 | binutils 2.40-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.98 | binutils 2.40-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.98 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.98 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.98 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-91781 | LOW1.98 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66861 | LOW1.98 | binutils-common 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66862 | LOW1.98 | binutils-common 2.40-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-66863 | LOW1.98 | binutils-common 2.40-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.98 | binutils-common 2.40-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.98 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.98 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.98 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-91781 | LOW1.98 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66861 | LOW1.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66862 | LOW1.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-66863 | LOW1.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-91781 | LOW1.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils-common 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2024-56433 | LOW1.84 | login 1:4.13+dfsg1-1+deb12u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-56433 | LOW1.84 | passwd 1:4.13+dfsg1-1+deb12u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW1.74 | gpgv 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-8225 | LOW1.68 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-8225 | LOW1.68 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-8225 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpgv 2.2.40-1.1+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-6141 | LOW1.68 | libtinfo6 6.4-4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6141 | LOW1.68 | ncurses-base 6.4-4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6141 | LOW1.68 | ncurses-bin 6.4-4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2011-4116 | LOW1.68 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW1.68 | binutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.68 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.68 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69644 | LOW1.68 | binutils-common 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.68 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.68 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69644 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1148 | LOW1.58 | binutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1149 | LOW1.58 | binutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1150 | LOW1.58 | binutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1151 | LOW1.58 | binutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1180 | LOW1.58 | binutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1148 | LOW1.58 | binutils-common 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1149 | LOW1.58 | binutils-common 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1150 | LOW1.58 | binutils-common 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1151 | LOW1.58 | binutils-common 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1180 | LOW1.58 | binutils-common 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1148 | LOW1.58 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1149 | LOW1.58 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1150 | LOW1.58 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1151 | LOW1.58 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1180 | LOW1.58 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| TEMP-0841856-B18BAF | LOW1.5 | bash 5.2.15-2+b10 No fix yet | — | Post-Exploit |
| TEMP-0628843-DBAD28 | LOW1.5 | login 1:4.13+dfsg1-1+deb12u2 No fix yet | — | Post-Exploit |
| TEMP-0628843-DBAD28 | LOW1.5 | passwd 1:4.13+dfsg1-1+deb12u2 No fix yet | — | Post-Exploit |
| TEMP-0517018-A83CE6 | LOW1.5 | sysvinit-utils 3.06-4 No fix yet | — | Post-Exploit |
| TEMP-0290435-0B57B5 | LOW1.5 | tar 1.34+dfsg-1.2+deb12u1 No fix yet | — | Post-Exploit |
| CVE-2025-6297 | LOW1.27 | dpkg 1.21.22 fixed in 1.21.23 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-27587 | LOW1.27 | openssl 3.0.18-1~deb12u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-68809 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68457 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-90037 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-93221 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-98959 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-43037 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2023-7356 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-23395 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-52924 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-64268 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-64562 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68156 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-68159 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-68480 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72083 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72130 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72319 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-72323 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-74476 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74516 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74588 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74597 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74669 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74705 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74744 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74752 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89656 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89674 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89676 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-90036 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-98716 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99999 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-89482 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89495 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-64018 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74580 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80725 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-10263 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63797 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98769 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74469 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2026-80586 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80844 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31788 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98466 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89697 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-90307 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68315 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43112 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43114 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68376 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72129 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72318 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89526 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89631 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89653 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-90011 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-93787 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64364 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74509 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89524 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89633 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43133 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2013-7445 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 2.8% Low-Moderate Risk | Not Applicable |
| CVE-2019-19449 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2019-19814 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 3.3% Low-Moderate Risk | Not Applicable |
| CVE-2021-3847 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-52452 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52624 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-52751 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53218 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53510 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54125 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-21803 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-26836 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26913 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26914 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26944 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35887 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38570 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-38630 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41045 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42118 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44941 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44942 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44951 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46729 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46811 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46813 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-47691 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50029 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-50217 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50226 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50282 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53068 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53168 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53179 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-53218 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56538 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-56775 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57900 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-21863 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-21927 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-21967 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-21969 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23133 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37750 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-37777 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-37861 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37952 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-37957 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38069 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38117 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38182 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38206 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38248 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-38250 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38369 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38582 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38584 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38585 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38595 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38627 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38704 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38722 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38734 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-39797 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39810 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39859 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39863 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39952 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71068 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-71073 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71152 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-100072 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23171 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23208 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23226 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-23227 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23231 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-23245 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23281 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23319 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23343 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23359 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23361 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23378 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23422 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23428 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-23447 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23448 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31399 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31402 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-31431 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 98.1% Actively Exploited | Not Applicable |
| CVE-2026-31452 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31455 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31485 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31488 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31489 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31493 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31500 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31527 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31532 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31566 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31576 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31578 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31580 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31581 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31583 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31627 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31678 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31686 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31696 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31702 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31709 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31715 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31720 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31729 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31747 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31748 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31759 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31787 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43015 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43020 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43027 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43049 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43128 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43150 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43196 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43205 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43206 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43250 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43284 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-3 | 94.2% Actively Exploited | Not Applicable |
| CVE-2026-43328 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43329 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43378 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43426 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43458 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43499 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-43500 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-3 | 94.1% Actively Exploited | Not Applicable |
| CVE-2026-45839 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45866 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45867 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45879 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45885 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45891 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45902 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45914 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45916 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45920 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45936 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45946 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45984 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45996 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46004 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46047 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46068 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46069 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46075 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46122 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46136 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46163 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46174 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.174-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46180 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46189 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46219 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46234 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46241 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46243 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.174-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46267 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46285 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46294 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46300 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.174-1 | 10.2% High Exploitation Risk | Not Applicable |
| CVE-2026-46301 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46323 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46333 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.172-1 | 4.3% Low-Moderate Risk | Not Applicable |
| CVE-2026-52912 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52923 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52929 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-52933 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52943 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-52962 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52969 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52992 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53004 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53059 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53089 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53112 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53115 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53117 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53118 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53120 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53129 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53130 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53136 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53137 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53143 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53148 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53156 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53157 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.177-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53195 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53262 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53272 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53294 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53296 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53359 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.177-1 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2026-53361 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53362 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.177-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-53366 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.177-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63794 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.177-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63829 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64001 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64034 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64085 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64103 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64225 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64242 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64246 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.177-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64249 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.177-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64270 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64271 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64272 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64273 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64274 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64305 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64329 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64330 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64340 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64341 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64342 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64343 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64344 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64346 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64348 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64352 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64362 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64363 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64365 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64381 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64424 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64446 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64530 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-64531 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64552 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64556 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64564 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2026-64565 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64582 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64600 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68108 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68138 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68143 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68398 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72042 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72052 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72061 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72098 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72255 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72298 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72339 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-74480 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-74518 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74581 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74582 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74583 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74746 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80521 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80714 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80951 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-81000 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89465 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89508 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89617 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89638 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89725 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89736 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89761 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89970 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-89972 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-93288 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93817 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98116 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98260 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98524 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98715 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98741 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46274 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74720 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80536 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80590 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-68470 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40025 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40137 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40333 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31432 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31433 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-31476 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43185 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-43501 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-46006 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46195 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-52911 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-53198 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53266 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-53399 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-64138 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64218 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64389 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64392 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64393 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64394 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64395 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64396 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64398 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64399 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64400 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-64534 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64580 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68136 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68199 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-72251 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-74345 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74394 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89788 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89803 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89922 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89980 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90048 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-93792 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97417 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-98171 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-98417 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98490 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-98532 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-98548 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-98550 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-98573 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98614 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98621 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98725 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98853 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98857 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98889 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98895 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98899 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98911 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98944 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98945 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98964 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-98968 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-98980 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99006 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99012 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99032 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99053 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99054 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99056 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99059 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-99081 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31669 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43110 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43186 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-43190 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53071 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74586 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74695 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80609 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89650 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89702 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43117 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74631 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98805 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40170 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89783 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-31607 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43038 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46099 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64563 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68121 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68294 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68426 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-72243 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53781 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39981 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23243 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31786 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43078 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43248 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63974 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-68278 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72099 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74283 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80863 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93262 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93813 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97415 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97505 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74556 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89610 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-26669 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41935 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53147 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-57982 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-21985 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22039 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2025-22104 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38081 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38204 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38616 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38636 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39744 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39901 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23204 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23315 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23318 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23327 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23388 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23397 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31568 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31778 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43040 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43052 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43141 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43241 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43281 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43380 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43386 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43427 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43449 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43450 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43453 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45893 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45943 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45957 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45994 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46022 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46033 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46064 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46130 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46191 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46293 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52968 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53138 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.177-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53149 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53179 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53255 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53303 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53309 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53330 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63833 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.177-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64014 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64121 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64237 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68409 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89481 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89846 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-14040 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-25743 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36013 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-40064 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40358 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68183 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68324 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23455 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2026-31613 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31685 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43042 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43051 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43126 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43414 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-46053 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46056 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46120 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46135 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46150 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46209 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46259 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52989 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-63806 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64039 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64078 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64153 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64458 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64487 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64549 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64572 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68099 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68155 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-68188 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68198 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-68373 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-72049 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-72084 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-74510 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89596 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89671 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89779 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-93812 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97422 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97425 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97493 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97494 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97495 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97497 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2021-3864 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2023-52586 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42162 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37776 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40354 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71221 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23191 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23454 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31419 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43050 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43125 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43198 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43494 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43503 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.174-1 | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-45972 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46054 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46116 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46181 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46227 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52991 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52993 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53000 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53002 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53006 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53091 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53264 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53329 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53356 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53374 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53398 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.177-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63795 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.177-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-63824 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.177-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63830 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.177-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-63831 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.177-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63875 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63884 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63886 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-63887 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-63888 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-63899 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63917 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63921 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63922 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-63924 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-63956 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63962 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63993 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63994 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64002 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64007 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64009 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64017 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64026 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64113 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64137 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64191 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.177-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64219 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64221 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64303 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-64304 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64434 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64560 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68123 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-68140 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-68144 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68160 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-68162 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68202 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68236 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68335 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68432 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68476 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72123 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72449 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74269 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-74310 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74359 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74488 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74569 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74615 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74616 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74630 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74662 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74743 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80792 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80824 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80837 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80840 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80841 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80842 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80848 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80852 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80921 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-81003 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89479 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89487 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89488 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89530 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89545 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89563 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89564 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89569 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89607 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89652 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89659 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89663 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89669 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89675 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89708 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89713 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89777 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89811 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89894 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89932 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90049 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90111 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90206 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90227 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90315 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98222 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98320 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98323 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-98364 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98378 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53762 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53216 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57984 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21739 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40135 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-40158 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-40168 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-23050 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23270 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23392 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31408 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31508 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31586 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31656 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31663 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43023 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43116 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43158 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43226 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43233 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43303 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43304 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-43334 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43339 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43341 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43370 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43493 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-45852 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45856 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45859 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-45860 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-45894 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45942 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45970 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46015 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46043 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46052 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46090 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46119 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46123 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46133 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-46149 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46173 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46185 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46199 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46204 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46230 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46251 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46266 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46275 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46306 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46319 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46324 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46330 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52917 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52918 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52920 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-52935 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52942 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52947 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52956 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-52957 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-52986 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-52998 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-53005 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53009 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53011 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53016 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53049 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53053 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53062 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53072 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53075 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53131 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53132 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53133 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53182 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53185 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53189 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53209 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53212 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53223 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53224 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53228 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-53230 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53239 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53242 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53246 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53253 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53254 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53256 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53268 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53270 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53275 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53354 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53355 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53357 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53381 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.177-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53384 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.177-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53388 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.177-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53391 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.177-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53392 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53397 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.177-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63800 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.177-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-63801 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.177-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63807 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.177-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63808 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.177-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63823 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.177-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63826 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63889 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-63891 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63898 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63901 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63912 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-63913 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 1.0% Theoretical Threat | Not Applicable |
| CVE-2026-63914 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63916 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-63919 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-63920 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63925 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63928 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63940 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63945 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63946 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63947 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63957 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63958 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63971 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63975 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63984 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63992 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64000 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64011 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64015 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64025 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64032 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64047 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64048 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64098 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64102 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64109 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64114 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64115 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64160 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64189 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64266 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64280 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64298 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64312 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64319 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64320 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-64323 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64355 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64372 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64375 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64378 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64379 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64380 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64401 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64422 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64438 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64448 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64455 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64456 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64470 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64471 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64475 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64481 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64527 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64539 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64543 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64548 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64551 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64554 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64557 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64561 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64573 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64577 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-68086 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68093 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68100 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68117 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68118 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68125 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-68131 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68142 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68147 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68148 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68154 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-68157 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-68158 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-68161 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-68169 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68181 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68253 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68273 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68289 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68293 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68300 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-68315 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68320 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68323 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68325 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68329 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68338 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68343 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68349 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68351 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68363 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68365 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68368 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68377 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68388 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68391 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68397 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-68401 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68402 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-68404 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68427 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68448 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68451 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68452 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68453 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68479 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72020 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72021 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72045 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72051 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72053 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72057 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72065 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72066 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72069 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72102 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72125 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72126 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72135 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72157 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-72218 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72242 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72252 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72253 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72261 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72262 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72284 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72288 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72289 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72301 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72310 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72320 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-72322 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72338 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72351 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72371 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72389 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72398 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72405 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72419 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72422 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72469 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-72473 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72492 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72502 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-74271 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74287 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-74289 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74305 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74378 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74390 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74391 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74405 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74436 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74443 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74446 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74492 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74493 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74496 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74498 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74499 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74506 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74537 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74557 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74563 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74575 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74587 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74598 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74608 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74609 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74611 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-74612 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74621 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74637 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74641 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74656 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74684 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74688 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74724 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74737 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-80552 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80553 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80558 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80561 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80584 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80613 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80663 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80668 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-80681 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80710 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80716 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80718 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80722 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80864 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80914 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80971 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80976 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-80977 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80989 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-81002 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89444 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89476 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89477 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89478 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89480 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89485 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89528 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89532 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89533 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89537 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89542 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89548 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89550 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89551 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89555 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89559 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89560 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89580 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89583 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89606 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89609 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89625 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89636 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89637 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89643 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89654 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89662 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89672 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89680 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89685 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89693 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89694 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89704 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89712 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89729 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89746 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90071 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90093 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90099 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90102 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-90104 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-90110 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-90151 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-90161 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90207 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90230 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-90237 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90284 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90292 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90294 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-90343 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90347 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90392 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90398 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-90413 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-90435 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-92508 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92511 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-92512 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93054 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93095 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93105 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93154 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93283 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93800 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97427 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97476 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97496 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97524 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-97555 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-97561 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97563 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97564 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97573 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-97594 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97611 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97926 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97931 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97933 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97940 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97954 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97990 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97991 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98033 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98034 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98041 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98066 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98068 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98069 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-98070 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-98108 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98130 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-98173 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98175 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98186 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98197 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98204 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98205 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98213 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98221 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98236 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98238 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98239 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-98241 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98246 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98247 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98249 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98251 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98252 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98254 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98262 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98266 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98276 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98282 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98283 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98287 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98290 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98295 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98299 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98306 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98312 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98314 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98330 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98331 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98339 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98341 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98343 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98347 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98357 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-98358 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98365 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-98367 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98368 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98370 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98373 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98374 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98375 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98379 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98380 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98403 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98426 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98428 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98429 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98606 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98657 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98733 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98754 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98176 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98362 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46125 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53196 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74697 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90203 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90414 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-98499 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-98612 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98687 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46331 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2020-36694 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-21264 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-53095 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-57795 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21714 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64508 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68284 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89579 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98589 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98590 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98808 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64296 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64322 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64324 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93125 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21759 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 7.8% Low-Moderate Risk | Not Applicable |
| CVE-2026-45991 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53267 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64478 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89640 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-90255 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-6240 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2024-36968 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31588 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43239 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53176 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-64535 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64550 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-72382 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-80819 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80901 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89511 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89538 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89541 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89665 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89696 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-89707 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89973 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-98167 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98439 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98449 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98452 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98454 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98457 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98479 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-98482 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98489 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98526 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98578 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98582 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98597 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98602 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98704 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98705 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98794 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98803 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98829 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40074 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-23383 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23450 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-23456 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31502 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31516 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52910 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53033 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53036 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53078 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53090 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63809 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.177-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64276 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64277 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68399 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-90333 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-3397 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40307 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31504 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64483 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89965 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40146 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23253 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80788 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89648 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89848 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-98185 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98481 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98575 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98634 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98763 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98828 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98836 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40071 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40355 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68342 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68736 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31449 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31464 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31505 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31570 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31700 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31708 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43134 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68350 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72054 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72055 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72136 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74365 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74515 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80952 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89649 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89786 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89858 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89959 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90054 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90068 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98760 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98810 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98839 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89778 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-31649 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64507 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40242 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68320 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-72399 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72436 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-74474 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74624 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74692 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89709 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-98271 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98432 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-98485 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98491 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98570 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98586 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98792 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98852 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53390 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.177-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-53706 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54107 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54141 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23239 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23240 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-23271 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23317 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31392 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31414 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-31426 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43279 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46065 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46113 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89448 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-49569 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-46024 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80836 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89995 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98464 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98714 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98863 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40347 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-0597 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-23005 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31082 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-37454 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-4133 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52590 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52591 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52625 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52629 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52648 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52671 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52676 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52761 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52770 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52797 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52888 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52920 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-53149 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53228 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53231 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53261 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53292 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53336 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53353 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53367 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53394 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53429 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53460 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53491 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-53523 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53529 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53538 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53545 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53574 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53627 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53846 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53989 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53999 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54013 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54271 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54280 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-6039 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-2193 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2024-25740 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26670 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26677 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26691 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26740 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26756 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26799 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26841 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26866 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26876 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26902 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26947 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26948 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26953 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-26962 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27010 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27011 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27012 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27041 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27057 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27062 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27079 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35784 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35794 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35799 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35808 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35860 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35904 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35924 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35931 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35942 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35945 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35946 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35951 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35961 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36911 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-36922 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-36951 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38557 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38564 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38594 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38608 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38620 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38622 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38625 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-40965 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-40969 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-40975 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40998 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40999 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-41008 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41023 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-41031 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41082 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42128 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42139 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42239 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42241 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42243 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42279 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42317 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-43819 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-43824 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-43850 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43872 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-43899 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43901 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43913 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44963 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-45015 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46678 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46681 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46698 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46727 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46728 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46730 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46754 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46760 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46765 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46775 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46776 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46806 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46808 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46834 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46860 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47141 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47658 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-47661 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-47662 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47664 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47703 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47736 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47752 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47794 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-47809 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49568 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-49893 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49901 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49906 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49908 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49910 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49914 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49916 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49918 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49919 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49920 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49921 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49922 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49923 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49926 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49940 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49945 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49970 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49988 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-50009 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50017 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50028 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50111 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50166 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50285 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-50289 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50298 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-52559 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-52560 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53051 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53056 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53079 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53085 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53089 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53090 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-53091 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53094 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-53114 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53134 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53187 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53195 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53219 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53221 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53224 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53687 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-54683 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56544 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-56565 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56566 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56583 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56588 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56591 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-56592 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56611 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56641 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-56647 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-3 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56657 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56692 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56712 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-56719 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-56742 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-57804 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-57809 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57872 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57888 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57975 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-57976 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-57999 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-58006 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-58012 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-58053 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-58089 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58094 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58095 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58096 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-58097 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58098 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58100 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58237 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58241 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21634 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21635 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-21649 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21656 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21658 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21673 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-21676 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-21682 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21693 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21696 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-21723 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-21729 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21768 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-21801 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-21831 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21836 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-21870 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-21872 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21885 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-21888 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21894 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21907 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21949 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21955 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-21961 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-21972 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-21976 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-22028 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22037 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 69.5% Actively Exploited | Not Applicable |
| CVE-2025-22043 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-22048 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22053 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22057 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22070 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22103 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22105 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22109 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-22113 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22125 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22127 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23129 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23130 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23131 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.177-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23132 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-37747 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37800 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37802 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-37806 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37807 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37833 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37834 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37842 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37853 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37856 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37860 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37864 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37880 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37893 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37945 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37956 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-37977 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37980 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38006 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38014 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38029 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38038 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38039 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38041 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38042 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38045 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38059 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38064 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-38080 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38096 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38105 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38127 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38132 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38140 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38162 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38192 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38195 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38203 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38207 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38237 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38244 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-38246 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-38261 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38264 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-38272 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38283 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38303 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38311 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38333 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38359 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38426 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38429 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-38436 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38438 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38449 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38507 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38531 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38544 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38590 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-38597 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38615 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38626 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38659 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38692 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38705 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38709 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38710 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38716 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39677 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39705 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39707 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39720 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-39732 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39746 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39747 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39748 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39762 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39764 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39767 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39779 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39789 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39829 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39833 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39850 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39851 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-39886 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39910 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39925 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39932 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-39933 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-39940 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39947 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39989 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40005 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40075 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-40102 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40160 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40325 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40328 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-40339 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68188 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68209 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68236 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68265 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68304 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68379 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68823 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71109 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71129 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71138 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71160 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71161 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-71184 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71188 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71202 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71227 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71265 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71266 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71267 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71269 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71272 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71273 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71285 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71287 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71288 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71289 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-71291 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71292 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-71295 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71297 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71304 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71305 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71313 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71315 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-100070 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-100071 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-100075 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-100076 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-100077 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-100078 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22996 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23000 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23066 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23088 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23100 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23113 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23137 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23138 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23141 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23154 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23157 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23213 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23214 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23242 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-23247 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23255 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23265 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23272 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.177-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23273 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23274 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23276 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23277 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23278 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.177-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23279 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23284 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23286 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23287 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23289 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23290 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23291 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23292 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23293 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23296 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23298 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23300 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23303 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23304 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23306 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23307 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23310 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23312 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23321 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23324 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23330 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23335 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23336 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23339 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23340 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23346 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23351 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23352 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23356 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23357 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23362 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23365 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23367 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23368 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23370 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23371 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23374 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23379 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23381 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23382 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23389 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23391 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23396 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23398 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23399 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23401 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23414 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-23419 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23420 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23426 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23434 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23438 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23439 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23442 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23444 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23446 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23449 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23460 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23462 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-23465 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23468 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23472 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23474 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23475 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31391 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31400 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31403 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31407 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31410 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31411 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31412 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31415 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31416 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31418 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31420 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31421 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31422 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31423 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31424 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31425 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31427 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31428 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31434 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31441 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31446 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31447 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31448 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31450 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31451 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.177-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31453 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31454 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31458 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31462 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31467 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31469 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31473 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31480 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31483 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31487 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31492 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31495 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31496 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31497 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31498 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31503 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31507 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31509 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31510 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31512 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31515 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31518 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31519 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31520 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31521 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31522 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31524 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31531 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31533 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31537 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31540 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31545 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31546 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31548 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31549 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31550 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31551 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31552 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31555 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31557 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31560 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31565 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31577 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31579 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31585 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31590 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31592 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31594 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31595 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31596 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31599 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31603 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31605 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31606 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31610 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31615 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31616 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31617 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31618 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31619 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31623 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31624 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31625 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31628 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31630 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31634 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31637 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-31642 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31648 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31651 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31655 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31658 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31660 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31661 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31662 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31664 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31665 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31667 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31670 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31671 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31672 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31673 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31674 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31675 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31676 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31677 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31679 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31680 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31681 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31682 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-31684 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31689 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31692 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31698 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31699 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31701 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31704 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31721 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31722 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31723 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31724 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31725 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31726 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31737 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31738 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31749 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31752 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31754 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31755 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31756 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31758 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31762 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31763 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31767 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31770 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31771 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31773 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31777 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31779 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31781 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43009 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43010 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43013 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43014 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43016 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43017 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43018 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43022 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43024 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43025 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43026 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43028 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43032 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43033 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43035 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43036 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43041 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43043 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43046 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43048 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43054 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43057 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43058 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43060 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43061 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43062 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43064 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43065 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43066 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43068 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43069 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43071 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43072 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43073 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43077 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43079 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43080 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43083 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-43085 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43088 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43089 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43091 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43093 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43094 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43098 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43099 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43101 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43103 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43104 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43105 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43107 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43111 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43113 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43115 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43118 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43119 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43123 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43124 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43129 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43130 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43132 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43135 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43136 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43137 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43139 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43140 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43143 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43145 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43147 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43148 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43149 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43152 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43153 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43156 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43157 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43159 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43161 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43162 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43167 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43168 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43170 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43171 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43172 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43173 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43180 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43182 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43183 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43187 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43200 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43202 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43204 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43209 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43213 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43214 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43215 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43216 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43218 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43219 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43221 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43223 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43225 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43227 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43230 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43231 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43234 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43238 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43240 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43242 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43244 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43246 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43251 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43252 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43255 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43257 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43261 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43262 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43264 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43265 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43266 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43268 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43269 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43270 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43271 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43273 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43277 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43278 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43287 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43288 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43289 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43295 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43296 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43299 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43302 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43308 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43309 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43310 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43312 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43313 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43314 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43315 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43316 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43317 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43318 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43327 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43333 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43338 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43340 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43343 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43344 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43350 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43352 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43353 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43355 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43357 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43359 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43360 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43361 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43362 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43363 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43365 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43366 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43381 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43382 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43387 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43405 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-43406 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-43407 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-43409 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43411 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43412 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43413 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43416 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43419 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43421 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43424 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43425 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43428 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43429 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43432 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43436 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43437 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43441 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-43443 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43445 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43451 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43452 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43455 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43456 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43457 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43459 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43466 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43468 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43469 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43472 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43473 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43475 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43480 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43483 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43484 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43491 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43492 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43496 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43502 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-45834 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45835 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45836 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45838 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45840 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45841 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45842 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45843 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-45844 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45846 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45847 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45848 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45849 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45850 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45855 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45857 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45858 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45862 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45864 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45865 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45868 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45869 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45870 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45871 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45872 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45873 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45875 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45877 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45881 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45883 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45886 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45890 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45892 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45897 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45899 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45901 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45904 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45911 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45912 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45915 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45917 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45919 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45923 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45924 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45930 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45934 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45940 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45941 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45944 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45948 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45954 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45960 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45961 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45962 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45963 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45964 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45965 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45968 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45969 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45974 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45978 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45981 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45982 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45983 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45985 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45986 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45987 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45988 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-45993 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45997 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45999 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46000 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46002 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46003 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46005 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46009 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46012 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46014 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46018 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46019 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46021 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46023 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46026 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46027 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46028 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46032 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46037 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46038 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46040 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46044 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46046 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46049 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46050 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46051 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46059 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46070 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46071 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46072 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46077 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46078 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46079 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46080 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46082 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46083 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46086 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46088 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46091 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46092 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46098 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46101 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46103 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46107 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46108 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46109 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46111 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46127 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46128 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46132 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46137 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46143 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46146 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46147 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46148 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46151 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46153 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46156 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46157 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46158 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46160 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46161 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46165 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46167 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46168 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46169 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46170 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46172 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46179 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46184 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46186 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46190 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46193 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46196 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46197 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46200 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46214 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46220 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46225 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46226 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46229 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46231 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46233 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46235 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46236 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46245 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46247 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46249 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46252 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.177-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46253 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46254 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46262 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46273 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46276 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46280 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46282 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46291 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46292 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46296 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46302 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46303 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46304 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46307 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46312 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46314 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46321 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46322 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52909 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52913 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52915 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52916 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52921 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52925 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52926 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52927 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52928 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.177-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52930 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52936 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52937 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52939 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52941 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52944 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52946 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-52948 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52954 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-52958 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-52961 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52963 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52967 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52970 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52972 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52975 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52977 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52982 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-52984 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52985 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52988 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52990 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52995 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52999 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-53001 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53003 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-53012 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53015 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53017 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53018 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53021 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53022 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53023 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53027 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53034 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53035 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53037 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53039 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53047 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53048 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53050 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53052 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53056 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53060 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53061 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53063 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53064 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53065 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53066 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53069 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53070 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53073 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53074 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53076 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53077 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53080 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53082 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53083 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53086 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53093 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53096 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53102 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53106 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53107 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53111 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53122 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53128 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53134 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53135 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53139 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.177-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53146 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53147 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53150 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53158 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.177-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53159 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53163 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.177-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53167 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.177-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53168 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53177 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53181 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53183 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53184 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53199 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53207 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53208 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53213 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53218 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53219 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53220 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53221 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-53225 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-53226 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53227 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53232 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53236 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53237 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53238 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53245 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53249 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53252 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53258 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53263 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53265 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53269 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53274 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53279 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53285 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53287 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53289 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53291 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53292 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53295 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53297 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53304 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53306 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53313 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53314 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53317 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53320 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53325 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.177-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53327 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.177-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53331 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53332 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53337 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53339 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53343 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53345 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53349 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53350 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53353 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53358 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53375 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53376 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53377 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53379 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53382 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.177-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53385 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.177-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53393 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53400 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53402 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53403 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.177-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63798 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.177-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63803 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.177-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63822 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.177-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63845 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63846 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63847 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63848 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63853 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63854 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63856 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63858 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63860 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63861 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63862 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63865 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63867 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63868 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63870 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63882 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63890 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63892 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63893 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-63897 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63900 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63902 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63903 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63904 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63906 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63926 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63927 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63942 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63948 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63961 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63963 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63968 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-63969 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63973 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63976 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-63983 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63985 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63990 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63991 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63999 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64004 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64005 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64006 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64012 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64036 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64046 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64060 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64073 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64076 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64077 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64079 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64083 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64087 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64090 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64094 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64097 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64106 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64112 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64116 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64118 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64123 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64125 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-64126 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64128 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64131 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64133 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64135 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64139 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64144 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64146 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64155 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64163 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64165 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64166 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64168 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64170 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64173 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64174 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64177 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64178 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64179 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64185 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64187 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64190 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64192 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64206 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64210 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64212 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64213 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64214 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64220 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64222 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64231 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64234 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64241 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64243 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64248 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64250 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64252 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.177-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64254 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.177-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64275 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64279 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64294 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64297 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64299 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64301 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64306 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64313 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64315 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64316 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64331 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64332 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64333 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64334 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64335 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64336 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64337 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64338 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64345 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64347 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64350 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64351 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64359 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64360 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64370 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64371 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64374 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64376 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64403 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64406 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64408 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64409 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64411 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64412 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64413 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64417 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64419 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64423 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64425 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64428 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64429 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64436 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64445 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64450 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64452 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64454 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64463 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64472 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64496 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64510 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64524 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64529 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.177-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64540 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64541 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-64542 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64545 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-64546 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64547 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64553 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64567 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64569 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64571 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64576 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64578 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64579 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68085 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68091 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-68096 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68098 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68104 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68106 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68111 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68112 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68127 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68129 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68130 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68135 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68137 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68141 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68146 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68152 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68153 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68180 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68182 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68183 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68184 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68186 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68187 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68189 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68190 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68194 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68195 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68196 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68197 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68204 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68205 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68206 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68207 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68209 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68210 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68212 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68214 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68215 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68222 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68229 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68231 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68233 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68242 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68243 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68244 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68246 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68247 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68248 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68255 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68258 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68259 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68269 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68277 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68279 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68286 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68287 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-68297 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68299 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68309 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68310 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68312 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68322 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68324 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68326 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-68344 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68352 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68353 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-68354 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-68355 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68357 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68360 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68362 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68366 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68367 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68369 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68371 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68395 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68396 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68410 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68411 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68413 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68414 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68417 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68425 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-68428 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68431 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68433 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68435 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68441 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68444 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68445 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68446 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68447 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68449 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68454 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68456 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68459 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68460 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68461 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68466 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68467 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68471 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-68474 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68475 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68477 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-68478 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72012 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-72013 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72014 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72015 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72017 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72019 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72022 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72024 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-72025 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72028 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72029 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-72030 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72033 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-72035 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72036 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72041 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-72043 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72047 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72048 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72058 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72062 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72070 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72073 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72074 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72075 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72076 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72077 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72078 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72079 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72081 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72082 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72085 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72086 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72088 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72096 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72105 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72106 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72107 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72108 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-72109 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72110 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72114 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72115 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-72116 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72119 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72120 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72121 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-72122 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72124 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-72133 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72138 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72144 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72146 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72147 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72148 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-72153 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72156 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72159 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72160 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72161 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72162 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72163 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72164 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72167 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72168 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72170 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72171 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72172 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72177 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72179 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72181 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72182 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72191 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72192 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72193 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72194 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-72195 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72196 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72197 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72198 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72200 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72203 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72213 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72214 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72215 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72226 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-72228 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72229 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72230 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72231 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72232 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72233 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-72234 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72235 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-72236 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72237 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72238 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72241 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72250 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72256 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72264 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72267 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72268 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72269 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72270 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72271 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72282 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72296 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72297 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72302 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72305 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72312 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72324 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72325 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72334 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-72335 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72336 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72337 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72341 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72343 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72349 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72369 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72373 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72374 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72375 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72379 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72380 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-72384 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72390 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72392 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72397 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72400 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72402 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72404 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72406 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72409 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72413 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72414 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72416 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72418 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72420 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72423 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72428 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72433 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72434 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72435 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72438 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-72440 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-72441 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72444 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-72447 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72448 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72450 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72454 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72459 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-72460 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-72464 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72466 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72470 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72472 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72476 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72478 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72479 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72480 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72481 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72483 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72484 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72486 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72487 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72488 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72489 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72491 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72493 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74256 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74257 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74262 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74268 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-74272 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74276 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74278 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74279 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-74280 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-74281 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-74282 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-74288 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74290 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74291 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74292 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74293 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74294 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74296 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74297 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74300 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74302 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74307 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74312 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74313 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74314 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74317 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74320 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74321 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-74329 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74330 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74334 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74337 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74339 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74340 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74341 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74342 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74346 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74347 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74348 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74349 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74350 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-74351 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74356 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74363 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74381 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74386 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74387 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74388 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74389 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74395 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74399 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74402 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74406 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74407 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74410 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74417 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74427 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-74438 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74444 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74445 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74450 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74453 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74454 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74455 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74457 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74458 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74459 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74460 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74461 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74463 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74464 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74465 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74466 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74467 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74468 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74470 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74472 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74473 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74475 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74478 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-74479 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74481 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74482 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74485 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74490 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74494 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74497 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74505 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74507 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74508 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74512 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74519 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74521 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74522 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-74523 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74525 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74527 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74540 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74544 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74548 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74549 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74550 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74551 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74552 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74565 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74566 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74567 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74578 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74584 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.177-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74592 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74595 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74599 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74600 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74603 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74607 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74613 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74620 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74625 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74626 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74628 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74632 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74635 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74638 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74647 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74648 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74649 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74650 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74651 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74657 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74658 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74659 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74666 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74667 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74668 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74671 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74673 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74675 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74679 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74683 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74687 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74689 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74693 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74694 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74696 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74701 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74704 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74713 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74719 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74723 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-74725 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74726 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74729 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74735 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74739 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74740 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74747 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74748 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80526 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80527 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80529 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80539 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80540 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80541 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80547 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80548 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80550 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80551 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80554 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80556 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80557 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80559 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80560 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80562 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80565 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80567 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80568 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80569 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80570 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80572 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80573 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80574 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80576 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80579 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80580 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80583 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80587 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80591 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80594 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80595 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80597 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80598 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80599 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80600 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-80601 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80602 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80604 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80618 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80619 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80620 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80622 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80623 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80626 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80627 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80628 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80629 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80630 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-80631 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80634 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-80635 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80636 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80637 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-80644 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80645 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80646 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-80647 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80649 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80650 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80654 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80660 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80664 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80670 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-80671 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80676 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80677 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80680 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80684 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80686 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80694 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80695 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80698 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80706 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80707 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-80708 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80709 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80717 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-80743 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80752 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80754 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80756 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80771 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80797 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80891 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80902 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80905 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80906 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80907 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80908 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80909 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80916 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80920 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80923 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80925 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80928 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80931 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80932 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80937 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-80938 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80964 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80965 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80966 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80968 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80969 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80972 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80978 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80980 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-80991 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80992 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80999 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-81016 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-81017 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89437 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89441 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89452 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89457 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89461 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89462 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89463 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89464 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89468 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89469 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89470 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89471 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89472 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89474 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89475 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89483 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89489 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89490 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89491 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89492 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89493 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89494 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89496 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89497 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89498 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89504 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89512 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89515 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89520 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89525 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89543 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89544 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89549 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89554 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89557 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89561 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89565 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89567 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89573 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89574 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89575 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89582 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89585 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89587 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89594 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89595 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89597 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89599 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89608 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89611 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89615 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89616 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89621 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89622 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89626 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89628 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89699 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89706 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89711 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89718 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89720 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89722 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89723 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89724 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89726 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89730 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89732 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89733 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89738 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89740 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89742 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89751 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89756 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89757 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89762 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89763 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89780 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89824 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89835 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89837 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89845 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89856 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89863 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89864 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89881 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89884 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89896 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89901 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89912 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89927 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89930 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89933 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89989 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89993 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89996 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90007 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90015 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90020 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90021 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90023 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90056 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90061 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90063 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90073 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90074 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90075 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90076 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90081 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90083 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90087 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90088 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90090 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90091 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90098 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90103 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-90105 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90106 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90107 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90108 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90112 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90114 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90116 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90122 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90124 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90140 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90141 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90143 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90146 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90148 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90149 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-90150 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90152 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90153 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-90154 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90155 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90156 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90157 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90162 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-90166 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90167 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90169 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90174 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90176 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-90179 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90196 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90198 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90199 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90200 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90204 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90205 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90208 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90214 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90218 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90219 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90221 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90222 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90223 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90224 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90225 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90226 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90228 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-90229 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90232 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90245 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90247 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90248 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90249 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90251 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90257 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90259 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90264 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90265 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90273 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90274 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90286 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90287 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90289 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90293 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-90295 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90296 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90297 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90298 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90300 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90301 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-90302 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90308 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90309 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90313 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90314 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90316 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90318 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90319 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90320 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90321 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90322 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90327 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90328 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90334 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90337 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90341 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90345 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90348 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90352 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90353 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-90354 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90357 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-90358 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90361 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90362 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90365 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90368 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90372 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90375 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90378 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90382 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90383 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90388 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90394 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90395 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90403 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-90407 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90410 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90416 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90418 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90419 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90420 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90421 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90431 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90433 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90434 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92476 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92477 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92480 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92481 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92482 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92488 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92496 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92498 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92499 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92501 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92503 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92504 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-92514 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92520 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92521 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92522 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-92525 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93037 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93039 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93040 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93041 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93042 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-93046 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93047 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93048 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93049 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93050 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93051 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93052 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93053 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93055 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93056 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93058 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93061 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93063 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93064 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93067 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93073 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93081 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93091 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93098 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93108 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93109 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93110 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93114 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93118 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93120 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93122 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93128 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93131 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93138 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93141 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93142 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93149 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93150 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93151 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-93152 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93155 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93159 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93160 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93163 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93165 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93167 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93168 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93170 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93174 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93175 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93177 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93178 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93179 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93182 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93183 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93184 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93185 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93188 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93190 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93191 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93192 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93196 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93203 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-93204 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93228 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-93247 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93261 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93264 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93271 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93272 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93278 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93279 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93280 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-93281 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93282 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-93285 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93287 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93782 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93786 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-93789 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93790 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93791 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93793 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93796 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93799 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93802 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93803 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93804 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93805 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93806 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-93807 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93808 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93815 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93816 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93819 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93820 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93821 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93822 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93824 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93826 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93830 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-97407 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97408 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97409 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97411 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97413 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-97418 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97419 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97420 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97421 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97434 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97435 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97437 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97438 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97439 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97442 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-97444 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97448 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97451 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97455 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97456 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97472 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97475 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97478 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97482 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97485 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97486 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97489 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97490 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97499 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97500 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97502 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97506 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97507 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97508 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97512 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97515 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97517 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97518 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97523 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-97529 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97534 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97535 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97536 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-97537 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97539 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97540 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97541 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97554 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97558 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97559 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97562 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-97565 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97567 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97572 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97576 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97581 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97582 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97587 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97596 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97598 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97599 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97600 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97604 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97609 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97612 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97901 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97908 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97909 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97910 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97918 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97920 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97924 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97925 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97929 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97930 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97935 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97939 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97950 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97951 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97952 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97953 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-97957 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97964 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97969 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97970 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97973 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97977 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97978 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97981 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97982 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97987 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97992 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97994 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97995 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97998 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98006 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98008 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98013 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98017 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98019 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98022 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98026 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98027 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98030 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98031 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98043 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98056 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-98063 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98071 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98072 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98080 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98085 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98090 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98091 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98092 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98094 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98095 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98098 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98103 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98104 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98107 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98111 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98113 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98114 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98121 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98123 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98124 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98125 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98126 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98127 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98128 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98129 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98131 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98142 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98157 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98158 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98159 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98160 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98161 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98162 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98164 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98169 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-98170 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98172 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98180 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98187 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98188 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98189 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98190 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98192 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98193 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98194 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98195 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98198 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98199 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98207 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98209 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98210 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98212 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98227 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98248 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98253 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98269 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98272 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98279 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98288 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98292 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98294 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98298 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98302 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98303 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98309 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98311 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98313 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98322 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98327 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98333 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98335 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98340 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98348 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98349 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98351 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98352 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98353 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98355 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98359 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98360 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98369 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98381 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98383 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98407 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98409 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98410 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98413 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98419 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98420 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98423 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98455 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98461 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98483 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98495 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98503 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98511 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98521 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98539 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98541 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98547 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98554 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98556 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98567 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98580 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98610 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98624 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98652 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98660 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98665 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98745 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98751 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98775 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98778 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98797 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98801 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98812 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98820 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98830 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98833 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98837 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98846 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98850 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52653 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-53823 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53857 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54030 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54088 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35843 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39990 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39997 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40057 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40196 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40219 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68206 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-68219 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68334 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68378 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68794 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-68822 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31486 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43030 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43194 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43211 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43253 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46102 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-46178 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46299 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46320 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-52974 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-52981 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53088 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53229 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53284 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53369 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63810 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63855 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63964 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64388 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64430 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64435 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64465 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64476 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64480 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64482 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64486 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64488 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64489 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64512 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64513 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64514 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64537 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64544 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64590 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64593 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68090 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68102 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68115 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68132 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68164 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68165 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68175 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68176 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68216 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68217 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68218 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68226 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68227 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68234 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68238 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68241 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68249 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68250 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68251 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68254 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68288 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68301 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68304 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68313 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68328 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68331 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68333 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68336 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68386 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68403 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68405 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68406 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68407 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68408 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68412 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68418 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68422 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68430 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68434 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68450 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68469 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-72004 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72005 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72007 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72009 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-72010 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72023 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72037 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72038 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72039 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72040 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72056 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72059 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72063 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72067 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72068 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72087 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72097 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72117 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72118 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72142 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72149 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72152 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72155 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72165 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72166 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72216 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72223 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72224 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72225 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72240 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72245 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72254 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72257 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72260 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72265 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72272 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72274 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72275 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72276 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72290 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72307 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72308 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72314 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72315 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72321 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72326 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72347 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72350 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72376 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72391 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72396 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72421 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72424 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72425 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72437 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72439 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72467 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72494 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-74261 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74265 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74284 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74295 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74308 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74318 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74327 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74331 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74338 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74374 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-74376 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74379 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74380 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74382 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74397 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74416 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74424 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74426 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74487 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74495 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74514 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74536 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74543 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74546 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74547 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74553 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74555 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74571 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74577 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74579 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74601 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74622 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74623 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74636 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74653 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74654 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74663 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74664 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74676 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74678 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74680 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74717 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74722 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74733 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74754 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80549 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80593 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80605 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80611 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80616 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80643 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80652 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80653 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80659 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80669 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80679 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80689 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80704 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80715 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80730 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80733 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80739 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80742 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80744 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80784 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80786 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80820 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80828 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80843 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80855 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80856 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80861 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80866 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80870 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80876 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80877 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80884 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80888 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80892 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80912 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80913 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80917 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80918 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80930 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80941 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80948 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80949 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80963 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80967 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80974 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80983 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80987 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80988 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80990 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80996 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89484 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89527 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89531 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89539 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89552 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89562 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89566 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89576 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89586 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89598 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89601 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89604 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89605 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89627 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89644 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89645 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89647 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89710 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89744 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89749 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89752 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89753 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89759 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89765 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89784 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89795 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89796 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89808 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89813 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89816 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89822 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89851 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89855 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89862 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89872 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89876 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89877 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89923 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89924 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89925 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89926 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89944 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89953 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89955 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89958 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89975 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89979 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89982 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90019 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90031 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90034 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90053 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90055 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90058 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90060 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90062 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90066 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90067 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-90070 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90072 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90078 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90084 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90097 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90109 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90119 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90125 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90126 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90138 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90139 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90160 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90182 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90183 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90184 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90186 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90187 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90188 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90190 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90194 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90202 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90209 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90213 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90216 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90250 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90253 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90254 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90267 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90281 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90283 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90285 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90290 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90311 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90330 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90335 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90346 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90360 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90385 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90386 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90389 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90391 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90411 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90415 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92493 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92494 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92523 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92524 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93062 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93072 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93093 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93102 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93103 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93115 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93116 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93129 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93130 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93136 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93140 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93145 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93146 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93158 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93161 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93172 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93186 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93199 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93202 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93206 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93208 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93210 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93213 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93216 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93222 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93226 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93231 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93234 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93242 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93243 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93244 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93256 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93268 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93269 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93274 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93286 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93781 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93785 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93788 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93794 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93795 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93798 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93811 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93814 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93823 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93825 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93828 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93829 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97416 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97424 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97430 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97436 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97440 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97441 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97446 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97477 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97479 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97480 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97481 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97483 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97484 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97487 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97488 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97491 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97492 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97501 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97509 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97510 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97516 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97530 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97556 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97566 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97592 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97597 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97601 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97605 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97613 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97615 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97616 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97619 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97899 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97904 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97905 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97906 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97921 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97922 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97923 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97927 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97948 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97958 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97959 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97963 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97979 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97984 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97985 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97989 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97993 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97997 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98003 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98009 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98010 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98011 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98012 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98021 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98044 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98046 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98055 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98058 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98064 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98067 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98073 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98074 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98079 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98081 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98087 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98148 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98177 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98179 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98182 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98191 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98202 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98203 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98208 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98233 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98234 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98237 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98285 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98289 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98304 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98307 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98308 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98317 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98319 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98321 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98325 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98326 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98328 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98329 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98332 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98334 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98337 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98338 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98344 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98345 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98386 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98387 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98388 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98389 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98393 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98394 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98398 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98399 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98400 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98402 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98404 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98406 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98421 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98422 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98424 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98425 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98427 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89634 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-36881 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40261 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-71225 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23457 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53194 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64391 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64538 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72247 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72348 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-74398 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74401 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-74408 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80603 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-80875 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80890 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89456 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89682 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89684 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89686 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89847 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89860 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89861 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-90041 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-90092 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-97965 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98154 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98156 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98174 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98284 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98300 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98401 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-98471 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98576 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98577 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98698 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98706 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98707 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98720 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98823 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98824 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98827 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98859 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40338 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71193 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23035 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72299 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-74384 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80793 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80830 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80846 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89655 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89892 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90234 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-90235 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-97557 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-97975 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98264 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98501 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98738 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98767 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40054 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40077 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40247 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40289 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40311 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40337 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-68190 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68201 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68322 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71065 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23372 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23393 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31396 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31405 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31477 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31598 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31611 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31622 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31629 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31657 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31659 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31683 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31705 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31706 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31707 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31711 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-31716 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31780 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43075 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43076 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43336 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43373 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43476 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43490 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43495 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43497 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45935 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45958 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46062 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46110 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46112 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46124 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46129 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46164 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46198 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46212 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46218 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46238 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-52914 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-52919 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52931 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-52934 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53040 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53041 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53043 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53046 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-53068 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53160 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53161 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53178 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53186 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53215 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53216 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53217 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53273 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53383 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.177-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-53401 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63796 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.177-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-63805 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63814 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.177-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63815 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63816 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63817 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.177-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63818 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63819 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63834 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.177-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63835 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.177-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63836 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.177-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63895 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63905 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63908 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63915 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-63930 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63931 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63933 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63934 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63949 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63954 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63959 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63960 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63967 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64010 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64033 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64084 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64086 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64088 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64089 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-64091 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64093 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64095 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64096 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64188 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.177-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64269 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-64318 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64361 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64390 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64397 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64432 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64437 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64461 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64462 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64468 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64469 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64484 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64494 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64495 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64497 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64500 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64503 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64504 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64505 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64528 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64532 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64533 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64581 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64584 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64585 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64586 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64587 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64594 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64599 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64602 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64604 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68082 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68083 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68088 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68097 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68185 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68192 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68280 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68302 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68327 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68340 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68359 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68361 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72140 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72306 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72378 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-74564 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74691 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-80555 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80732 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80761 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80763 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80768 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80770 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80772 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80781 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80783 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80789 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80794 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80795 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80796 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80798 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80799 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80800 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80801 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80802 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80803 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80807 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80808 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80809 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80812 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80814 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80823 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80826 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80827 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80831 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80833 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80834 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80847 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80865 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80867 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80879 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80881 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80886 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80904 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80910 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-81007 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89774 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89776 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89781 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89782 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89785 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89787 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89789 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89792 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89793 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89794 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89817 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89818 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89821 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89832 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89833 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89840 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89843 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89849 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89850 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89852 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89865 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89871 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89878 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89880 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89883 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89887 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89888 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89890 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89893 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89895 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89906 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89934 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89936 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89937 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89939 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89945 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89946 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89947 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89948 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89949 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89951 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89952 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89954 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89957 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89964 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89968 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-89969 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89984 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89992 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89997 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89999 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90000 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90016 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90017 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90018 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90025 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90029 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90032 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93214 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93219 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93236 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93238 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93245 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93252 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93783 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93784 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93797 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97445 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97449 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97450 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97452 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97453 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97454 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97568 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98076 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98077 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98088 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98089 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98096 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-98097 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98099 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98257 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-98275 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98436 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63871 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89897 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-90329 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-90379 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-93189 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-97531 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98255 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98549 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-98742 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2019-20794 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-52771 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53447 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2024-24864 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26869 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27408 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36024 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36949 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39508 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42107 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46787 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46870 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-49998 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50135 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53176 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-53178 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-56729 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57857 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-57974 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21651 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21732 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21825 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21892 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22115 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38234 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38524 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-38717 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39726 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39754 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39927 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39961 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40016 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40139 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68239 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68296 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68745 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-71074 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71274 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23004 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23118 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23207 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23302 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.177-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23348 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23394 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23452 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23463 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31389 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31393 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31466 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31523 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31697 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31728 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31751 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43047 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43053 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43163 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43275 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43342 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43383 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43420 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43430 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43439 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43448 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45905 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45949 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46017 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46159 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46187 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52955 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53108 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53352 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64038 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64373 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68084 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72113 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72219 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72329 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72383 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74255 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74264 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74267 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-74377 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74441 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74589 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74594 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74614 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74660 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74672 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74677 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74690 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74700 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74714 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74715 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74730 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80528 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80589 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80678 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80731 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80737 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80762 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80764 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80767 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80785 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80806 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80854 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80880 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80883 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80893 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80944 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80947 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80982 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80994 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-81001 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-81008 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89440 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89510 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89540 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89553 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89719 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89741 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89810 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89823 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89853 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89854 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89899 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89913 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89920 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89929 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89956 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89983 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89998 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90003 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90057 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90128 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90135 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90180 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90185 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90189 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90303 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90325 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90326 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90393 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90417 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92500 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92507 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92509 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92510 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93099 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93100 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93104 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93137 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93176 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93200 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97608 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97949 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97986 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97988 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98014 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98015 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98016 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98023 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98075 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98196 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98217 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98229 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98245 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98301 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98342 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98354 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98430 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98476 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98507 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98508 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98515 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98536 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98537 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98538 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98555 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98559 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98568 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98581 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98598 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98622 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98625 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98656 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98662 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98672 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98681 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98694 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98695 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98708 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98709 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98734 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98735 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98736 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98737 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98749 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98750 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98752 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98753 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98762 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98768 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98772 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98773 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98785 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98786 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98790 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98800 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98826 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98840 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68081 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72316 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80534 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2019-15213 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-74585 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74682 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80829 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89879 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89891 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98025 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98181 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98265 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98711 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2020-14304 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-54263 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42123 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40206 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68768 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74456 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74471 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80757 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80765 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80805 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80832 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90359 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98078 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98273 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98435 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98443 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98460 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98525 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98565 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98569 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98572 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98583 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98620 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98623 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98626 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98631 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98636 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98640 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98644 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98647 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98703 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98722 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98726 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98739 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98764 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98789 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98793 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98795 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98798 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98799 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98807 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98809 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98814 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98819 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98838 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98855 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98856 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98872 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98875 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26661 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26662 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26672 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26757 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26758 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26768 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-23458 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68337 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98101 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98363 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80791 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89666 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90033 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98453 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98701 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98822 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80766 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2019-16089 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-42156 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42158 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72072 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72342 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74604 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80782 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80790 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-81005 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90336 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93117 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97532 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97938 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98286 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98416 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98456 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98488 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98493 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98494 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98506 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98544 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98558 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98588 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98593 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98632 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98663 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98664 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98666 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98669 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98670 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98677 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98696 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98721 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98740 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98748 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98756 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98757 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98765 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98766 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98796 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98815 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98816 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98825 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98834 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98847 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98854 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98862 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98876 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98761 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53851 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98877 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98878 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98879 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98880 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98881 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98882 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98883 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98884 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98885 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98886 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98887 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98888 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98890 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98891 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98892 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98893 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98894 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98896 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98897 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98898 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98900 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98901 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98902 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98903 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98904 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98905 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98906 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98907 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98908 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98909 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98910 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98912 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98913 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98914 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98915 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98916 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98917 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98924 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98925 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98926 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98929 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98930 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98931 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98932 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98933 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98934 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98935 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98936 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98937 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98940 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98942 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98946 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98947 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98950 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98954 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98955 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98956 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98957 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98966 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98967 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98969 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98970 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98971 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98972 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98975 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98977 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98978 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98979 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98981 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98983 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98984 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98985 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98989 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98990 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98992 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98993 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98996 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99002 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99005 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99007 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99008 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99009 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99010 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99015 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99019 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99021 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99022 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99024 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99025 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99026 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99027 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99031 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99033 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99034 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99035 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99036 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99037 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99038 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99039 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99040 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99041 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99043 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99045 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99049 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99052 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99057 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99058 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99061 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99063 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99067 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99070 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99071 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99072 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99074 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-99076 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99077 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-99080 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99082 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99083 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-99086 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99087 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99088 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | — | Not Applicable |
| CVE-2026-99089 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | — | Not Applicable |
| CVE-2026-99090 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | — | Not Applicable |
| CVE-2026-99091 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | — | Not Applicable |
| CVE-2026-99095 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | — | Not Applicable |
| DLA-4792-1 | NONE0 | tzdata 2025b-0+deb12u2 fixed in 2026c-0+deb12u1 | — | Not Applicable |
| DLA-4854-1 | NONE0 | tzdata 2025b-0+deb12u2 fixed in 2026e-0+deb12u1 | — | Not Applicable |
| CVE-2004-0230 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 80.3% Actively Exploited | Not Applicable |
| CVE-2005-3660 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2008-2544 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2008-4609 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 32.1% High Exploitation Risk | Not Applicable |
| CVE-2010-4563 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 2.9% Low-Moderate Risk | Not Applicable |
| CVE-2010-5321 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2011-4915 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2011-4916 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2011-4917 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2012-4542 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2014-9892 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2014-9900 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2016-10723 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2016-8660 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2017-0630 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2017-13693 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2017-13694 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-1121 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 4.1% Low-Moderate Risk | Not Applicable |
| CVE-2018-12928 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-17977 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-12378 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-12379 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-12380 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-12381 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-12382 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-12455 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-12456 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-16229 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-16230 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-16231 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-16232 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2019-16233 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-16234 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-19070 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 2.8% Low-Moderate Risk | Not Applicable |
| CVE-2019-19378 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2020-11725 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-26934 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-3714 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-0400 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2022-1247 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-25265 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2022-2961 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-3238 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-41848 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-44032 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-44033 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-44034 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-4543 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2022-45884 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-45885 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-23039 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-26242 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-31081 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-31085 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-3640 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2023-39191 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-4134 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-0564 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-40918 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64317 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98802 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89987 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2020-35501 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98484 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98732 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89642 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90263 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90401 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92485 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98201 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98377 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2015-2877 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-54227 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-54233 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54322 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50057 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50211 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40268 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40303 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31668 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-98450 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98451 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-98502 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98509 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98514 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98531 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98551 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98579 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98607 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98608 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98629 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98655 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98668 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98679 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98685 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98686 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98700 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98755 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98771 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98777 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98811 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98851 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98873 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80973 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89458 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2019-11191 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-25742 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40003 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40065 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40097 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40136 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40180 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40266 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68755 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68781 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71067 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71198 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23364 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31409 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31417 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31478 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31494 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31536 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31563 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-31587 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31597 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31602 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31612 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31626 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31695 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31712 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31761 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31768 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43011 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-43184 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43203 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43207 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43212 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43232 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43236 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43249 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43256 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43258 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43283 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43291 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43324 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43377 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45956 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46031 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46058 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46175 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46177 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-46205 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46206 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46208 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46250 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46265 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46270 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46328 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52922 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53024 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53025 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53045 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53368 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63825 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-63827 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.177-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63828 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.177-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64055 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64056 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-64082 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64108 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64420 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64440 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64441 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64442 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64443 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64444 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64449 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64536 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.180-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64583 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68124 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-68151 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68203 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68213 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68223 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68303 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68370 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.187-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80738 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80747 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80755 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80851 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89797 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89799 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89834 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89838 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89859 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89870 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89921 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89938 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89960 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89962 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89988 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90002 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90013 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90044 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90045 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93205 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93235 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93239 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93251 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93260 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93810 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98102 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98433 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98498 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98527 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98609 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98682 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98683 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98684 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| TEMP-0000000-F7A20F | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | — | Not Applicable |
| CVE-2026-98516 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98535 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98553 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98628 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98643 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98671 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98710 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98784 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98831 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98874 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2007-3719 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42155 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98486 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98505 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98519 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98529 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98594 | NONE0 | linux-libc-dev 6.1.164-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98697 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98779 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98780 | NONE0 | linux-libc-dev 6.1.164-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
Want to check another image? Run a full scan with the Docker Security Scanner.