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