Last scanned:
This image carries significant risk; production deployment is highly discouraged without strict compensating controls. Remote attackers could trigger denial of service via HTTP/2 rapid reset (CVE-2023-44487) or cause memory corruption through Kerberos GSS token handling (CVE-2024-37371). Disabling HTTP/2 would fully mitigate CVE-2023-44487, and the image should be placed behind a WAF with minimal network exposure. The large number of exposed vulnerabilities (2,374) means that even with mitigations, this image requires continuous monitoring and a clear remediation plan.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2023-44487 | CRITICAL9.75 | libnghttp2-14 1.40.0-1build1 fixed in 1.40.0-1ubuntu0.2 | 100.0% Actively Exploited | Directly ExposedContext importance: HIGH |
| CVE-2023-0286 | CRITICAL9.62 | libssl1.1 1.1.1f-1ubuntu2.16 fixed in 1.1.1f-1ubuntu2.17 | 59.5% Actively Exploited | Directly Exposed |
| CVE-2024-37371 | CRITICAL9.1 | libgssapi-krb5-2 1.17-6ubuntu4.1 fixed in 1.17-6ubuntu4.6 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2024-37371 | CRITICAL9.1 | libk5crypto3 1.17-6ubuntu4.1 fixed in 1.17-6ubuntu4.6 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2024-37371 | CRITICAL9.1 | libkrb5-3 1.17-6ubuntu4.1 fixed in 1.17-6ubuntu4.6 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2024-37371 | CRITICAL9.1 | libkrb5support0 1.17-6ubuntu4.1 fixed in 1.17-6ubuntu4.6 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2024-47685 | CRITICAL9.1 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-32233 | HIGH8.97 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-150.167 | 13.0% High Exploitation Risk | Directly Exposed |
| CVE-2023-32629 | HIGH8.97 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-155.172 | 10.4% High Exploitation Risk | Directly Exposed |
| CVE-2024-1086 | HIGH8.97 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-174.193 | 28.1% High Exploitation Risk | Directly Exposed |
| CVE-2022-42898 | HIGH8.8 | libasn1-8-heimdal 7.7.0+dfsg-1ubuntu1.2 fixed in 7.7.0+dfsg-1ubuntu1.3 | 6.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-42898 | HIGH8.8 | libgssapi-krb5-2 1.17-6ubuntu4.1 fixed in 1.17-6ubuntu4.2 | 6.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-42898 | HIGH8.8 | libgssapi3-heimdal 7.7.0+dfsg-1ubuntu1.2 fixed in 7.7.0+dfsg-1ubuntu1.3 | 6.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-42898 | HIGH8.8 | libhcrypto4-heimdal 7.7.0+dfsg-1ubuntu1.2 fixed in 7.7.0+dfsg-1ubuntu1.3 | 6.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-42898 | HIGH8.8 | libheimbase1-heimdal 7.7.0+dfsg-1ubuntu1.2 fixed in 7.7.0+dfsg-1ubuntu1.3 | 6.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-42898 | HIGH8.8 | libheimntlm0-heimdal 7.7.0+dfsg-1ubuntu1.2 fixed in 7.7.0+dfsg-1ubuntu1.3 | 6.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-42898 | HIGH8.8 | libhx509-5-heimdal 7.7.0+dfsg-1ubuntu1.2 fixed in 7.7.0+dfsg-1ubuntu1.3 | 6.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-42898 | HIGH8.8 | libk5crypto3 1.17-6ubuntu4.1 fixed in 1.17-6ubuntu4.2 | 6.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-42898 | HIGH8.8 | libkrb5-26-heimdal 7.7.0+dfsg-1ubuntu1.2 fixed in 7.7.0+dfsg-1ubuntu1.3 | 6.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-42898 | HIGH8.8 | libkrb5-3 1.17-6ubuntu4.1 fixed in 1.17-6ubuntu4.2 | 6.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-42898 | HIGH8.8 | libkrb5support0 1.17-6ubuntu4.1 fixed in 1.17-6ubuntu4.2 | 6.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-42898 | HIGH8.8 | libroken18-heimdal 7.7.0+dfsg-1ubuntu1.2 fixed in 7.7.0+dfsg-1ubuntu1.3 | 6.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-42898 | HIGH8.8 | libwind0-heimdal 7.7.0+dfsg-1ubuntu1.2 fixed in 7.7.0+dfsg-1ubuntu1.3 | 6.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-42896 | HIGH8.8 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-137.154 | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-3640 | HIGH8.8 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-2163 | HIGH8.8 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 3.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-5178 | HIGH8.8 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 9.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-36222 | HIGH8.62 | libgssapi-krb5-2 1.17-6ubuntu4.1 fixed in 1.17-6ubuntu4.3 | 10.3% High Exploitation Risk | Directly Exposed |
| CVE-2021-36222 | HIGH8.62 | libk5crypto3 1.17-6ubuntu4.1 fixed in 1.17-6ubuntu4.3 | 10.3% High Exploitation Risk | Directly Exposed |
| CVE-2021-36222 | HIGH8.62 | libkrb5-3 1.17-6ubuntu4.1 fixed in 1.17-6ubuntu4.3 | 10.3% High Exploitation Risk | Directly Exposed |
| CVE-2021-36222 | HIGH8.62 | libkrb5support0 1.17-6ubuntu4.1 fixed in 1.17-6ubuntu4.3 | 10.3% High Exploitation Risk | Directly Exposed |
| CVE-2022-4450 | HIGH8.62 | libssl1.1 1.1.1f-1ubuntu2.16 fixed in 1.1.1f-1ubuntu2.17 | 20.4% High Exploitation Risk | Directly Exposed |
| CVE-2022-43945 | HIGH8.62 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-137.154 | 21.3% High Exploitation Risk | Directly Exposed |
| CVE-2023-2650 | HIGH8.45 | libssl1.1 1.1.1f-1ubuntu2.16 fixed in 1.1.1f-1ubuntu2.19 | 75.1% Actively Exploited | Directly Exposed |
| CVE-2023-1380 | HIGH8.16 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-150.167 | 16.6% High Exploitation Risk | Directly Exposed |
| CVE-2023-31484 | HIGH8.1 | libperl5.30 5.30.0-9ubuntu0.3 fixed in 5.30.0-9ubuntu0.4 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-1829 | HIGH7.8 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-148.165 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-35001 | HIGH7.8 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-155.172 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26581 | HIGH7.8 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-177.197 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-36971 | HIGH7.8 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2024-53104 | HIGH7.8 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 3.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-36886 | HIGH7.8 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0286 | HIGH7.7 | openssl 1.1.1f-1ubuntu2.16 fixed in 1.1.1f-1ubuntu2.17 | 59.5% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2023-48795 | HIGH7.67 | libssh-4 0.9.3-2ubuntu2.2 fixed in 0.9.3-2ubuntu2.4 | 93.3% Actively Exploited | Directly Exposed |
| CVE-2024-33599 | HIGH7.6 | libc-bin 2.31-0ubuntu9.9 fixed in 2.31-0ubuntu9.16 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33599 | HIGH7.6 | libc-dev-bin 2.31-0ubuntu9.9 fixed in 2.31-0ubuntu9.16 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33599 | HIGH7.6 | libc6 2.31-0ubuntu9.9 fixed in 2.31-0ubuntu9.16 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33599 | HIGH7.6 | libc6-dev 2.31-0ubuntu9.9 fixed in 2.31-0ubuntu9.16 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2021-44758 | HIGH7.5 | libasn1-8-heimdal 7.7.0+dfsg-1ubuntu1.2 fixed in 7.7.0+dfsg-1ubuntu1.3 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-45490 | HIGH7.5 | libexpat1 2.2.9-1ubuntu0.6 fixed in 2.2.9-1ubuntu0.7 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2024-0553 | HIGH7.5 | libgnutls30 3.6.13-2ubuntu1.7 fixed in 3.6.13-2ubuntu1.10 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2021-44758 | HIGH7.5 | libgssapi3-heimdal 7.7.0+dfsg-1ubuntu1.2 fixed in 7.7.0+dfsg-1ubuntu1.3 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-44758 | HIGH7.5 | libhcrypto4-heimdal 7.7.0+dfsg-1ubuntu1.2 fixed in 7.7.0+dfsg-1ubuntu1.3 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-44758 | HIGH7.5 | libheimbase1-heimdal 7.7.0+dfsg-1ubuntu1.2 fixed in 7.7.0+dfsg-1ubuntu1.3 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-44758 | HIGH7.5 | libheimntlm0-heimdal 7.7.0+dfsg-1ubuntu1.2 fixed in 7.7.0+dfsg-1ubuntu1.3 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-44758 | HIGH7.5 | libhx509-5-heimdal 7.7.0+dfsg-1ubuntu1.2 fixed in 7.7.0+dfsg-1ubuntu1.3 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-44758 | HIGH7.5 | libkrb5-26-heimdal 7.7.0+dfsg-1ubuntu1.2 fixed in 7.7.0+dfsg-1ubuntu1.3 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-2953 | HIGH7.5 | libldap-2.4-2 2.4.49+dfsg-2ubuntu1.9 fixed in 2.4.49+dfsg-2ubuntu1.10 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2023-2953 | HIGH7.5 | libldap-common 2.4.49+dfsg-2ubuntu1.9 fixed in 2.4.49+dfsg-2ubuntu1.10 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2020-11080 | HIGH7.5 | libnghttp2-14 1.40.0-1build1 fixed in 1.40.0-1ubuntu0.1 | 5.3% Low-Moderate Risk | Directly Exposed |
| CVE-2021-44758 | HIGH7.5 | libroken18-heimdal 7.7.0+dfsg-1ubuntu1.2 fixed in 7.7.0+dfsg-1ubuntu1.3 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0215 | HIGH7.5 | libssl1.1 1.1.1f-1ubuntu2.16 fixed in 1.1.1f-1ubuntu2.17 | 4.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0464 | HIGH7.5 | libssl1.1 1.1.1f-1ubuntu2.16 fixed in 1.1.1f-1ubuntu2.18 | 3.7% Low-Moderate Risk | Directly Exposed |
| CVE-2021-44758 | HIGH7.5 | libwind0-heimdal 7.7.0+dfsg-1ubuntu1.2 fixed in 7.7.0+dfsg-1ubuntu1.3 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-46838 | HIGH7.5 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-176.196 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-6356 | HIGH7.5 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-176.196 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-6535 | HIGH7.5 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-176.196 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-6536 | HIGH7.5 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-176.196 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2024-49997 | HIGH7.5 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0045 | HIGH7.5 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-2196 | HIGH7.48 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-146.163 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-47659 | HIGH7.48 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-0361 | HIGH7.4 | libgnutls30 3.6.13-2ubuntu1.7 fixed in 3.6.13-2ubuntu1.8 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2024-0565 | HIGH7.4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-172.190 | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-7104 | HIGH7.3 | libsqlite3-0 3.31.1-4ubuntu0.5 fixed in 3.31.1-4ubuntu0.6 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-53150 | HIGH7.1 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0266 | HIGH7 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 3.7% Low-Moderate Risk | Directly Exposed |
| CVE-2024-28182 | MEDIUM6.89 | libnghttp2-14 1.40.0-1build1 fixed in 1.40.0-1ubuntu0.3 | 84.8% Actively Exploited | Directly Exposed |
| CVE-2022-50386 | MEDIUM6.8 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52434 | MEDIUM6.8 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-2002 | MEDIUM6.8 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-24023 | MEDIUM6.8 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-177.197 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-4304 | MEDIUM6.79 | libssl1.1 1.1.1f-1ubuntu2.16 fixed in 1.1.1f-1ubuntu2.17 | 16.2% High Exploitation Risk | Directly Exposed |
| CVE-2023-47038 | MEDIUM6.63 | libperl5.30 5.30.0-9ubuntu0.3 fixed in 5.30.0-9ubuntu0.5 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-49770 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50401 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49763 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49775 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50252 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50411 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50423 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-0461 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-1281 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-147.164 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-3090 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-155.172 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-31436 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-150.167 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-3390 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-155.172 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2023-35788 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-153.170 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-3609 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-159.176 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-3611 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-159.176 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-3776 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-159.176 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-40283 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-163.180 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-4206 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-163.180 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-4207 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-163.180 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-4208 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-163.180 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-42753 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-165.182 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-4623 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-165.182 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-4921 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-165.182 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-52664 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-215.235 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52885 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-166.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52927 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-215.235 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-53285 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53305 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53338 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53373 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53485 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53554 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53569 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53608 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-0646 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-172.190 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26689 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-215.235 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26800 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26928 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-212.232 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27398 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-35864 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-212.232 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38630 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-198.218 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49883 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50264 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-204.224 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-53103 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-205.225 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53171 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-56581 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56595 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-56596 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56598 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56619 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56658 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-212.232 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57850 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57900 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-58055 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21704 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-21715 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21735 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-21772 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21791 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-21858 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-47063 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-186.206 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2021-47082 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2021-47103 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2021-47131 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-190.210 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-20421 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-136.153 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2022-3424 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-3545 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-4095 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-136.153 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-4139 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-45934 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-137.154 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2022-48655 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-190.210 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2022-48672 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-136.153 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48674 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48686 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-136.153 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-48695 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-136.153 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48702 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-136.153 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48733 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-202.222 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48791 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-196.216 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48873 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-147.164 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48943 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-202.222 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48948 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-48951 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48956 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-48960 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48962 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48981 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48991 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-49014 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-49015 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-49023 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-49025 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49029 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49779 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49826 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49840 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49846 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49921 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49950 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-136.153 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49952 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-136.153 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50243 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50245 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50248 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50258 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50315 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50419 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50454 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50499 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50542 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-1078 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-149.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-20928 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-20938 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-21255 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-23559 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-146.163 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-3111 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-34319 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-165.182 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-3812 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-51042 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52436 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-176.196 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52438 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-176.196 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52439 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-176.196 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52444 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-176.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52445 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-176.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52451 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-176.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52457 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-176.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52464 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-176.196 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52475 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-171.189 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52509 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-171.189 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52510 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-171.189 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52524 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-171.189 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52530 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-182.202 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52531 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52594 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52599 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52600 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-177.197 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52603 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-177.197 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52604 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52612 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-176.196 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52614 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52637 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52679 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-176.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52691 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-176.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52707 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-149.166 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52741 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52752 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52760 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-193.213 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52764 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-173.191 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52796 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-173.191 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52799 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-173.191 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52804 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-173.191 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52818 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-173.191 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52835 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-173.191 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52836 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-173.191 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52840 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-173.191 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52864 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-173.191 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52867 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-173.191 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52868 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-173.191 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52906 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52988 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-149.166 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-53003 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-147.164 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-53019 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-147.164 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53053 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53081 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53106 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53116 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53138 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53148 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-166.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53153 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53179 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-165.182 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53215 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-166.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53219 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53322 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-166.183 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53372 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53395 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53427 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53454 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53487 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53495 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53500 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53506 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53559 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53560 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-166.183 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-5717 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-6040 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-170.188 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26589 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-177.197 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26598 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26622 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-182.202 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26625 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26704 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-181.201 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26736 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-186.206 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26748 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-186.206 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26749 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-186.206 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26754 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-186.206 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26793 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-186.206 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26882 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26883 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26884 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26885 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26898 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26907 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-190.210 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26934 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26955 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26956 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26957 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26965 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26981 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26996 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27000 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27008 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27024 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27043 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27065 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27075 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27395 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27396 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35789 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-35847 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35855 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35886 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-36015 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-36904 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-36934 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-36940 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36974 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-36978 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-38552 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-38570 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-196.216 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38578 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-38583 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-38588 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38627 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-39494 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-196.216 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-39495 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-39502 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40901 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40902 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40958 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40974 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41011 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41042 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41046 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41070 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41073 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41087 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42086 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42092 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42105 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-42119 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-42148 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-42160 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-196.216 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42271 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42280 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42284 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-42285 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42301 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42313 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43830 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43839 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-43858 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43900 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44940 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-202.222 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44942 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-202.222 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44987 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-44998 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-45026 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46673 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46738 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46740 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46744 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46759 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46782 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46798 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46800 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46815 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46818 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46828 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46844 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46849 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46853 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47670 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47696 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-47697 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-47698 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-47701 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47742 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49882 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49884 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49894 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49924 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49936 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49966 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49982 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49996 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50007 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50051 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50055 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50074 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50127 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50131 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50143 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50150 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50151 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50180 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50230 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50262 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50267 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50269 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50282 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53057 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-204.224 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53059 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53061 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53141 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-205.225 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-53142 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53156 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53165 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53173 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53227 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53237 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-214.234 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53239 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-56548 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56570 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56600 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56606 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56614 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-56615 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-56631 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-56642 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56651 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-214.234 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57951 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57980 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-58002 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58069 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58240 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21687 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21914 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-33631 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-49006 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-49755 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-147.164 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49789 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49811 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49834 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49842 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49907 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49917 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49934 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-136.153 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49956 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-136.153 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50274 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50301 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50368 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50384 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50408 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50422 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50437 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50470 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50496 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50536 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-1118 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-149.166 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-1670 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-2124 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-22995 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-173.191 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52469 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-176.196 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52805 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-173.191 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52922 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-166.183 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-53000 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-147.164 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53075 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53145 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53307 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53308 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53311 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53331 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53388 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53446 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-166.183 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53471 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53484 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53515 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53524 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53541 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53556 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-166.183 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53587 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53604 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53616 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53619 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-166.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53676 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-0841 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-186.206 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-23307 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-35887 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39480 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-42104 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53214 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-56601 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56602 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56603 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56605 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56633 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-56704 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57849 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57892 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57904 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58072 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21785 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-21811 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21928 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21934 | MEDIUM6.63 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-3437 | MEDIUM6.5 | libasn1-8-heimdal 7.7.0+dfsg-1ubuntu1.2 fixed in 7.7.0+dfsg-1ubuntu1.3 | 3.7% Low-Moderate Risk | Directly Exposed |
| CVE-2021-37750 | MEDIUM6.5 | libgssapi-krb5-2 1.17-6ubuntu4.1 fixed in 1.17-6ubuntu4.3 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-36054 | MEDIUM6.5 | libgssapi-krb5-2 1.17-6ubuntu4.1 fixed in 1.17-6ubuntu4.4 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-3437 | MEDIUM6.5 | libgssapi3-heimdal 7.7.0+dfsg-1ubuntu1.2 fixed in 7.7.0+dfsg-1ubuntu1.3 | 3.7% Low-Moderate Risk | Directly Exposed |
| CVE-2022-3437 | MEDIUM6.5 | libhcrypto4-heimdal 7.7.0+dfsg-1ubuntu1.2 fixed in 7.7.0+dfsg-1ubuntu1.3 | 3.7% Low-Moderate Risk | Directly Exposed |
| CVE-2022-3437 | MEDIUM6.5 | libheimbase1-heimdal 7.7.0+dfsg-1ubuntu1.2 fixed in 7.7.0+dfsg-1ubuntu1.3 | 3.7% Low-Moderate Risk | Directly Exposed |
| CVE-2022-3437 | MEDIUM6.5 | libheimntlm0-heimdal 7.7.0+dfsg-1ubuntu1.2 fixed in 7.7.0+dfsg-1ubuntu1.3 | 3.7% Low-Moderate Risk | Directly Exposed |
| CVE-2022-3437 | MEDIUM6.5 | libhx509-5-heimdal 7.7.0+dfsg-1ubuntu1.2 fixed in 7.7.0+dfsg-1ubuntu1.3 | 3.7% Low-Moderate Risk | Directly Exposed |
| CVE-2021-37750 | MEDIUM6.5 | libk5crypto3 1.17-6ubuntu4.1 fixed in 1.17-6ubuntu4.3 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-36054 | MEDIUM6.5 | libk5crypto3 1.17-6ubuntu4.1 fixed in 1.17-6ubuntu4.4 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-3437 | MEDIUM6.5 | libkrb5-26-heimdal 7.7.0+dfsg-1ubuntu1.2 fixed in 7.7.0+dfsg-1ubuntu1.3 | 3.7% Low-Moderate Risk | Directly Exposed |
| CVE-2021-37750 | MEDIUM6.5 | libkrb5-3 1.17-6ubuntu4.1 fixed in 1.17-6ubuntu4.3 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-36054 | MEDIUM6.5 | libkrb5-3 1.17-6ubuntu4.1 fixed in 1.17-6ubuntu4.4 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2021-37750 | MEDIUM6.5 | libkrb5support0 1.17-6ubuntu4.1 fixed in 1.17-6ubuntu4.3 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-36054 | MEDIUM6.5 | libkrb5support0 1.17-6ubuntu4.1 fixed in 1.17-6ubuntu4.4 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-3437 | MEDIUM6.5 | libroken18-heimdal 7.7.0+dfsg-1ubuntu1.2 fixed in 7.7.0+dfsg-1ubuntu1.3 | 3.7% Low-Moderate Risk | Directly Exposed |
| CVE-2023-1667 | MEDIUM6.5 | libssh-4 0.9.3-2ubuntu2.2 fixed in 0.9.3-2ubuntu2.3 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2023-2283 | MEDIUM6.5 | libssh-4 0.9.3-2ubuntu2.2 fixed in 0.9.3-2ubuntu2.3 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-3437 | MEDIUM6.5 | libwind0-heimdal 7.7.0+dfsg-1ubuntu1.2 fixed in 7.7.0+dfsg-1ubuntu1.3 | 3.7% Low-Moderate Risk | Directly Exposed |
| CVE-2022-40982 | MEDIUM6.5 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-159.176 | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-3338 | MEDIUM6.5 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-164.181 | 8.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-47692 | MEDIUM6.5 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-45142 | MEDIUM6.38 | libasn1-8-heimdal 7.7.0+dfsg-1ubuntu1.2 fixed in 7.7.0+dfsg-1ubuntu1.4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-37370 | MEDIUM6.38 | libgssapi-krb5-2 1.17-6ubuntu4.1 fixed in 1.17-6ubuntu4.6 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2022-45142 | MEDIUM6.38 | libgssapi3-heimdal 7.7.0+dfsg-1ubuntu1.2 fixed in 7.7.0+dfsg-1ubuntu1.4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-45142 | MEDIUM6.38 | libhcrypto4-heimdal 7.7.0+dfsg-1ubuntu1.2 fixed in 7.7.0+dfsg-1ubuntu1.4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-45142 | MEDIUM6.38 | libheimbase1-heimdal 7.7.0+dfsg-1ubuntu1.2 fixed in 7.7.0+dfsg-1ubuntu1.4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-45142 | MEDIUM6.38 | libheimntlm0-heimdal 7.7.0+dfsg-1ubuntu1.2 fixed in 7.7.0+dfsg-1ubuntu1.4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-45142 | MEDIUM6.38 | libhx509-5-heimdal 7.7.0+dfsg-1ubuntu1.2 fixed in 7.7.0+dfsg-1ubuntu1.4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-37370 | MEDIUM6.38 | libk5crypto3 1.17-6ubuntu4.1 fixed in 1.17-6ubuntu4.6 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2022-45142 | MEDIUM6.38 | libkrb5-26-heimdal 7.7.0+dfsg-1ubuntu1.2 fixed in 7.7.0+dfsg-1ubuntu1.4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-37370 | MEDIUM6.38 | libkrb5-3 1.17-6ubuntu4.1 fixed in 1.17-6ubuntu4.6 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-37370 | MEDIUM6.38 | libkrb5support0 1.17-6ubuntu4.1 fixed in 1.17-6ubuntu4.6 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2022-45142 | MEDIUM6.38 | libroken18-heimdal 7.7.0+dfsg-1ubuntu1.2 fixed in 7.7.0+dfsg-1ubuntu1.4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-45142 | MEDIUM6.38 | libwind0-heimdal 7.7.0+dfsg-1ubuntu1.2 fixed in 7.7.0+dfsg-1ubuntu1.4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-3623 | MEDIUM6.38 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-50567 | MEDIUM6.38 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50865 | MEDIUM6.38 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-39197 | MEDIUM6.38 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-166.183 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2023-45871 | MEDIUM6.38 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-167.184 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-52340 | MEDIUM6.38 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-176.196 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2023-53827 | MEDIUM6.38 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-20588 | MEDIUM6.32 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-163.180 | 12.4% High Exploitation Risk | Directly Exposed |
| CVE-2025-21760 | MEDIUM6.32 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 33.4% High Exploitation Risk | Directly Exposed |
| CVE-2023-53705 | MEDIUM6.21 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42093 | MEDIUM6.21 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-3567 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-149.166 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-26597 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-176.196 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-21647 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-21762 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2021-47101 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-204.224 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-47191 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-47219 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-47520 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-48701 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-136.153 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48966 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48967 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48999 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-49031 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49032 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49740 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-149.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49852 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49865 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49870 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49945 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-136.153 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49948 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-136.153 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50279 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50333 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50366 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50394 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50478 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50497 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-3268 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-52502 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-171.189 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52504 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-186.206 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52507 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-171.189 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52525 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-171.189 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52598 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52628 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-165.182 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-53024 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-147.164 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53035 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53059 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53090 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53117 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53135 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53213 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-150.167 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53222 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-166.183 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53238 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53265 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53321 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53333 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-166.183 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53357 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-166.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53521 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53668 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-166.183 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53675 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-6606 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-170.188 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-0775 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26593 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-181.201 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26664 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26669 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26673 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26763 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-186.206 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26791 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-186.206 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27401 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-35849 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-35896 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35963 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-204.224 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35965 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-204.224 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35966 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-204.224 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-35967 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-204.224 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36883 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-36960 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-37078 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-38381 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-38538 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-202.222 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-38560 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-38599 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38621 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-38635 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38659 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39467 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39469 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39471 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39487 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39499 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40929 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40978 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41090 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41091 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-42094 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42292 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44999 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46722 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46723 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46724 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-202.222 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46731 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46743 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46747 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46854 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47723 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-47757 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49860 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49900 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50033 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50035 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50278 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50279 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50301 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-52332 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53155 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56597 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56650 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-57906 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57908 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57910 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57911 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-57912 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-57929 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58007 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58014 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21719 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21753 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-21920 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49738 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-149.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-26607 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-3141 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-26982 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41059 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53174 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56558 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21782 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-21905 | MEDIUM6.03 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-4802 | MEDIUM5.95 | libc-bin 2.31-0ubuntu9.9 fixed in 2.31-0ubuntu9.18 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-4802 | MEDIUM5.95 | libc-dev-bin 2.31-0ubuntu9.9 fixed in 2.31-0ubuntu9.18 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-4802 | MEDIUM5.95 | libc6 2.31-0ubuntu9.9 fixed in 2.31-0ubuntu9.18 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-4802 | MEDIUM5.95 | libc6-dev 2.31-0ubuntu9.9 fixed in 2.31-0ubuntu9.18 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-4244 | MEDIUM5.95 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-173.191 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-4622 | MEDIUM5.95 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-165.182 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-51781 | MEDIUM5.95 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-172.190 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-6270 | MEDIUM5.95 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-6931 | MEDIUM5.95 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-170.188 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-6932 | MEDIUM5.95 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-170.188 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-27397 | MEDIUM5.95 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-198.218 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-43882 | MEDIUM5.95 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21703 | MEDIUM5.95 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-214.234 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-21718 | MEDIUM5.95 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21761 | MEDIUM5.95 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21764 | MEDIUM5.95 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-3649 | MEDIUM5.95 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-48872 | MEDIUM5.95 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-147.164 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48988 | MEDIUM5.95 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49919 | MEDIUM5.95 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-49939 | MEDIUM5.95 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-136.153 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50638 | MEDIUM5.95 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50673 | MEDIUM5.95 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-1077 | MEDIUM5.95 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-28466 | MEDIUM5.95 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-51043 | MEDIUM5.95 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-166.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-51779 | MEDIUM5.95 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-173.191 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-51780 | MEDIUM5.95 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-173.191 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-51782 | MEDIUM5.95 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-173.191 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52578 | MEDIUM5.95 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-171.189 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52847 | MEDIUM5.95 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-173.191 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52999 | MEDIUM5.95 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-147.164 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53622 | MEDIUM5.95 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53761 | MEDIUM5.95 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53821 | MEDIUM5.95 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54286 | MEDIUM5.95 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26654 | MEDIUM5.95 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26852 | MEDIUM5.95 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26974 | MEDIUM5.95 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27020 | MEDIUM5.95 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39503 | MEDIUM5.95 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41049 | MEDIUM5.95 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-42228 | MEDIUM5.95 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-196.216 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43883 | MEDIUM5.95 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47747 | MEDIUM5.95 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49981 | MEDIUM5.95 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50059 | MEDIUM5.95 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50234 | MEDIUM5.95 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21702 | MEDIUM5.95 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-214.234 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-45884 | MEDIUM5.95 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-166.183 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-45886 | MEDIUM5.95 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-45919 | MEDIUM5.95 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-1989 | MEDIUM5.95 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-35823 | MEDIUM5.95 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-35824 | MEDIUM5.95 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-35827 | MEDIUM5.95 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-171.189 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-35828 | MEDIUM5.95 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-52974 | MEDIUM5.95 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-149.166 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49903 | MEDIUM5.95 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-4806 | MEDIUM5.9 | libc-bin 2.31-0ubuntu9.9 fixed in 2.31-0ubuntu9.14 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4813 | MEDIUM5.9 | libc-bin 2.31-0ubuntu9.9 fixed in 2.31-0ubuntu9.14 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4806 | MEDIUM5.9 | libc-dev-bin 2.31-0ubuntu9.9 fixed in 2.31-0ubuntu9.14 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4813 | MEDIUM5.9 | libc-dev-bin 2.31-0ubuntu9.9 fixed in 2.31-0ubuntu9.14 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4806 | MEDIUM5.9 | libc6 2.31-0ubuntu9.9 fixed in 2.31-0ubuntu9.14 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4813 | MEDIUM5.9 | libc6 2.31-0ubuntu9.9 fixed in 2.31-0ubuntu9.14 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4806 | MEDIUM5.9 | libc6-dev 2.31-0ubuntu9.9 fixed in 2.31-0ubuntu9.14 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4813 | MEDIUM5.9 | libc6-dev 2.31-0ubuntu9.9 fixed in 2.31-0ubuntu9.14 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2024-50602 | MEDIUM5.9 | libexpat1 2.2.9-1ubuntu0.6 fixed in 2.2.9-1ubuntu0.8 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-5981 | MEDIUM5.9 | libgnutls30 3.6.13-2ubuntu1.7 fixed in 3.6.13-2ubuntu1.9 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libgssapi-krb5-2 1.17-6ubuntu4.1 fixed in 1.17-6ubuntu4.9 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libk5crypto3 1.17-6ubuntu4.1 fixed in 1.17-6ubuntu4.9 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libkrb5-3 1.17-6ubuntu4.1 fixed in 1.17-6ubuntu4.9 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libkrb5support0 1.17-6ubuntu4.1 fixed in 1.17-6ubuntu4.9 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-5535 | MEDIUM5.9 | libssl1.1 1.1.1f-1ubuntu2.16 fixed in 1.1.1f-1ubuntu2.23 | 5.6% Low-Moderate Risk | Directly Exposed |
| CVE-2024-45491 | MEDIUM5.88 | libexpat1 2.2.9-1ubuntu0.6 fixed in 2.2.9-1ubuntu0.7 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-45492 | MEDIUM5.88 | libexpat1 2.2.9-1ubuntu0.6 fixed in 2.2.9-1ubuntu0.7 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2024-53197 | MEDIUM5.8 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 3.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-1079 | MEDIUM5.78 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-24857 | MEDIUM5.78 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-21400 | MEDIUM5.7 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-205.225 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26828 | MEDIUM5.7 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-43750 | MEDIUM5.7 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-136.153 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-2194 | MEDIUM5.7 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-32269 | MEDIUM5.7 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-149.166 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-53820 | MEDIUM5.7 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54102 | MEDIUM5.7 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54110 | MEDIUM5.7 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26586 | MEDIUM5.7 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21731 | MEDIUM5.7 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-3628 | MEDIUM5.61 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-1073 | MEDIUM5.61 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-147.164 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-53729 | MEDIUM5.61 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54168 | MEDIUM5.61 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54179 | MEDIUM5.61 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54300 | MEDIUM5.61 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-166.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-0607 | MEDIUM5.61 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-176.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-4741 | MEDIUM5.6 | libssl1.1 1.1.1f-1ubuntu2.16 fixed in 1.1.1f-1ubuntu2.23 | 2.9% Low-Moderate Risk | Directly Exposed |
| CVE-2023-1998 | MEDIUM5.6 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2025-24528 | MEDIUM5.52 | libgssapi-krb5-2 1.17-6ubuntu4.1 fixed in 1.17-6ubuntu4.9 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-24528 | MEDIUM5.52 | libk5crypto3 1.17-6ubuntu4.1 fixed in 1.17-6ubuntu4.9 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-24528 | MEDIUM5.52 | libkrb5-3 1.17-6ubuntu4.1 fixed in 1.17-6ubuntu4.9 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-24528 | MEDIUM5.52 | libkrb5support0 1.17-6ubuntu4.1 fixed in 1.17-6ubuntu4.9 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-30456 | MEDIUM5.52 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-150.167 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-3643 | MEDIUM5.52 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-137.154 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-42895 | MEDIUM5.52 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-50821 | MEDIUM5.52 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36968 | MEDIUM5.52 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-202.222 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53135 | MEDIUM5.52 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-0727 | MEDIUM5.5 | libssl1.1 1.1.1f-1ubuntu2.16 fixed in 1.1.1f-1ubuntu2.21 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-20593 | MEDIUM5.5 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-159.176 | 5.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0394 | MEDIUM5.5 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-27028 | MEDIUM5.5 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-27053 | MEDIUM5.5 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2024-27405 | MEDIUM5.5 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-186.206 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-35955 | MEDIUM5.5 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-35960 | MEDIUM5.5 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2024-38587 | MEDIUM5.5 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-44879 | MEDIUM5.5 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-173.191 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-38612 | MEDIUM5.5 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-36016 | MEDIUM5.44 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-190.210 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-50880 | MEDIUM5.44 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-45863 | MEDIUM5.44 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-171.189 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52886 | MEDIUM5.44 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-21700 | MEDIUM5.44 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-214.234 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-4382 | MEDIUM5.44 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-146.163 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-30772 | MEDIUM5.44 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-33203 | MEDIUM5.44 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-57979 | MEDIUM5.44 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52644 | MEDIUM5.35 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54072 | MEDIUM5.35 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-24861 | MEDIUM5.35 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26830 | MEDIUM5.35 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-193.213 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27030 | MEDIUM5.35 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38544 | MEDIUM5.35 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41012 | MEDIUM5.35 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-1611 | MEDIUM5.35 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-1855 | MEDIUM5.35 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-33600 | MEDIUM5.3 | libc-bin 2.31-0ubuntu9.9 fixed in 2.31-0ubuntu9.16 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33600 | MEDIUM5.3 | libc-dev-bin 2.31-0ubuntu9.9 fixed in 2.31-0ubuntu9.16 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33600 | MEDIUM5.3 | libc6 2.31-0ubuntu9.9 fixed in 2.31-0ubuntu9.16 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33600 | MEDIUM5.3 | libc6-dev 2.31-0ubuntu9.9 fixed in 2.31-0ubuntu9.16 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-12243 | MEDIUM5.3 | libgnutls30 3.6.13-2ubuntu1.7 fixed in 3.6.13-2ubuntu1.12 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-6918 | MEDIUM5.3 | libssh-4 0.9.3-2ubuntu2.2 fixed in 0.9.3-2ubuntu2.5 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0465 | MEDIUM5.3 | libssl1.1 1.1.1f-1ubuntu2.16 fixed in 1.1.1f-1ubuntu2.18 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0466 | MEDIUM5.3 | libssl1.1 1.1.1f-1ubuntu2.16 fixed in 1.1.1f-1ubuntu2.18 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-3446 | MEDIUM5.3 | libssl1.1 1.1.1f-1ubuntu2.16 fixed in 1.1.1f-1ubuntu2.20 | 6.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-3817 | MEDIUM5.3 | libssl1.1 1.1.1f-1ubuntu2.16 fixed in 1.1.1f-1ubuntu2.20 | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-5678 | MEDIUM5.3 | libssl1.1 1.1.1f-1ubuntu2.16 fixed in 1.1.1f-1ubuntu2.21 | 4.5% Low-Moderate Risk | Directly Exposed |
| CVE-2024-12133 | MEDIUM5.3 | libtasn1-6 4.16.0-2 fixed in 4.16.0-2ubuntu0.1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-2663 | MEDIUM5.3 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-136.153 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-50726 | MEDIUM5.27 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50829 | MEDIUM5.27 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50838 | MEDIUM5.27 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54039 | MEDIUM5.27 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54311 | MEDIUM5.27 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50251 | MEDIUM5.27 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-21722 | MEDIUM5.27 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50717 | MEDIUM5.18 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52497 | MEDIUM5.18 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-202.222 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52810 | MEDIUM5.18 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-173.191 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-53788 | MEDIUM5.18 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53802 | MEDIUM5.18 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53808 | MEDIUM5.18 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42224 | MEDIUM5.18 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-39842 | MEDIUM5.18 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-136.153 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-2398 | MEDIUM5.17 | libcurl3-gnutls 7.68.0-1ubuntu2.14 fixed in 7.68.0-1ubuntu2.22 | 36.1% High Exploitation Risk | Post-Exploit |
| CVE-2024-2398 | MEDIUM5.17 | libcurl4 7.68.0-1ubuntu2.14 fixed in 7.68.0-1ubuntu2.22 | 36.1% High Exploitation Risk | Post-Exploit |
| CVE-2023-39189 | MEDIUM5.1 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-39192 | MEDIUM5.1 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-39193 | MEDIUM5.1 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-26702 | MEDIUM5.1 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26894 | MEDIUM5.1 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-2650 | MEDIUM5.07 | openssl 1.1.1f-1ubuntu2.16 fixed in 1.1.1f-1ubuntu2.19 | 75.1% Actively Exploited | Post-Exploit |
| CVE-2025-3576 | MEDIUM5.02 | libgssapi-krb5-2 1.17-6ubuntu4.1 fixed in 1.17-6ubuntu4.11 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libgssapi-krb5-2 1.17-6ubuntu4.1 fixed in 1.17-6ubuntu4.9 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-3576 | MEDIUM5.02 | libk5crypto3 1.17-6ubuntu4.1 fixed in 1.17-6ubuntu4.11 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libk5crypto3 1.17-6ubuntu4.1 fixed in 1.17-6ubuntu4.9 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-3576 | MEDIUM5.02 | libkrb5-3 1.17-6ubuntu4.1 fixed in 1.17-6ubuntu4.11 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkrb5-3 1.17-6ubuntu4.1 fixed in 1.17-6ubuntu4.9 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-3576 | MEDIUM5.02 | libkrb5support0 1.17-6ubuntu4.1 fixed in 1.17-6ubuntu4.11 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkrb5support0 1.17-6ubuntu4.1 fixed in 1.17-6ubuntu4.9 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-50849 | MEDIUM5.02 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48651 | MEDIUM4.93 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-136.153 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-50625 | MEDIUM4.93 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50636 | MEDIUM4.93 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53717 | MEDIUM4.93 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54045 | MEDIUM4.93 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54120 | MEDIUM4.93 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54136 | MEDIUM4.93 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54214 | MEDIUM4.93 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54236 | MEDIUM4.93 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35910 | MEDIUM4.93 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-31484 | MEDIUM4.86 | perl 5.30.0-9ubuntu0.3 fixed in 5.30.0-9ubuntu0.4 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2023-31484 | MEDIUM4.86 | perl-base 5.30.0-9ubuntu0.3 fixed in 5.30.0-9ubuntu0.4 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2023-31484 | MEDIUM4.86 | perl-modules-5.30 5.30.0-9ubuntu0.3 fixed in 5.30.0-9ubuntu0.4 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2023-1206 | MEDIUM4.84 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-164.181 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-54015 | MEDIUM4.84 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-2511 | MEDIUM4.81 | libssl1.1 1.1.1f-1ubuntu2.16 fixed in 1.1.1f-1ubuntu2.23 | 54.0% Actively Exploited | Directly Exposed |
| CVE-2023-54193 | MEDIUM4.76 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-2201 | MEDIUM4.7 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-187.207 | 8.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-29007 | MEDIUM4.68 | git 1:2.25.1-1ubuntu3.6 fixed in 1:2.25.1-1ubuntu3.11 | 6.1% Low-Moderate Risk | Post-Exploit |
| CVE-2024-32004 | MEDIUM4.68 | git 1:2.25.1-1ubuntu3.6 fixed in 1:2.25.1-1ubuntu3.12 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2025-0395 | MEDIUM4.67 | libc-bin 2.31-0ubuntu9.9 fixed in 2.31-0ubuntu9.17 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-0395 | MEDIUM4.67 | libc-dev-bin 2.31-0ubuntu9.9 fixed in 2.31-0ubuntu9.17 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-0395 | MEDIUM4.67 | libc6 2.31-0ubuntu9.9 fixed in 2.31-0ubuntu9.17 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-0395 | MEDIUM4.67 | libc6-dev 2.31-0ubuntu9.9 fixed in 2.31-0ubuntu9.17 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-29088 | MEDIUM4.67 | libsqlite3-0 3.31.1-4ubuntu0.5 fixed in 3.31.1-4ubuntu0.7 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-3821 | MEDIUM4.67 | libsystemd0 245.4-4ubuntu3.19 fixed in 245.4-4ubuntu3.20 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-4415 | MEDIUM4.67 | libsystemd0 245.4-4ubuntu3.19 fixed in 245.4-4ubuntu3.20 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-3821 | MEDIUM4.67 | libudev1 245.4-4ubuntu3.19 fixed in 245.4-4ubuntu3.20 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-4415 | MEDIUM4.67 | libudev1 245.4-4ubuntu3.19 fixed in 245.4-4ubuntu3.20 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-36402 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-42752 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-165.182 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-42755 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-165.182 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-52880 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53023 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-147.164 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26584 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-190.210 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26642 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26643 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-187.207 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26921 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-193.213 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-26925 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-187.207 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26960 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-198.218 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38558 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49958 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50299 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50302 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-53063 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53140 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53217 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56593 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58083 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21763 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21926 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2020-36691 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2021-4454 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-149.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-46926 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-193.213 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-47076 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-202.222 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-47119 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-214.234 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2021-47176 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-47188 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-196.216 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-47212 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-47501 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-202.222 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-1184 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-3061 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-136.153 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-3108 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-147.164 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-3169 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-3586 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-136.153 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-36280 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2022-3707 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-149.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-38096 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-204.224 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2022-4129 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-147.164 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-42328 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-42329 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-4269 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-47929 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2022-48631 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-136.153 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48636 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-136.153 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48639 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-136.153 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48641 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-136.153 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48644 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-136.153 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48654 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-136.153 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48659 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-136.153 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48687 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-136.153 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48688 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-136.153 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48693 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-136.153 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48697 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-136.153 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48704 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-136.153 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48708 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-149.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48772 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48863 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-196.216 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48877 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-147.164 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48879 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48891 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48896 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48938 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-202.222 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48945 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48946 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-48947 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-137.154 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48949 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-48958 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48969 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-48970 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48971 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48972 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-48973 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48977 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48978 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-48986 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48987 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48992 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48994 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49002 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49005 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49007 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49010 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49011 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49013 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49019 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49020 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49021 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-49033 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-49034 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49035 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49139 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-147.164 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-49271 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-49409 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-49558 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-173.191 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-49739 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49741 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-149.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49746 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-147.164 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49748 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-147.164 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49751 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-147.164 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49757 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-147.164 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49762 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49767 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49768 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-49769 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49772 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49776 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49777 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49780 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49787 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49788 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49790 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49793 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49794 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49802 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49809 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49818 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49821 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49835 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49836 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49841 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49845 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49850 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49853 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49861 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49862 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49869 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49871 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49872 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49874 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49877 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49879 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49880 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49881 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49887 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49890 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49903 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49904 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49912 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49913 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49914 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49915 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49916 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49918 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49922 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49925 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49926 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49927 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49931 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49936 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-136.153 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49937 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-147.164 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49942 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-136.153 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49954 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-136.153 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49957 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-136.153 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49964 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-136.153 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50001 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-149.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50242 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50244 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50246 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50249 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50250 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50251 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50253 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50257 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50261 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50264 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50265 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50268 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50271 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50272 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50273 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50275 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50276 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50278 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50280 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50282 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50285 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50286 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50288 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50289 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50291 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50294 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50296 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50297 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50299 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-136.153 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50309 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50311 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50312 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50313 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50314 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50317 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50318 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50321 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50324 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50330 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50334 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50341 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50343 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50344 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50346 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50347 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50348 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50349 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50352 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50353 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50355 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50359 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50365 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50375 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50376 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50381 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50389 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50395 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50396 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50402 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50405 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50409 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50414 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50415 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50427 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50430 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50431 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50434 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50435 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50439 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50440 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50444 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50449 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50452 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50456 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50458 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50462 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50463 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50473 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50474 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50476 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50480 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50481 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50482 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50484 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50485 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50486 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50489 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50494 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50501 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50503 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50504 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50505 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50509 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50510 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50511 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50513 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50514 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50519 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-136.153 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50520 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50521 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50523 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50525 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50529 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50531 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50532 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50534 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50535 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50538 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50544 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50545 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50547 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50549 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50553 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50555 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50566 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50569 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50578 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50618 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50626 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50645 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50646 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50653 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50655 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50659 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50660 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50664 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-50669 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50670 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50672 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50678 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50703 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50709 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50719 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-50724 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50728 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50731 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50733 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50740 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50742 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50749 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50751 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50760 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-50761 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-50771 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50773 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50780 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50781 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50782 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50832 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50845 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50868 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50872 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50884 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50885 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50889 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-0459 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-149.166 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-0597 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-166.183 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-1074 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-147.164 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-1076 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-2162 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-149.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-2166 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-23000 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-174.193 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-23004 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-174.193 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-23454 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-23455 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-28327 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-28328 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-2985 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-3006 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-3161 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-149.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-3220 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-3358 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-147.164 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-4194 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-164.181 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-42754 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-45862 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-46343 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-171.189 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52435 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52443 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-176.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52448 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-176.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52449 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-176.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52454 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-176.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52458 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52477 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-171.189 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52486 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52488 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-202.222 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52498 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-202.222 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52513 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-171.189 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52522 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-171.189 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52527 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-171.189 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52528 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-171.189 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52566 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-171.189 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52567 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-171.189 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52573 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-171.189 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52574 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-171.189 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52577 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-171.189 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52587 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-181.201 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52595 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52601 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52606 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52615 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52619 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52622 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52623 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-181.201 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52629 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-193.213 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52646 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-149.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52650 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52655 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-173.191 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52656 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52670 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-181.201 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52675 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-176.196 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52683 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-176.196 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52686 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-176.196 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52690 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-176.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52693 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-176.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52696 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-176.196 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-52698 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-176.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52699 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2023-52703 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-149.166 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52705 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-149.166 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52708 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-149.166 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52730 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-149.166 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52742 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-149.166 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52743 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-149.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52745 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-149.166 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52747 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-149.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52753 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-173.191 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52774 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-173.191 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52784 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-173.191 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52789 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-173.191 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52791 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-173.191 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52803 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52806 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-173.191 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52809 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-173.191 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52813 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-173.191 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52817 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-173.191 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52819 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-173.191 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52821 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-204.224 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52843 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-173.191 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52845 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-173.191 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52853 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-173.191 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52865 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-173.191 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52871 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-173.191 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52873 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-173.191 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52875 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-173.191 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52876 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-173.191 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52881 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-173.191 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52882 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52887 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52893 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-147.164 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52894 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-147.164 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52899 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-147.164 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52900 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-147.164 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52901 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-147.164 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52907 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52915 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52918 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52919 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-171.189 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52923 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-173.191 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52924 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-173.191 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52932 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-149.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52933 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-149.166 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52973 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-149.166 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52976 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-149.166 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52977 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-149.166 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52989 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-149.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52992 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-147.164 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52993 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-147.164 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52996 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-147.164 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52997 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-147.164 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-53005 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-147.164 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-53006 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-147.164 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53007 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-147.164 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53015 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-147.164 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53021 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-147.164 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53026 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-147.164 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53031 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53032 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53040 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53041 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53044 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53045 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53051 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53060 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53062 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53066 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53078 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53089 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53096 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53100 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53101 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53108 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53109 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53114 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53119 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53121 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53125 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53134 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53139 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53141 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53146 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53147 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-166.183 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53150 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-166.183 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53151 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-166.183 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53164 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53165 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53167 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-166.183 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53174 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53176 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53182 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53185 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-166.183 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53189 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-166.183 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53191 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53196 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-166.183 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53199 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53220 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53223 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53224 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-149.166 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53226 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53229 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53234 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53239 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53242 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53245 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53246 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53255 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-166.183 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53271 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53275 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53276 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53277 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53280 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-166.183 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53288 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-166.183 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53289 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53290 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53295 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53296 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53297 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53298 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53299 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53302 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53309 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53313 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-166.183 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53314 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53317 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53318 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53324 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53330 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53337 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53339 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53343 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-166.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53344 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53346 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53354 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53365 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53369 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53375 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53379 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-166.183 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53380 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-166.183 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53384 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53397 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-166.183 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53400 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53425 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53431 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53433 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53435 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53436 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53437 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53440 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53443 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53449 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53450 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53451 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-166.183 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53453 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53456 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53457 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53468 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53472 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53477 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53480 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53481 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53488 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53489 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53505 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-166.183 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53518 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53519 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53533 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53535 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53542 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53546 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53548 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53564 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53567 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53568 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53582 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53589 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53590 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53593 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53611 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53612 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53637 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53639 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53641 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53644 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53648 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-166.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53650 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-166.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53658 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-166.183 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53667 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53672 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53679 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53681 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53683 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53687 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-166.183 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53692 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53719 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53724 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53728 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-166.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53731 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-166.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53746 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53747 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53754 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53783 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53800 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53803 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53818 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53825 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53826 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53845 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53847 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53858 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-166.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53863 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-166.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53989 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-166.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53995 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54003 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54004 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54006 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54010 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54012 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54014 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-166.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54021 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54024 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54032 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-166.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54044 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54046 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54051 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54053 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54056 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54057 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54062 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54064 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54069 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-173.191 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54084 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54087 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54091 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-166.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54093 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54095 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54097 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54099 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54114 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54123 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54134 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54170 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54184 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54186 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54189 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-166.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54224 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54264 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54265 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54299 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54305 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54306 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54310 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54314 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54317 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54326 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-166.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-6915 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-172.190 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-7042 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-7324 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-0639 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-166.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-22099 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-23848 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-25739 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26600 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-181.201 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26602 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-181.201 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26606 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26615 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-181.201 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26633 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-176.196 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26635 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26636 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26640 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26641 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26645 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26651 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26663 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26668 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26675 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-181.201 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26677 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-196.216 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26679 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26684 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26685 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-181.201 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26687 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26688 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-186.206 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26696 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26697 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26722 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26733 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-186.206 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26735 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-186.206 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26751 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-186.206 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26752 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-186.206 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26766 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-186.206 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26772 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-186.206 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26773 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-186.206 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26777 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-186.206 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26778 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-186.206 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26779 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-186.206 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26787 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-196.216 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26788 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-186.206 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26790 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-186.206 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26801 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-186.206 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26804 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-186.206 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2024-26805 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-186.206 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26812 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26816 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26817 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26825 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26835 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-186.206 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26839 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-186.206 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26840 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-186.206 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26845 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-186.206 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26851 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26855 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26863 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26880 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-26889 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26891 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26901 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26903 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26917 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26922 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26926 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-26931 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26935 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26937 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26947 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-202.222 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26966 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26969 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26976 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26984 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26994 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26999 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27001 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27004 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27012 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-196.216 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27013 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27038 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27044 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27046 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27051 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27059 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27074 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27076 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27077 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27078 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27388 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27399 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27410 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-186.206 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27412 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-186.206 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27413 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-186.206 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27414 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-186.206 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27416 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-186.206 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27417 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-186.206 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27436 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-27437 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-31076 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-33621 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-35805 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35806 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35807 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-35811 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-182.202 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35813 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35815 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35819 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35821 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-35822 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35823 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-35825 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35828 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35830 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35833 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35835 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-181.201 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-35852 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-35853 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-35854 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-35877 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-35888 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-35893 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35895 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35897 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35898 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35899 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35900 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35904 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-202.222 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35915 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35922 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35925 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35930 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35933 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35936 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35944 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35947 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-35950 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35951 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-202.222 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35958 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-214.234 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35969 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-35973 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-35976 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-35978 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-35982 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-35984 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-35997 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36004 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36006 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36007 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36014 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36017 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36020 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36270 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-36286 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-36484 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-36901 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-193.213 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-36902 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-36905 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-36919 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36933 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-36938 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-202.222 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36939 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36941 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36946 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-36953 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-202.222 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36954 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36959 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36964 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-37356 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38549 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-38553 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-204.224 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38565 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-38567 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-38579 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-38582 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-38589 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38597 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-204.224 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38598 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38600 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38602 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38607 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38611 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38615 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38618 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-38619 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-38633 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38634 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38637 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38661 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-38780 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39276 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39292 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39301 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39475 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39476 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39484 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-193.213 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39488 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39489 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39493 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39505 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-39506 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-39509 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40904 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40910 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-204.224 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40911 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40912 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-40916 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40932 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40934 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40941 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40942 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40945 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40959 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40960 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40961 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40963 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40965 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-40967 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-205.225 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-40968 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40980 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-40981 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-40984 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40987 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40988 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40995 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41006 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41015 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41016 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41017 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41022 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41034 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41035 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41041 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41044 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41063 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41064 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41065 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41066 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41068 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41072 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41081 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41089 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41095 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41097 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41098 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-42068 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-202.222 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42070 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-42076 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42077 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-202.222 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42084 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42087 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42089 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42090 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42096 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42097 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42101 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-42106 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-42115 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-42124 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-42127 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42145 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42153 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42223 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42232 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42236 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42240 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-202.222 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42244 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42246 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42252 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42259 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-42265 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-42276 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42281 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42283 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42286 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42288 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42289 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42290 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42295 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42297 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42304 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42305 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42306 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42309 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42310 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42311 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-43098 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43829 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43835 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43846 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43853 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43854 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43856 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-43860 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43861 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43863 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43867 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43871 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43879 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43880 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43884 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-43890 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-43893 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-43894 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43908 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43914 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44931 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44935 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44938 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44944 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44946 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-44947 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-44948 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44960 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44965 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44969 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44988 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44995 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-45006 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-45008 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-45016 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-198.218 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-45021 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-45025 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-45028 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46675 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46676 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46677 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46685 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46689 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46714 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46719 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46721 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46737 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46739 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46745 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46750 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46755 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46761 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46771 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46777 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46780 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46781 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46783 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46817 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46822 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46829 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46840 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-47663 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47667 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47669 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47671 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47674 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47684 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-47699 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-47706 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47707 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47709 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47710 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47712 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47713 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-47737 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-47740 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47749 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47756 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-48881 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49851 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49867 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49868 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49877 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49878 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49879 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49892 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49896 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49902 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49925 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49938 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49944 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49948 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49949 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49952 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49955 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49957 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49959 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49962 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49963 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49973 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49974 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-214.234 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49975 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49985 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50008 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50024 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50039 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50040 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50045 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50096 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50099 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50116 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50117 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50134 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50142 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50148 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50167 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50168 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50171 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50179 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50184 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50194 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50195 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50199 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50202 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50205 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50218 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50229 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50233 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50236 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50237 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50256 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-214.234 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50265 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50273 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50287 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50290 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50296 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53066 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53112 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53121 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53127 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53130 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53131 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53138 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53145 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53146 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53148 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53157 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53158 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53161 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53164 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-205.225 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53172 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53181 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53183 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53184 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53198 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53680 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53690 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-55916 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56531 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56532 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56539 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-56562 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56567 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56569 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56572 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56574 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56586 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56587 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-56594 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56629 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56630 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-56634 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-56643 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56644 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56645 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56659 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56670 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56681 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56688 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56690 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56691 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56694 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56700 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56720 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56723 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56724 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56739 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56746 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56747 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56748 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56756 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56767 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56769 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56770 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-56779 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56780 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57802 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57807 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57884 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57889 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57890 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57901 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-57902 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-57922 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-57931 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57938 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57946 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57948 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57973 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57977 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57981 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57986 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58001 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58009 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58010 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58017 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58020 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58051 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58052 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58058 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58063 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58071 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58085 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58090 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58239 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-186.206 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21638 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21639 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21640 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21653 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21664 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21678 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21689 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21694 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21697 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21699 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21708 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21721 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21728 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21736 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21744 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21749 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21765 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-21776 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21781 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21787 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21806 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21814 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21823 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21835 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21846 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21859 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21862 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21865 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21866 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21871 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21877 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21898 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21904 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21909 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21910 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21916 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21917 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21922 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21925 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21935 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21948 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21971 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-3669 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-146.163 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-41218 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-4662 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-136.153 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-49753 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-147.164 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49832 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49863 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-0615 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-31084 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-31085 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-167.184 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-34256 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-4132 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-166.183 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52429 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-176.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52470 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-176.196 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52583 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52607 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53124 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53140 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53143 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-0340 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-173.191 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-23849 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-181.201 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-23851 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-176.196 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26813 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26820 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26920 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-181.201 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26973 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26993 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27073 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46826 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-214.234 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49965 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53101 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53194 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56599 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21848 | MEDIUM4.67 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-216.236 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-23521 | MEDIUM4.58 | git 1:2.25.1-1ubuntu3.6 fixed in 1:2.25.1-1ubuntu3.8 | 56.3% Actively Exploited | Post-Exploit |
| CVE-2023-23946 | MEDIUM4.5 | git 1:2.25.1-1ubuntu3.6 fixed in 1:2.25.1-1ubuntu3.10 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2024-52006 | MEDIUM4.5 | git 1:2.25.1-1ubuntu3.6 fixed in 1:2.25.1-1ubuntu3.14 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-0215 | MEDIUM4.5 | openssl 1.1.1f-1ubuntu2.16 fixed in 1.1.1f-1ubuntu2.17 | 4.5% Low-Moderate Risk | Post-Exploit |
| CVE-2023-0464 | MEDIUM4.5 | openssl 1.1.1f-1ubuntu2.16 fixed in 1.1.1f-1ubuntu2.18 | 3.7% Low-Moderate Risk | Post-Exploit |
| CVE-2024-28834 | MEDIUM4.5 | libgnutls30 3.6.13-2ubuntu1.7 fixed in 3.6.13-2ubuntu1.11 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2022-50755 | MEDIUM4.5 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26886 | MEDIUM4.5 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-24858 | MEDIUM4.5 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-24860 | MEDIUM4.5 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-193.213 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-7264 | MEDIUM4.48 | libcurl3-gnutls 7.68.0-1ubuntu2.14 fixed in 7.68.0-1ubuntu2.23 | 17.3% High Exploitation Risk | Post-Exploit |
| CVE-2024-7264 | MEDIUM4.48 | libcurl4 7.68.0-1ubuntu2.14 fixed in 7.68.0-1ubuntu2.23 | 17.3% High Exploitation Risk | Post-Exploit |
| CVE-2023-53841 | MEDIUM4.42 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-166.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-28085 | MEDIUM4.4 | libblkid1 2.34-0.1ubuntu9.3 fixed in 2.34-0.1ubuntu9.6 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-28085 | MEDIUM4.4 | libfdisk1 2.34-0.1ubuntu9.3 fixed in 2.34-0.1ubuntu9.6 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-28085 | MEDIUM4.4 | libmount1 2.34-0.1ubuntu9.3 fixed in 2.34-0.1ubuntu9.6 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-28085 | MEDIUM4.4 | libsmartcols1 2.34-0.1ubuntu9.3 fixed in 2.34-0.1ubuntu9.6 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-28085 | MEDIUM4.4 | libuuid1 2.34-0.1ubuntu9.3 fixed in 2.34-0.1ubuntu9.6 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-50640 | MEDIUM4.33 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54226 | MEDIUM4.33 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-3435 | MEDIUM4.3 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 3.8% Low-Moderate Risk | Directly Exposed |
| CVE-2023-6121 | MEDIUM4.3 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-173.191 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2022-50736 | MEDIUM4.25 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-34324 | MEDIUM4.17 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-171.189 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-2961 | MEDIUM4.12 | libc-bin 2.31-0ubuntu9.9 fixed in 2.31-0ubuntu9.15 | 88.3% Actively Exploited | Post-Exploit |
| CVE-2024-2961 | MEDIUM4.12 | libc-dev-bin 2.31-0ubuntu9.9 fixed in 2.31-0ubuntu9.15 | 88.3% Actively Exploited | Post-Exploit |
| CVE-2024-2961 | MEDIUM4.12 | libc6 2.31-0ubuntu9.9 fixed in 2.31-0ubuntu9.15 | 88.3% Actively Exploited | Post-Exploit |
| CVE-2024-2961 | MEDIUM4.12 | libc6-dev 2.31-0ubuntu9.9 fixed in 2.31-0ubuntu9.15 | 88.3% Actively Exploited | Post-Exploit |
| CVE-2023-6004 | MEDIUM4.08 | libssh-4 0.9.3-2ubuntu2.2 fixed in 0.9.3-2ubuntu2.5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-24859 | MEDIUM4.08 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2022-4304 | MEDIUM4.07 | openssl 1.1.1f-1ubuntu2.16 fixed in 1.1.1f-1ubuntu2.17 | 16.2% High Exploitation Risk | Post-Exploit |
| CVE-2022-41903 | MEDIUM4.06 | git 1:2.25.1-1ubuntu3.6 fixed in 1:2.25.1-1ubuntu3.8 | 44.3% High Exploitation Risk | Post-Exploit |
| CVE-2024-13176 | MEDIUM4 | libssl1.1 1.1.1f-1ubuntu2.16 fixed in 1.1.1f-1ubuntu2.24 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-42756 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-165.182 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-6176 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26583 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-190.210 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26585 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-190.210 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26923 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-47001 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-204.224 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-27672 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-3303 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-136.153 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-39188 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-136.153 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-40307 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-136.153 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-45887 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-48869 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-146.163 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48899 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48997 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49733 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-136.153 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-49771 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49814 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-49968 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-136.153 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50259 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50379 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50668 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50671 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-50676 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-50677 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50697 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50816 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-147.164 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50843 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50875 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-0458 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-147.164 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-0590 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-1382 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-1859 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-2612 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-150.167 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-26545 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-147.164 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52478 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-171.189 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52602 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52609 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-176.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52639 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-202.222 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52896 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-147.164 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52898 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-147.164 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53204 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53368 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53615 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-171.189 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53623 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53766 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53786 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53832 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53839 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53853 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54007 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54244 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54289 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-166.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54309 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-166.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-22386 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-23196 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-24855 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-174.193 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26607 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26671 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26859 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26862 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26874 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26878 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26915 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-214.234 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27019 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27419 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35809 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35848 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36952 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-204.224 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38596 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38601 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38613 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-40905 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40943 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-40953 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41020 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42102 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-42287 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43892 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-204.224 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44954 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-45003 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46679 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47668 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47679 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50006 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50082 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53124 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53136 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56576 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56637 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57913 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-211.231 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-41850 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-1990 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-31083 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-166.183 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26910 | MEDIUM4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-33601 | MEDIUM4 | libc-bin 2.31-0ubuntu9.9 fixed in 2.31-0ubuntu9.16 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33601 | MEDIUM4 | libc-dev-bin 2.31-0ubuntu9.9 fixed in 2.31-0ubuntu9.16 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33601 | MEDIUM4 | libc6 2.31-0ubuntu9.9 fixed in 2.31-0ubuntu9.16 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33601 | MEDIUM4 | libc6-dev 2.31-0ubuntu9.9 fixed in 2.31-0ubuntu9.16 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-32465 | LOW3.98 | git 1:2.25.1-1ubuntu3.6 fixed in 1:2.25.1-1ubuntu3.12 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2023-47038 | LOW3.98 | perl 5.30.0-9ubuntu0.3 fixed in 5.30.0-9ubuntu0.5 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2023-47038 | LOW3.98 | perl-base 5.30.0-9ubuntu0.3 fixed in 5.30.0-9ubuntu0.5 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2023-47038 | LOW3.98 | perl-modules-5.30 5.30.0-9ubuntu0.3 fixed in 5.30.0-9ubuntu0.5 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2023-37453 | LOW3.91 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2022-3903 | LOW3.91 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-147.164 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-25012 | LOW3.91 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-23916 | LOW3.9 | libcurl3-gnutls 7.68.0-1ubuntu2.14 fixed in 7.68.0-1ubuntu2.16 | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2023-46218 | LOW3.9 | libcurl3-gnutls 7.68.0-1ubuntu2.14 fixed in 7.68.0-1ubuntu2.21 | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2023-23916 | LOW3.9 | libcurl4 7.68.0-1ubuntu2.14 fixed in 7.68.0-1ubuntu2.16 | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2023-46218 | LOW3.9 | libcurl4 7.68.0-1ubuntu2.14 fixed in 7.68.0-1ubuntu2.21 | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2022-50866 | LOW3.82 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53831 | LOW3.82 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-7192 | LOW3.74 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2021-47070 | LOW3.74 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-186.206 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-0168 | LOW3.74 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-42432 | LOW3.74 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-136.153 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2022-48627 | LOW3.74 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-50563 | LOW3.74 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50715 | LOW3.74 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-2269 | LOW3.74 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-2860 | LOW3.74 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-136.153 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-3772 | LOW3.74 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-166.183 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-39194 | LOW3.74 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-52585 | LOW3.74 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52617 | LOW3.74 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52838 | LOW3.74 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-173.191 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52855 | LOW3.74 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-173.191 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52858 | LOW3.74 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-173.191 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-53722 | LOW3.74 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54160 | LOW3.74 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26712 | LOW3.74 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-186.206 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26810 | LOW3.74 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26857 | LOW3.74 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26875 | LOW3.74 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36894 | LOW3.74 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-36950 | LOW3.74 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-38559 | LOW3.74 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-192.212 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-42154 | LOW3.74 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-3212 | LOW3.74 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-164.181 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-42131 | LOW3.74 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-32002 | LOW3.73 | git 1:2.25.1-1ubuntu3.6 fixed in 1:2.25.1-1ubuntu3.13 | 25.3% High Exploitation Risk | Post-Exploit |
| CVE-2024-3596 | LOW3.73 | libgssapi-krb5-2 1.17-6ubuntu4.1 fixed in 1.17-6ubuntu4.8 | 14.9% High Exploitation Risk | Post-Exploit |
| CVE-2024-3596 | LOW3.73 | libk5crypto3 1.17-6ubuntu4.1 fixed in 1.17-6ubuntu4.8 | 14.9% High Exploitation Risk | Post-Exploit |
| CVE-2024-3596 | LOW3.73 | libkrb5-3 1.17-6ubuntu4.1 fixed in 1.17-6ubuntu4.8 | 14.9% High Exploitation Risk | Post-Exploit |
| CVE-2024-3596 | LOW3.73 | libkrb5support0 1.17-6ubuntu4.1 fixed in 1.17-6ubuntu4.8 | 14.9% High Exploitation Risk | Post-Exploit |
| CVE-2024-9143 | LOW3.7 | libssl1.1 1.1.1f-1ubuntu2.16 fixed in 1.1.1f-1ubuntu2.24 | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-3646 | LOW3.65 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-136.153 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2023-54213 | LOW3.65 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54270 | LOW3.65 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-47233 | LOW3.65 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-182.202 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-32021 | LOW3.62 | git 1:2.25.1-1ubuntu3.6 fixed in 1:2.25.1-1ubuntu3.12 | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2022-50358 | LOW3.57 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-41849 | LOW3.57 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-43552 | LOW3.54 | libcurl3-gnutls 7.68.0-1ubuntu2.14 fixed in 7.68.0-1ubuntu2.15 | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2023-27535 | LOW3.54 | libcurl3-gnutls 7.68.0-1ubuntu2.14 fixed in 7.68.0-1ubuntu2.18 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2023-27536 | LOW3.54 | libcurl3-gnutls 7.68.0-1ubuntu2.14 fixed in 7.68.0-1ubuntu2.18 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2023-28321 | LOW3.54 | libcurl3-gnutls 7.68.0-1ubuntu2.14 fixed in 7.68.0-1ubuntu2.19 | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2024-11053 | LOW3.54 | libcurl3-gnutls 7.68.0-1ubuntu2.14 fixed in 7.68.0-1ubuntu2.25 | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2022-43552 | LOW3.54 | libcurl4 7.68.0-1ubuntu2.14 fixed in 7.68.0-1ubuntu2.15 | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2023-27535 | LOW3.54 | libcurl4 7.68.0-1ubuntu2.14 fixed in 7.68.0-1ubuntu2.18 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2023-27536 | LOW3.54 | libcurl4 7.68.0-1ubuntu2.14 fixed in 7.68.0-1ubuntu2.18 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2023-28321 | LOW3.54 | libcurl4 7.68.0-1ubuntu2.14 fixed in 7.68.0-1ubuntu2.19 | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2024-11053 | LOW3.54 | libcurl4 7.68.0-1ubuntu2.14 fixed in 7.68.0-1ubuntu2.25 | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2024-5535 | LOW3.54 | openssl 1.1.1f-1ubuntu2.16 fixed in 1.1.1f-1ubuntu2.23 | 5.6% Low-Moderate Risk | Post-Exploit |
| CVE-2022-44640 | LOW3.53 | libasn1-8-heimdal 7.7.0+dfsg-1ubuntu1.2 fixed in 7.7.0+dfsg-1ubuntu1.3 | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2022-44640 | LOW3.53 | libgssapi3-heimdal 7.7.0+dfsg-1ubuntu1.2 fixed in 7.7.0+dfsg-1ubuntu1.3 | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2022-44640 | LOW3.53 | libhcrypto4-heimdal 7.7.0+dfsg-1ubuntu1.2 fixed in 7.7.0+dfsg-1ubuntu1.3 | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2022-44640 | LOW3.53 | libheimbase1-heimdal 7.7.0+dfsg-1ubuntu1.2 fixed in 7.7.0+dfsg-1ubuntu1.3 | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2022-44640 | LOW3.53 | libheimntlm0-heimdal 7.7.0+dfsg-1ubuntu1.2 fixed in 7.7.0+dfsg-1ubuntu1.3 | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2022-44640 | LOW3.53 | libhx509-5-heimdal 7.7.0+dfsg-1ubuntu1.2 fixed in 7.7.0+dfsg-1ubuntu1.3 | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2022-44640 | LOW3.53 | libkrb5-26-heimdal 7.7.0+dfsg-1ubuntu1.2 fixed in 7.7.0+dfsg-1ubuntu1.3 | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2022-44640 | LOW3.53 | libroken18-heimdal 7.7.0+dfsg-1ubuntu1.2 fixed in 7.7.0+dfsg-1ubuntu1.3 | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2022-44640 | LOW3.53 | libwind0-heimdal 7.7.0+dfsg-1ubuntu1.2 fixed in 7.7.0+dfsg-1ubuntu1.3 | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2023-25652 | LOW3.51 | git 1:2.25.1-1ubuntu3.6 fixed in 1:2.25.1-1ubuntu3.11 | 51.9% Actively Exploited | Post-Exploit |
| CVE-2021-4001 | LOW3.48 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-164.181 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-3863 | LOW3.48 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-164.181 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42156 | LOW3.48 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-202.222 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42157 | LOW3.48 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42229 | LOW3.48 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-33602 | LOW3.4 | libc-bin 2.31-0ubuntu9.9 fixed in 2.31-0ubuntu9.16 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-33602 | LOW3.4 | libc-dev-bin 2.31-0ubuntu9.9 fixed in 2.31-0ubuntu9.16 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-33602 | LOW3.4 | libc6 2.31-0ubuntu9.9 fixed in 2.31-0ubuntu9.16 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-33602 | LOW3.4 | libc6-dev 2.31-0ubuntu9.9 fixed in 2.31-0ubuntu9.16 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-50777 | LOW3.4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52597 | LOW3.4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-181.201 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53695 | LOW3.4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53994 | LOW3.4 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-166.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-4741 | LOW3.36 | openssl 1.1.1f-1ubuntu2.16 fixed in 1.1.1f-1ubuntu2.23 | 2.9% Low-Moderate Risk | Post-Exploit |
| CVE-2024-8096 | LOW3.31 | libcurl3-gnutls 7.68.0-1ubuntu2.14 fixed in 7.68.0-1ubuntu2.24 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2024-8096 | LOW3.31 | libcurl4 7.68.0-1ubuntu2.14 fixed in 7.68.0-1ubuntu2.24 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-53715 | LOW3.31 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-27538 | LOW3.3 | libcurl3-gnutls 7.68.0-1ubuntu2.14 fixed in 7.68.0-1ubuntu2.18 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2023-27538 | LOW3.3 | libcurl4 7.68.0-1ubuntu2.14 fixed in 7.68.0-1ubuntu2.18 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2024-0727 | LOW3.3 | openssl 1.1.1f-1ubuntu2.16 fixed in 1.1.1f-1ubuntu2.21 | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2022-48303 | LOW3.3 | tar 1.30+dfsg-7ubuntu0.20.04.2 fixed in 1.30+dfsg-7ubuntu0.20.04.3 | 4.5% Low-Moderate Risk | Post-Exploit |
| CVE-2023-0465 | LOW3.18 | openssl 1.1.1f-1ubuntu2.16 fixed in 1.1.1f-1ubuntu2.18 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2023-0466 | LOW3.18 | openssl 1.1.1f-1ubuntu2.16 fixed in 1.1.1f-1ubuntu2.18 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2023-3446 | LOW3.18 | openssl 1.1.1f-1ubuntu2.16 fixed in 1.1.1f-1ubuntu2.20 | 6.5% Low-Moderate Risk | Post-Exploit |
| CVE-2023-3817 | LOW3.18 | openssl 1.1.1f-1ubuntu2.16 fixed in 1.1.1f-1ubuntu2.20 | 3.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-5678 | LOW3.18 | openssl 1.1.1f-1ubuntu2.16 fixed in 1.1.1f-1ubuntu2.21 | 4.5% Low-Moderate Risk | Post-Exploit |
| CVE-2023-27533 | LOW3.17 | libcurl3-gnutls 7.68.0-1ubuntu2.14 fixed in 7.68.0-1ubuntu2.18 | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-27534 | LOW3.17 | libcurl3-gnutls 7.68.0-1ubuntu2.14 fixed in 7.68.0-1ubuntu2.18 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2023-27533 | LOW3.17 | libcurl4 7.68.0-1ubuntu2.14 fixed in 7.68.0-1ubuntu2.18 | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-27534 | LOW3.17 | libcurl4 7.68.0-1ubuntu2.14 fixed in 7.68.0-1ubuntu2.18 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2022-4450 | LOW3.1 | openssl 1.1.1f-1ubuntu2.16 fixed in 1.1.1f-1ubuntu2.17 | 20.4% High Exploitation Risk | Post-Exploit |
| CVE-2024-2511 | LOW2.89 | openssl 1.1.1f-1ubuntu2.16 fixed in 1.1.1f-1ubuntu2.23 | 54.0% Actively Exploited | Post-Exploit |
| CVE-2023-22490 | LOW2.8 | git 1:2.25.1-1ubuntu3.6 fixed in 1:2.25.1-1ubuntu3.10 | 0.7% Theoretical Threat | 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-2023-4016 | LOW2.8 | libprocps8 2:3.3.16-1ubuntu2.3 fixed in 2:3.3.16-1ubuntu2.4 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50522 | LOW2.8 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50575 | LOW2.8 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50706 | LOW2.8 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50750 | LOW2.8 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50769 | LOW2.8 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50823 | LOW2.8 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50824 | LOW2.8 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50836 | LOW2.8 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50846 | LOW2.8 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50850 | LOW2.8 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50858 | LOW2.8 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50859 | LOW2.8 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50883 | LOW2.8 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50886 | LOW2.8 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50887 | LOW2.8 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-1075 | LOW2.8 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-149.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53998 | LOW2.8 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-166.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54050 | LOW2.8 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54119 | LOW2.8 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54127 | LOW2.8 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54177 | LOW2.8 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54198 | LOW2.8 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54211 | LOW2.8 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54218 | LOW2.8 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54220 | LOW2.8 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54230 | LOW2.8 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54260 | LOW2.8 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54282 | LOW2.8 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54294 | LOW2.8 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54298 | LOW2.8 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26614 | LOW2.8 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-182.202 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26764 | LOW2.8 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-186.206 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35935 | LOW2.8 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41007 | LOW2.8 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-195.215 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43841 | LOW2.8 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-200.220 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50044 | LOW2.8 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-208.228 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-1513 | LOW2.8 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-149.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-28085 | LOW2.64 | bsdutils 1:2.34-0.1ubuntu9.3 fixed in 2.34-0.1ubuntu9.6 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2024-28085 | LOW2.64 | mount 2.34-0.1ubuntu9.3 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.3 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.6 fixed in 1:2.25.1-1ubuntu3.14 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2024-13176 | LOW2.4 | openssl 1.1.1f-1ubuntu2.16 fixed in 1.1.1f-1ubuntu2.24 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-28322 | LOW2.22 | libcurl3-gnutls 7.68.0-1ubuntu2.14 fixed in 7.68.0-1ubuntu2.19 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2023-38546 | LOW2.22 | libcurl3-gnutls 7.68.0-1ubuntu2.14 fixed in 7.68.0-1ubuntu2.20 | 6.2% Low-Moderate Risk | Post-Exploit |
| CVE-2023-28322 | LOW2.22 | libcurl4 7.68.0-1ubuntu2.14 fixed in 7.68.0-1ubuntu2.19 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2023-38546 | LOW2.22 | libcurl4 7.68.0-1ubuntu2.14 fixed in 7.68.0-1ubuntu2.20 | 6.2% Low-Moderate Risk | Post-Exploit |
| CVE-2024-9143 | LOW2.22 | openssl 1.1.1f-1ubuntu2.16 fixed in 1.1.1f-1ubuntu2.24 | 5.8% Low-Moderate Risk | Post-Exploit |
| CVE-2023-52620 | LOW2.12 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-189.209 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-3521 | LOW2.12 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50870 | LOW2.12 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54108 | LOW2.12 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54268 | LOW2.12 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54283 | LOW2.12 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-166.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54312 | LOW2.12 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-166.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-32020 | LOW1.68 | git 1:2.25.1-1ubuntu3.6 fixed in 1:2.25.1-1ubuntu3.12 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-4016 | LOW1.68 | procps 2:3.3.16-1ubuntu2.3 fixed in 2:3.3.16-1ubuntu2.4 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-39804 | LOW1.68 | tar 1.30+dfsg-7ubuntu0.20.04.2 fixed in 1.30+dfsg-7ubuntu0.20.04.4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-25815 | LOW1.12 | git 1:2.25.1-1ubuntu3.6 fixed in 1:2.25.1-1ubuntu3.11 | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2022-23521 | NONE0 | git-man 1:2.25.1-1ubuntu3.6 fixed in 1:2.25.1-1ubuntu3.8 | 56.3% Actively Exploited | Not Applicable |
| CVE-2022-41903 | NONE0 | git-man 1:2.25.1-1ubuntu3.6 fixed in 1:2.25.1-1ubuntu3.8 | 44.3% High Exploitation Risk | Not Applicable |
| CVE-2022-28321 | NONE0 | libpam-modules 1.3.1-5ubuntu4.3 fixed in 1.3.1-5ubuntu4.4 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-28321 | NONE0 | libpam-modules-bin 1.3.1-5ubuntu4.3 fixed in 1.3.1-5ubuntu4.4 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-28321 | NONE0 | libpam-runtime 1.3.1-5ubuntu4.3 fixed in 1.3.1-5ubuntu4.4 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-28321 | NONE0 | libpam0g 1.3.1-5ubuntu4.3 fixed in 1.3.1-5ubuntu4.4 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2024-37371 | NONE0 | krb5-locales 1.17-6ubuntu4.1 fixed in 1.17-6ubuntu4.6 | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2024-32002 | NONE0 | git-man 1:2.25.1-1ubuntu3.6 fixed in 1:2.25.1-1ubuntu3.13 | 25.3% High Exploitation Risk | Not Applicable |
| CVE-2024-3596 | NONE0 | krb5-locales 1.17-6ubuntu4.1 fixed in 1.17-6ubuntu4.8 | 14.9% High Exploitation Risk | Not Applicable |
| CVE-2022-42898 | NONE0 | krb5-locales 1.17-6ubuntu4.1 fixed in 1.17-6ubuntu4.2 | 6.4% Low-Moderate Risk | Not Applicable |
| CVE-2021-39537 | NONE0 | libncurses6 6.2-0ubuntu2 fixed in 6.2-0ubuntu2.1 | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2021-39537 | NONE0 | libncursesw6 6.2-0ubuntu2 fixed in 6.2-0ubuntu2.1 | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2021-39537 | NONE0 | libtinfo6 6.2-0ubuntu2 fixed in 6.2-0ubuntu2.1 | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2021-39537 | NONE0 | ncurses-base 6.2-0ubuntu2 fixed in 6.2-0ubuntu2.1 | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2021-39537 | NONE0 | ncurses-bin 6.2-0ubuntu2 fixed in 6.2-0ubuntu2.1 | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2023-29007 | NONE0 | git-man 1:2.25.1-1ubuntu3.6 fixed in 1:2.25.1-1ubuntu3.11 | 6.1% Low-Moderate Risk | Not Applicable |
| CVE-2024-32004 | NONE0 | git-man 1:2.25.1-1ubuntu3.6 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.6 fixed in 1:2.25.1-1ubuntu3.12 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-29491 | NONE0 | libncurses6 6.2-0ubuntu2 fixed in 6.2-0ubuntu2.1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-29491 | NONE0 | libncursesw6 6.2-0ubuntu2 fixed in 6.2-0ubuntu2.1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-29491 | NONE0 | libtinfo6 6.2-0ubuntu2 fixed in 6.2-0ubuntu2.1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-29491 | NONE0 | ncurses-base 6.2-0ubuntu2 fixed in 6.2-0ubuntu2.1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-29491 | NONE0 | ncurses-bin 6.2-0ubuntu2 fixed in 6.2-0ubuntu2.1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-23946 | NONE0 | git-man 1:2.25.1-1ubuntu3.6 fixed in 1:2.25.1-1ubuntu3.10 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2023-25652 | NONE0 | git-man 1:2.25.1-1ubuntu3.6 fixed in 1:2.25.1-1ubuntu3.11 | 51.9% Actively Exploited | Not Applicable |
| CVE-2024-52006 | NONE0 | git-man 1:2.25.1-1ubuntu3.6 fixed in 1:2.25.1-1ubuntu3.14 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2021-36222 | NONE0 | krb5-locales 1.17-6ubuntu4.1 fixed in 1.17-6ubuntu4.3 | 10.3% High Exploitation Risk | Not Applicable |
| CVE-2024-37370 | NONE0 | krb5-locales 1.17-6ubuntu4.1 fixed in 1.17-6ubuntu4.6 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-32021 | NONE0 | git-man 1:2.25.1-1ubuntu3.6 fixed in 1:2.25.1-1ubuntu3.12 | 1.0% Theoretical Threat | Not Applicable |
| CVE-2022-29458 | NONE0 | libncurses6 6.2-0ubuntu2 fixed in 6.2-0ubuntu2.1 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-29458 | NONE0 | libncursesw6 6.2-0ubuntu2 fixed in 6.2-0ubuntu2.1 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-29458 | NONE0 | libtinfo6 6.2-0ubuntu2 fixed in 6.2-0ubuntu2.1 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-29458 | NONE0 | ncurses-base 6.2-0ubuntu2 fixed in 6.2-0ubuntu2.1 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-29458 | NONE0 | ncurses-bin 6.2-0ubuntu2 fixed in 6.2-0ubuntu2.1 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2021-37750 | NONE0 | krb5-locales 1.17-6ubuntu4.1 fixed in 1.17-6ubuntu4.3 | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2023-36054 | NONE0 | krb5-locales 1.17-6ubuntu4.1 fixed in 1.17-6ubuntu4.4 | 2.8% Low-Moderate Risk | Not Applicable |
| CVE-2025-24528 | NONE0 | krb5-locales 1.17-6ubuntu4.1 fixed in 1.17-6ubuntu4.9 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-3576 | NONE0 | krb5-locales 1.17-6ubuntu4.1 fixed in 1.17-6ubuntu4.11 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26458 | NONE0 | krb5-locales 1.17-6ubuntu4.1 fixed in 1.17-6ubuntu4.9 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-26461 | NONE0 | krb5-locales 1.17-6ubuntu4.1 fixed in 1.17-6ubuntu4.9 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2023-22490 | NONE0 | git-man 1:2.25.1-1ubuntu3.6 fixed in 1:2.25.1-1ubuntu3.10 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-22365 | NONE0 | libpam-modules 1.3.1-5ubuntu4.3 fixed in 1.3.1-5ubuntu4.7 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-22365 | NONE0 | libpam-modules-bin 1.3.1-5ubuntu4.3 fixed in 1.3.1-5ubuntu4.7 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-22365 | NONE0 | libpam-runtime 1.3.1-5ubuntu4.3 fixed in 1.3.1-5ubuntu4.7 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-22365 | NONE0 | libpam0g 1.3.1-5ubuntu4.3 fixed in 1.3.1-5ubuntu4.7 | 0.5% 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-50349 | NONE0 | git-man 1:2.25.1-1ubuntu3.6 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-28085 | NONE0 | fdisk 2.34-0.1ubuntu9.3 fixed in 2.34-0.1ubuntu9.6 | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2024-32020 | NONE0 | git-man 1:2.25.1-1ubuntu3.6 fixed in 1:2.25.1-1ubuntu3.12 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-25815 | NONE0 | git-man 1:2.25.1-1ubuntu3.6 fixed in 1:2.25.1-1ubuntu3.11 | 1.0% Theoretical Threat | Not Applicable |
| CVE-2022-50564 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50568 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50570 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50572 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50574 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50576 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50581 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50624 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50629 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50641 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50644 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50647 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50649 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50652 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50656 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50716 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50732 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50747 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50753 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50754 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50757 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50758 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50767 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50770 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50776 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-50779 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-50786 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50810 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50813 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50828 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50834 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50840 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50848 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50857 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50876 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-139.156 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50879 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-144.161 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53723 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53725 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-166.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53745 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53757 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53782 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53796 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53797 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-166.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53804 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53817 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-53862 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53865 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-166.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53986 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54005 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54017 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54018 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54049 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54079 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54109 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54111 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-186.206 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54112 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54115 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54122 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54124 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54126 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54132 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54140 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54142 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-166.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54158 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54159 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54178 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54183 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54205 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54208 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-152.169 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54219 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54232 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54240 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54255 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-166.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54257 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54266 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-169.187 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54277 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54279 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54284 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54307 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-156.173 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54319 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-166.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-24856 | NONE0 | linux-libc-dev 5.4.0-135.152 fixed in 5.4.0-162.179 | 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.
Base-image lineage, package provenance and signatures — nothing slipped in unnoticed.
A step-by-step hardened build plan, with parity tests proving nothing breaks.
Want to check another image? Run a full scan with the Docker Security Scanner.