Last scanned:
AI verdict failed due to an error.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2024-32002 | MEDIUM6.21 | git 1:2.25.1-1ubuntu3.11 fixed in 1:2.25.1-1ubuntu3.13 | 25.3% High Exploitation Risk | Post-Exploit |
| CVE-2024-32004 | MEDIUM4.68 | git 1:2.25.1-1ubuntu3.11 fixed in 1:2.25.1-1ubuntu3.12 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2024-52006 | MEDIUM4.5 | git 1:2.25.1-1ubuntu3.11 fixed in 1:2.25.1-1ubuntu3.14 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2024-32465 | LOW3.98 | git 1:2.25.1-1ubuntu3.11 fixed in 1:2.25.1-1ubuntu3.12 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2024-32021 | LOW3.62 | git 1:2.25.1-1ubuntu3.11 fixed in 1:2.25.1-1ubuntu3.12 | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2024-5535 | LOW3.54 | openssl 1.1.1f-1ubuntu2.20 fixed in 1.1.1f-1ubuntu2.23 | 5.6% Low-Moderate Risk | Post-Exploit |
| CVE-2024-4741 | LOW3.36 | openssl 1.1.1f-1ubuntu2.20 fixed in 1.1.1f-1ubuntu2.23 | 2.9% Low-Moderate Risk | Post-Exploit |
| CVE-2024-0727 | LOW3.3 | openssl 1.1.1f-1ubuntu2.20 fixed in 1.1.1f-1ubuntu2.21 | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2023-5678 | LOW3.18 | openssl 1.1.1f-1ubuntu2.20 fixed in 1.1.1f-1ubuntu2.21 | 4.5% Low-Moderate Risk | Post-Exploit |
| CVE-2024-2511 | LOW2.89 | openssl 1.1.1f-1ubuntu2.20 fixed in 1.1.1f-1ubuntu2.23 | 54.0% Actively Exploited | Post-Exploit |
| CVE-2023-4641 | LOW2.8 | passwd 1:4.8.1-1ubuntu5.20.04.4 fixed in 1:4.8.1-1ubuntu5.20.04.5 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-28085 | LOW2.64 | bsdutils 1:2.34-0.1ubuntu9.4 fixed in 2.34-0.1ubuntu9.6 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2024-28085 | LOW2.64 | mount 2.34-0.1ubuntu9.4 fixed in 2.34-0.1ubuntu9.6 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2024-28085 | LOW2.64 | util-linux 2.34-0.1ubuntu9.4 fixed in 2.34-0.1ubuntu9.6 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2024-50349 | LOW2.4 | git 1:2.25.1-1ubuntu3.11 fixed in 1:2.25.1-1ubuntu3.14 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2024-13176 | LOW2.4 | openssl 1.1.1f-1ubuntu2.20 fixed in 1.1.1f-1ubuntu2.24 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2024-9143 | LOW2.22 | openssl 1.1.1f-1ubuntu2.20 fixed in 1.1.1f-1ubuntu2.24 | 5.8% Low-Moderate Risk | Post-Exploit |
| CVE-2024-32020 | LOW1.68 | git 1:2.25.1-1ubuntu3.11 fixed in 1:2.25.1-1ubuntu3.12 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2024-45491 | NONE0 | libexpat1 2.2.9-1ubuntu0.6 fixed in 2.2.9-1ubuntu0.7 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2024-45492 | NONE0 | libexpat1 2.2.9-1ubuntu0.6 fixed in 2.2.9-1ubuntu0.7 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2024-37371 | NONE0 | krb5-locales 1.17-6ubuntu4.4 fixed in 1.17-6ubuntu4.6 | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2024-37371 | NONE0 | libgssapi-krb5-2 1.17-6ubuntu4.4 fixed in 1.17-6ubuntu4.6 | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2024-37371 | NONE0 | libk5crypto3 1.17-6ubuntu4.4 fixed in 1.17-6ubuntu4.6 | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2024-37371 | NONE0 | libkrb5-3 1.17-6ubuntu4.4 fixed in 1.17-6ubuntu4.6 | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2024-37371 | NONE0 | libkrb5support0 1.17-6ubuntu4.4 fixed in 1.17-6ubuntu4.6 | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2024-47685 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2024-32002 | NONE0 | git-man 1:2.25.1-1ubuntu3.11 fixed in 1:2.25.1-1ubuntu3.13 | 25.3% High Exploitation Risk | Not Applicable |
| CVE-2024-3596 | NONE0 | krb5-locales 1.17-6ubuntu4.4 fixed in 1.17-6ubuntu4.8 | 14.9% High Exploitation Risk | Not Applicable |
| CVE-2024-3596 | NONE0 | libgssapi-krb5-2 1.17-6ubuntu4.4 fixed in 1.17-6ubuntu4.8 | 14.9% High Exploitation Risk | Not Applicable |
| CVE-2024-3596 | NONE0 | libk5crypto3 1.17-6ubuntu4.4 fixed in 1.17-6ubuntu4.8 | 14.9% High Exploitation Risk | Not Applicable |
| CVE-2024-3596 | NONE0 | libkrb5-3 1.17-6ubuntu4.4 fixed in 1.17-6ubuntu4.8 | 14.9% High Exploitation Risk | Not Applicable |
| CVE-2024-3596 | NONE0 | libkrb5support0 1.17-6ubuntu4.4 fixed in 1.17-6ubuntu4.8 | 14.9% High Exploitation Risk | Not Applicable |
| CVE-2024-2961 | NONE0 | libc-bin 2.31-0ubuntu9.14 fixed in 2.31-0ubuntu9.15 | 88.3% Actively Exploited | Not Applicable |
| CVE-2024-2961 | NONE0 | libc-dev-bin 2.31-0ubuntu9.14 fixed in 2.31-0ubuntu9.15 | 88.3% Actively Exploited | Not Applicable |
| CVE-2024-2961 | NONE0 | libc6 2.31-0ubuntu9.14 fixed in 2.31-0ubuntu9.15 | 88.3% Actively Exploited | Not Applicable |
| CVE-2024-2961 | NONE0 | libc6-dev 2.31-0ubuntu9.14 fixed in 2.31-0ubuntu9.15 | 88.3% Actively Exploited | Not Applicable |
| CVE-2024-47659 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2023-52434 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-32004 | NONE0 | git-man 1:2.25.1-1ubuntu3.11 fixed in 1:2.25.1-1ubuntu3.12 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2024-32465 | NONE0 | git-man 1:2.25.1-1ubuntu3.11 fixed in 1:2.25.1-1ubuntu3.12 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-52664 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-215.235 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52927 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-215.235 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-0646 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-172.190 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-1086 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-174.193 | 28.1% High Exploitation Risk | Not Applicable |
| CVE-2024-26581 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-177.197 | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2024-26689 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-215.235 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26800 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26928 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-212.232 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27398 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-35864 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-212.232 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36971 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 2.7% Low-Moderate Risk | Not Applicable |
| CVE-2024-38630 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-198.218 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49883 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50264 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-204.224 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-53103 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-205.225 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53104 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 3.3% Low-Moderate Risk | Not Applicable |
| CVE-2024-53171 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-56581 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56595 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-56596 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56598 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56619 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56658 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-212.232 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57850 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57900 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-58055 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21704 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-21715 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21735 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-21772 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21791 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-21858 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47063 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-186.206 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47131 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-190.210 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-48655 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-190.210 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2022-48674 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48733 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-202.222 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48791 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-196.216 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48943 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-202.222 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52436 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-176.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52438 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-176.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52439 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-176.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52444 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-176.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52445 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-176.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52451 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-176.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52457 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-176.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52464 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-176.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52475 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-171.189 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52509 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-171.189 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52510 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-171.189 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52524 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-171.189 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52530 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-182.202 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52531 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52594 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52599 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52600 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-177.197 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52603 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-177.197 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52604 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52612 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-176.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52614 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52637 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52679 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-176.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52691 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-176.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52741 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52752 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52760 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-193.213 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52764 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-173.191 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52796 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-173.191 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52799 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-173.191 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52804 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-173.191 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52818 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-173.191 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52835 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-173.191 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52836 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-173.191 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52840 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-173.191 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52864 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-173.191 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52867 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-173.191 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52868 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-173.191 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26589 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-177.197 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26598 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26622 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-182.202 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26625 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26704 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-181.201 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26736 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-186.206 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26748 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-186.206 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26749 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-186.206 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26754 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-186.206 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26793 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-186.206 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26882 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-26883 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26884 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26885 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26898 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26907 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-190.210 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26934 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26955 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26956 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26957 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26965 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26981 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26996 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27000 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27008 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27024 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27043 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27065 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27075 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27395 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27396 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35789 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-35847 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35855 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35886 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-36015 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-36886 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2024-36904 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-36934 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-36940 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36974 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-36978 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38552 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38570 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-196.216 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38578 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38583 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38588 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38627 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-39494 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-196.216 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-39495 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-39502 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40901 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40902 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40958 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40974 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41011 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41042 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41046 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41070 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41073 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41087 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42086 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42092 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42105 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42119 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42148 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42160 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-196.216 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42271 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42280 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42284 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42285 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42301 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42313 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43830 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43839 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-43858 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43900 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44940 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-202.222 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44942 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-202.222 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44987 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-44998 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-45026 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46673 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46738 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46740 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46744 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46759 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46782 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46798 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46800 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46815 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46818 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46828 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46844 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46849 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46853 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47670 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47696 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-47697 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-47698 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-47701 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47742 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49882 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49884 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49894 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49924 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49936 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49966 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49982 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49996 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50007 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50051 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50055 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50074 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50127 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50131 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50143 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50150 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50151 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50180 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50230 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50262 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50267 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50269 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50282 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53057 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-204.224 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53059 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53061 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53141 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-205.225 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-53142 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53156 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53165 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53173 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53227 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53237 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-214.234 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53239 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-56548 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56570 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56600 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56606 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56614 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-56615 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-56631 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-56642 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56651 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-214.234 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57951 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57980 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-58002 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58069 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58240 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21687 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21914 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-22995 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-173.191 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52469 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-176.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52805 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-173.191 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-0841 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-186.206 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-23307 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-35887 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39480 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42104 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53214 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-56601 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56602 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56603 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56605 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56633 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-56704 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57849 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57892 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57904 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58072 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21785 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-21811 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21928 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21934 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-33599 | NONE0 | libc-bin 2.31-0ubuntu9.14 fixed in 2.31-0ubuntu9.16 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2024-33599 | NONE0 | libc-dev-bin 2.31-0ubuntu9.14 fixed in 2.31-0ubuntu9.16 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2024-33599 | NONE0 | libc6 2.31-0ubuntu9.14 fixed in 2.31-0ubuntu9.16 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2024-33599 | NONE0 | libc6-dev 2.31-0ubuntu9.14 fixed in 2.31-0ubuntu9.16 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2024-52006 | NONE0 | git-man 1:2.25.1-1ubuntu3.11 fixed in 1:2.25.1-1ubuntu3.14 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2024-37370 | NONE0 | krb5-locales 1.17-6ubuntu4.4 fixed in 1.17-6ubuntu4.6 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-2398 | NONE0 | libcurl3-gnutls 7.68.0-1ubuntu2.21 fixed in 7.68.0-1ubuntu2.22 | 36.1% High Exploitation Risk | Not Applicable |
| CVE-2024-2398 | NONE0 | libcurl4 7.68.0-1ubuntu2.21 fixed in 7.68.0-1ubuntu2.22 | 36.1% High Exploitation Risk | Not Applicable |
| CVE-2024-45490 | NONE0 | libexpat1 2.2.9-1ubuntu0.6 fixed in 2.2.9-1ubuntu0.7 | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2024-37370 | NONE0 | libgssapi-krb5-2 1.17-6ubuntu4.4 fixed in 1.17-6ubuntu4.6 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-37370 | NONE0 | libk5crypto3 1.17-6ubuntu4.4 fixed in 1.17-6ubuntu4.6 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-37370 | NONE0 | libkrb5-3 1.17-6ubuntu4.4 fixed in 1.17-6ubuntu4.6 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-37370 | NONE0 | libkrb5support0 1.17-6ubuntu4.4 fixed in 1.17-6ubuntu4.6 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2022-50865 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-46838 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-176.196 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2023-52340 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-176.196 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-6356 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-176.196 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2023-6535 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-176.196 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2023-6536 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-176.196 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2024-49997 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2024-0565 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-172.190 | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2024-42093 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-32021 | NONE0 | git-man 1:2.25.1-1ubuntu3.11 fixed in 1:2.25.1-1ubuntu3.12 | 1.0% Theoretical Threat | Not Applicable |
| CVE-2024-26597 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-176.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53150 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2025-21647 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-21762 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2021-47101 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-204.224 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47191 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47219 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52502 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-171.189 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52504 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-186.206 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52507 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-171.189 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52525 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-171.189 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52598 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26593 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-181.201 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26664 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26669 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26673 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26763 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-186.206 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26791 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-186.206 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27401 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-35849 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-35896 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35963 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-204.224 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35965 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-204.224 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35966 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-204.224 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-35967 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-204.224 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36883 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-36960 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-37078 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38381 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38538 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-202.222 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38560 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38599 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38621 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38635 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38659 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39467 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39469 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39471 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39487 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39499 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40929 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40978 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41090 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41091 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42094 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42292 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44999 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46722 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46723 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46724 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-202.222 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46731 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46743 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46747 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46854 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47723 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-47757 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49860 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49900 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50033 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50035 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50278 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50279 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50301 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-52332 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53155 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56597 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56650 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-57906 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57908 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57910 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57911 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-57912 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-57929 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58007 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58014 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21719 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21753 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-21920 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26982 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41059 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53174 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56558 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21782 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-21905 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-4802 | NONE0 | libc-bin 2.31-0ubuntu9.14 fixed in 2.31-0ubuntu9.18 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-4802 | NONE0 | libc-dev-bin 2.31-0ubuntu9.14 fixed in 2.31-0ubuntu9.18 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-4802 | NONE0 | libc6 2.31-0ubuntu9.14 fixed in 2.31-0ubuntu9.18 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-4802 | NONE0 | libc6-dev 2.31-0ubuntu9.14 fixed in 2.31-0ubuntu9.18 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-4244 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-173.191 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-51781 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-172.190 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-6270 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-27397 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-198.218 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-43882 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21703 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-214.234 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-21718 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21761 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21764 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-51779 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-173.191 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-51780 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-173.191 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-51782 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-173.191 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52578 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-171.189 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52847 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-173.191 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26654 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26852 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26974 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27020 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39503 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41049 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42228 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-196.216 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43883 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47747 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49981 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50059 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50234 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21702 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-214.234 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-35827 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-171.189 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49903 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-24023 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-177.197 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2024-24857 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-21400 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-205.225 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26828 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-53820 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26586 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21731 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-0607 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-176.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-24528 | NONE0 | krb5-locales 1.17-6ubuntu4.4 fixed in 1.17-6ubuntu4.9 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-7264 | NONE0 | libcurl3-gnutls 7.68.0-1ubuntu2.21 fixed in 7.68.0-1ubuntu2.23 | 17.3% High Exploitation Risk | Not Applicable |
| CVE-2024-8096 | NONE0 | libcurl3-gnutls 7.68.0-1ubuntu2.21 fixed in 7.68.0-1ubuntu2.24 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-7264 | NONE0 | libcurl4 7.68.0-1ubuntu2.21 fixed in 7.68.0-1ubuntu2.23 | 17.3% High Exploitation Risk | Not Applicable |
| CVE-2024-8096 | NONE0 | libcurl4 7.68.0-1ubuntu2.21 fixed in 7.68.0-1ubuntu2.24 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-24528 | NONE0 | libgssapi-krb5-2 1.17-6ubuntu4.4 fixed in 1.17-6ubuntu4.9 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-24528 | NONE0 | libk5crypto3 1.17-6ubuntu4.4 fixed in 1.17-6ubuntu4.9 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-24528 | NONE0 | libkrb5-3 1.17-6ubuntu4.4 fixed in 1.17-6ubuntu4.9 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-24528 | NONE0 | libkrb5support0 1.17-6ubuntu4.4 fixed in 1.17-6ubuntu4.9 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-36968 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-202.222 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47692 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2024-53135 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36016 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-190.210 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-45863 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-171.189 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-21700 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-214.234 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57979 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52644 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-24861 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26830 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-193.213 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27030 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38544 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41012 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50251 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-21722 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52497 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-202.222 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52810 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-173.191 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42224 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26702 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26894 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-3576 | NONE0 | krb5-locales 1.17-6ubuntu4.4 fixed in 1.17-6ubuntu4.11 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26458 | NONE0 | krb5-locales 1.17-6ubuntu4.4 fixed in 1.17-6ubuntu4.9 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-26461 | NONE0 | krb5-locales 1.17-6ubuntu4.4 fixed in 1.17-6ubuntu4.9 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2024-11053 | NONE0 | libcurl3-gnutls 7.68.0-1ubuntu2.21 fixed in 7.68.0-1ubuntu2.25 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2024-11053 | NONE0 | libcurl4 7.68.0-1ubuntu2.21 fixed in 7.68.0-1ubuntu2.25 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2024-50602 | NONE0 | libexpat1 2.2.9-1ubuntu0.6 fixed in 2.2.9-1ubuntu0.8 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2025-3576 | NONE0 | libgssapi-krb5-2 1.17-6ubuntu4.4 fixed in 1.17-6ubuntu4.11 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26458 | NONE0 | libgssapi-krb5-2 1.17-6ubuntu4.4 fixed in 1.17-6ubuntu4.9 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-26461 | NONE0 | libgssapi-krb5-2 1.17-6ubuntu4.4 fixed in 1.17-6ubuntu4.9 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2025-3576 | NONE0 | libk5crypto3 1.17-6ubuntu4.4 fixed in 1.17-6ubuntu4.11 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26458 | NONE0 | libk5crypto3 1.17-6ubuntu4.4 fixed in 1.17-6ubuntu4.9 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-26461 | NONE0 | libk5crypto3 1.17-6ubuntu4.4 fixed in 1.17-6ubuntu4.9 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2025-3576 | NONE0 | libkrb5-3 1.17-6ubuntu4.4 fixed in 1.17-6ubuntu4.11 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26458 | NONE0 | libkrb5-3 1.17-6ubuntu4.4 fixed in 1.17-6ubuntu4.9 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-26461 | NONE0 | libkrb5-3 1.17-6ubuntu4.4 fixed in 1.17-6ubuntu4.9 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2025-3576 | NONE0 | libkrb5support0 1.17-6ubuntu4.4 fixed in 1.17-6ubuntu4.11 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26458 | NONE0 | libkrb5support0 1.17-6ubuntu4.4 fixed in 1.17-6ubuntu4.9 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-26461 | NONE0 | libkrb5support0 1.17-6ubuntu4.4 fixed in 1.17-6ubuntu4.9 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2024-5535 | NONE0 | libssl1.1 1.1.1f-1ubuntu2.20 fixed in 1.1.1f-1ubuntu2.23 | 5.6% Low-Moderate Risk | Not Applicable |
| CVE-2024-53197 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 3.6% Low-Moderate Risk | Not Applicable |
| CVE-2024-35910 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-4741 | NONE0 | libssl1.1 1.1.1f-1ubuntu2.20 fixed in 1.1.1f-1ubuntu2.23 | 2.9% Low-Moderate Risk | Not Applicable |
| CVE-2025-0395 | NONE0 | libc-bin 2.31-0ubuntu9.14 fixed in 2.31-0ubuntu9.17 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-0395 | NONE0 | libc-dev-bin 2.31-0ubuntu9.14 fixed in 2.31-0ubuntu9.17 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-0395 | NONE0 | libc6 2.31-0ubuntu9.14 fixed in 2.31-0ubuntu9.17 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-0395 | NONE0 | libc6-dev 2.31-0ubuntu9.14 fixed in 2.31-0ubuntu9.17 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-29088 | NONE0 | libsqlite3-0 3.31.1-4ubuntu0.6 fixed in 3.31.1-4ubuntu0.7 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-0727 | NONE0 | libssl1.1 1.1.1f-1ubuntu2.20 fixed in 1.1.1f-1ubuntu2.21 | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2022-36402 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-52880 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26584 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-190.210 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26642 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26643 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-187.207 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26921 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-193.213 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-26925 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-187.207 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26960 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-198.218 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38558 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49958 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50299 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50302 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-53063 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53140 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53217 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56593 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58083 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21760 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 33.4% High Exploitation Risk | Not Applicable |
| CVE-2025-21763 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21926 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-46926 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-193.213 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47076 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-202.222 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47119 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-214.234 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47188 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-196.216 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47212 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47501 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-202.222 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-38096 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-204.224 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2022-48772 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48863 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-196.216 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48938 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-202.222 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49034 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49409 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49558 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-173.191 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-50313 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-23000 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-174.193 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-23004 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-174.193 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-46343 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-171.189 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52435 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52443 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-176.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52448 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-176.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52449 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-176.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52454 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-176.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52458 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52477 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-171.189 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52486 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52488 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-202.222 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52498 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-202.222 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52513 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-171.189 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52522 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-171.189 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52527 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-171.189 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52528 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-171.189 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52566 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-171.189 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52567 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-171.189 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52573 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-171.189 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52574 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-171.189 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52577 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-171.189 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52587 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-181.201 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52595 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52601 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52606 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52615 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52619 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52622 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52623 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-181.201 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52629 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-193.213 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52650 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52655 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-173.191 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52656 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52670 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-181.201 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52675 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-176.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52683 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-176.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52686 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-176.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52690 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-176.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52693 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-176.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52696 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-176.196 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2023-52698 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-176.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52699 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 1.0% Theoretical Threat | Not Applicable |
| CVE-2023-52753 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-173.191 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52774 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-173.191 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52784 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-173.191 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52789 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-173.191 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52791 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-173.191 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52803 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52806 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-173.191 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52809 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-173.191 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52813 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-173.191 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52817 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-173.191 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52819 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-173.191 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52821 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-204.224 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52843 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-173.191 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52845 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-173.191 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52853 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-173.191 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52865 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-173.191 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52871 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-173.191 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52873 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-173.191 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52875 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-173.191 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52876 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-173.191 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52881 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-173.191 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52882 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52887 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52918 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52919 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-171.189 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52923 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-173.191 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52924 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-173.191 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54069 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-173.191 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-6915 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-172.190 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-7042 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-22099 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-23848 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-25739 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26600 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-181.201 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26602 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-181.201 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26606 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26615 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-181.201 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26633 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-176.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26635 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26636 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26640 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26641 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26645 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26651 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26663 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26668 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26675 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-181.201 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26677 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-196.216 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26679 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26684 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26685 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-181.201 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26687 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26688 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-186.206 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26696 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26697 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26722 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26733 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-186.206 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26735 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-186.206 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26751 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-186.206 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26752 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-186.206 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26766 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-186.206 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26772 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-186.206 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26773 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-186.206 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26777 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-186.206 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26778 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-186.206 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26779 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-186.206 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26787 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-196.216 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26788 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-186.206 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26790 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-186.206 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26801 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-186.206 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26804 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-186.206 | 1.0% Theoretical Threat | Not Applicable |
| CVE-2024-26805 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-186.206 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26812 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26816 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26817 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-26825 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26835 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-186.206 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26839 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-186.206 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26840 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-186.206 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26845 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-186.206 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26851 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26855 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26863 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26880 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-26889 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26891 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26901 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-26903 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26917 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26922 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26926 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-26931 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26935 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26937 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26947 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-202.222 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26966 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26969 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26976 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26984 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26994 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26999 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27001 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27004 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27012 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-196.216 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27013 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27028 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2024-27038 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27044 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27046 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27051 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27053 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2024-27059 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27074 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27076 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27077 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27078 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27388 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27399 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27405 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-186.206 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2024-27410 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-186.206 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27412 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-186.206 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27413 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-186.206 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27414 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-186.206 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27416 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-186.206 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27417 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-186.206 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27436 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-27437 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-31076 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-33621 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-35805 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35806 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35807 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-35811 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-182.202 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35813 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35815 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35819 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35821 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-35822 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35823 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2024-35825 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35828 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35830 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35833 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35835 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-181.201 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2024-35852 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-35853 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-35854 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2024-35877 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-35888 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-35893 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35895 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35897 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35898 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35899 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35900 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35904 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-202.222 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35915 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35922 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35925 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35930 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35933 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35936 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35944 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35947 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-35950 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35951 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-202.222 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35955 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2024-35958 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-214.234 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35960 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2024-35969 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-35973 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-35976 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-35978 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-35982 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-35984 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-35997 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36004 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36006 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36007 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36014 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36017 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36020 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36270 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-36286 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-36484 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-36901 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-193.213 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-36902 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-36905 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-36919 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36933 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-36938 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-202.222 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36939 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36941 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36946 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-36953 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-202.222 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36954 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36959 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36964 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-37356 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38549 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38553 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-204.224 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38565 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-38567 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38579 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38582 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2024-38587 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2024-38589 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38597 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-204.224 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38598 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38600 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38602 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38607 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38611 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38615 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38618 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-38619 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38633 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38634 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38637 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38661 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38780 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39276 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39292 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39301 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39475 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39476 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39484 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-193.213 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39488 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39489 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39493 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39505 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-39506 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-39509 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40904 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40910 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-204.224 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40911 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40912 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-40916 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40932 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40934 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40941 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40942 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40945 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40959 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40960 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40961 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40963 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40965 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-40967 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-205.225 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-40968 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40980 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-40981 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-40984 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40987 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40988 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40995 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41006 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41015 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41016 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41017 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41022 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41034 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41035 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41041 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41044 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41063 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41064 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41065 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41066 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41068 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41072 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41081 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41089 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41095 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41097 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41098 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42068 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-202.222 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42070 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42076 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42077 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-202.222 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42084 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42087 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42089 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42090 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42096 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42097 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42101 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42106 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42115 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42124 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42127 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42145 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42153 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42223 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42232 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42236 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42240 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-202.222 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42244 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42246 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42252 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42259 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42265 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42276 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42281 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42283 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42286 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42288 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42289 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42290 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42295 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42297 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42304 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42305 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42306 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42309 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42310 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42311 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-43098 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43829 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43835 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43846 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43853 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43854 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43856 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-43860 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43861 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43863 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43867 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43871 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43879 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43880 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43884 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-43890 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-43893 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-43894 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43908 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43914 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44931 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44935 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44938 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44944 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44946 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-44947 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2024-44948 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44960 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44965 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44969 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44988 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44995 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-45006 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-45008 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-45016 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-198.218 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-45021 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-45025 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-45028 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46675 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46676 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46677 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46685 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46689 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46714 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46719 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46721 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46737 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46739 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46745 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46750 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46755 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46761 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46771 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46777 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46780 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46781 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46783 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46817 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46822 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46829 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46840 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-47663 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47667 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47669 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47671 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47674 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47684 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-47699 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-47706 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47707 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47709 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47710 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47712 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47713 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-47737 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-47740 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47749 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47756 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-48881 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49851 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49867 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49868 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49877 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49878 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49879 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49892 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49896 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49902 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49925 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49938 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49944 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49948 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49949 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49952 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49955 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49957 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49959 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49962 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49963 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49973 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49974 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-214.234 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49975 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49985 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50008 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50024 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50039 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50040 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50045 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50096 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50099 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50116 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50117 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50134 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50142 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50148 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50167 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50168 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50171 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50179 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50184 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50194 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50195 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50199 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50202 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50205 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50218 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50229 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50233 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50236 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50237 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50256 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-214.234 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50265 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50273 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50287 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50290 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50296 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53066 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53112 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53121 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53127 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53130 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53131 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53138 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53145 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53146 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53148 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53157 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53158 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53161 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53164 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-205.225 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53172 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53181 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53183 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53184 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53198 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53680 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53690 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-55916 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56531 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56532 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56539 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-56562 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56567 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56569 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56572 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56574 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56586 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56587 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-56594 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56629 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56630 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-56634 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-56643 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56644 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56645 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56659 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56670 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56681 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56688 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56690 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56691 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56694 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56700 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56720 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56723 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56724 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56739 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56746 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56747 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56748 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56756 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56767 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56769 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56770 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-56779 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56780 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57802 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57807 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57884 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57889 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57890 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57901 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-57902 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-57922 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-57931 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57938 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57946 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57948 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57973 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57977 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57981 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57986 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58001 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58009 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58010 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58017 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58020 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58051 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58052 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58058 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58063 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58071 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-58085 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58090 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58239 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-186.206 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21638 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21639 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21640 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21653 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21664 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21678 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21689 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21694 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21697 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21699 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21708 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21721 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21728 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21736 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21744 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21749 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21765 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-21776 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21781 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21787 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21806 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21814 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21823 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21835 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21846 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21859 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21862 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21865 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21866 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21871 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21877 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21898 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21904 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21909 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21910 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21916 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21917 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21922 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21925 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21935 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21948 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21971 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-44879 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-173.191 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2023-52429 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-176.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52470 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-176.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52583 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52607 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-0340 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-173.191 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-23849 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-181.201 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-23851 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-176.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26813 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26820 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26920 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-181.201 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26973 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26993 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27073 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38612 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2024-46826 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-214.234 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49965 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53101 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53194 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56599 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21848 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-4641 | NONE0 | login 1:4.8.1-1ubuntu5.20.04.4 fixed in 1:4.8.1-1ubuntu5.20.04.5 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-33600 | NONE0 | libc-bin 2.31-0ubuntu9.14 fixed in 2.31-0ubuntu9.16 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2024-33600 | NONE0 | libc-dev-bin 2.31-0ubuntu9.14 fixed in 2.31-0ubuntu9.16 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2024-33600 | NONE0 | libc6 2.31-0ubuntu9.14 fixed in 2.31-0ubuntu9.16 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2024-33600 | NONE0 | libc6-dev 2.31-0ubuntu9.14 fixed in 2.31-0ubuntu9.16 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2024-12243 | NONE0 | libgnutls30 3.6.13-2ubuntu1.10 fixed in 3.6.13-2ubuntu1.12 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2024-28834 | NONE0 | libgnutls30 3.6.13-2ubuntu1.10 fixed in 3.6.13-2ubuntu1.11 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-28182 | NONE0 | libnghttp2-14 1.40.0-1ubuntu0.2 fixed in 1.40.0-1ubuntu0.3 | 84.8% Actively Exploited | Not Applicable |
| CVE-2023-5678 | NONE0 | libssl1.1 1.1.1f-1ubuntu2.20 fixed in 1.1.1f-1ubuntu2.21 | 4.5% Low-Moderate Risk | Not Applicable |
| CVE-2024-12133 | NONE0 | libtasn1-6 4.16.0-2 fixed in 4.16.0-2ubuntu0.1 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2024-26886 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-24858 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-24860 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-193.213 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2023-34324 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-171.189 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2024-24859 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-50349 | NONE0 | git-man 1:2.25.1-1ubuntu3.11 fixed in 1:2.25.1-1ubuntu3.14 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-30258 | NONE0 | gpgv 2.2.19-3ubuntu2.2 fixed in 2.2.19-3ubuntu2.4 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-13176 | NONE0 | libssl1.1 1.1.1f-1ubuntu2.20 fixed in 1.1.1f-1ubuntu2.24 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-26583 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-190.210 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26585 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-190.210 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26923 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47001 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-204.224 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52478 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-171.189 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52602 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52609 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-176.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52639 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-202.222 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53615 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-171.189 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-2201 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-187.207 | 8.6% Low-Moderate Risk | Not Applicable |
| CVE-2024-24855 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-174.193 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26607 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26671 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26859 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26862 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26874 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26878 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26915 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-214.234 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27019 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27419 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35809 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35848 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36952 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-204.224 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38596 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38601 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38613 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-40905 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40943 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-40953 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41020 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42102 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42287 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43892 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-204.224 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44954 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-45003 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46679 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47668 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47679 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50006 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50082 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53124 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53136 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56576 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56637 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57913 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26910 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-28085 | NONE0 | fdisk 2.34-0.1ubuntu9.4 fixed in 2.34-0.1ubuntu9.6 | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2024-28085 | NONE0 | libblkid1 2.34-0.1ubuntu9.4 fixed in 2.34-0.1ubuntu9.6 | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2024-28085 | NONE0 | libfdisk1 2.34-0.1ubuntu9.4 fixed in 2.34-0.1ubuntu9.6 | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2024-28085 | NONE0 | libmount1 2.34-0.1ubuntu9.4 fixed in 2.34-0.1ubuntu9.6 | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2024-28085 | NONE0 | libsmartcols1 2.34-0.1ubuntu9.4 fixed in 2.34-0.1ubuntu9.6 | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2024-28085 | NONE0 | libuuid1 2.34-0.1ubuntu9.4 fixed in 2.34-0.1ubuntu9.6 | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2021-47070 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-186.206 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48627 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52585 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52617 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52838 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-173.191 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52855 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-173.191 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52858 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-173.191 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26712 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-186.206 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26810 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26857 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26875 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36894 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-36950 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38559 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-192.212 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42154 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42131 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-6121 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-173.191 | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2023-47233 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-182.202 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42156 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-202.222 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42157 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42229 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-33601 | NONE0 | libc-bin 2.31-0ubuntu9.14 fixed in 2.31-0ubuntu9.16 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2024-33602 | NONE0 | libc-bin 2.31-0ubuntu9.14 fixed in 2.31-0ubuntu9.16 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-33601 | NONE0 | libc-dev-bin 2.31-0ubuntu9.14 fixed in 2.31-0ubuntu9.16 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2024-33602 | NONE0 | libc-dev-bin 2.31-0ubuntu9.14 fixed in 2.31-0ubuntu9.16 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-33601 | NONE0 | libc6 2.31-0ubuntu9.14 fixed in 2.31-0ubuntu9.16 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2024-33602 | NONE0 | libc6 2.31-0ubuntu9.14 fixed in 2.31-0ubuntu9.16 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-33601 | NONE0 | libc6-dev 2.31-0ubuntu9.14 fixed in 2.31-0ubuntu9.16 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2024-33602 | NONE0 | libc6-dev 2.31-0ubuntu9.14 fixed in 2.31-0ubuntu9.16 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-52597 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-2511 | NONE0 | libssl1.1 1.1.1f-1ubuntu2.20 fixed in 1.1.1f-1ubuntu2.23 | 54.0% Actively Exploited | Not Applicable |
| CVE-2024-9143 | NONE0 | libssl1.1 1.1.1f-1ubuntu2.20 fixed in 1.1.1f-1ubuntu2.24 | 5.8% Low-Moderate Risk | Not Applicable |
| CVE-2024-32020 | NONE0 | git-man 1:2.25.1-1ubuntu3.11 fixed in 1:2.25.1-1ubuntu3.12 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-26614 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-182.202 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26764 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-186.206 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35935 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41007 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-195.215 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43841 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50044 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52620 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54111 | NONE0 | linux-libc-dev 5.4.0-170.188 fixed in 5.4.0-186.206 | 0.2% Theoretical Threat | Not Applicable |
Which CVEs are actually reachable — is the vulnerable code even linked and callable.
Live-container probes: default user, writable paths, capabilities, exposed ports.
A step-by-step hardened build plan, with parity tests proving nothing breaks.
Want to check another image? Run a full scan with the Docker Security Scanner.