Last scanned:
AI verdict failed due to an error.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2025-15467 | MEDIUM6.76 | openssl 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.21 | 47.6% High Exploitation Risk | Post-Exploit |
| CVE-2026-31789 | MEDIUM5 | openssl 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.23 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45447 | MEDIUM4.86 | openssl 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.25 | 5.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-28417 | MEDIUM4.68 | vim 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.26 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-45445 | MEDIUM4.64 | openssl 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.25 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-1519 | MEDIUM4.5 | dnsutils 1:9.18.39-0ubuntu0.22.04.2 fixed in 1:9.18.39-0ubuntu0.22.04.3 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-3039 | MEDIUM4.5 | dnsutils 1:9.18.39-0ubuntu0.22.04.2 fixed in 1:9.18.39-0ubuntu0.22.04.4 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-5946 | MEDIUM4.5 | dnsutils 1:9.18.39-0ubuntu0.22.04.2 fixed in 1:9.18.39-0ubuntu0.22.04.4 | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2026-28388 | MEDIUM4.5 | openssl 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.23 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-28389 | MEDIUM4.5 | openssl 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.23 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-28390 | MEDIUM4.5 | openssl 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.23 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-47162 | MEDIUM4.49 | vim 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.32 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-34982 | MEDIUM4.18 | vim 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.27 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-52859 | MEDIUM4.18 | vim 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.32 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8925 | MEDIUM4.13 | curl 7.81.0-1ubuntu1.21 fixed in 7.81.0-1ubuntu1.25 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | MEDIUM4.13 | curl 7.81.0-1ubuntu1.21 fixed in 7.81.0-1ubuntu1.22 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8286 | MEDIUM4.13 | curl 7.81.0-1ubuntu1.21 fixed in 7.81.0-1ubuntu1.25 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-28387 | MEDIUM4.13 | openssl 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.23 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-28421 | LOW3.98 | vim 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.26 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-39881 | LOW3.98 | vim 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.28 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-52858 | LOW3.98 | vim 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.32 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-52860 | LOW3.98 | vim 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.32 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-55693 | LOW3.98 | vim 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.33 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-55895 | LOW3.98 | vim 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.33 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-57455 | LOW3.98 | vim 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.33 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-57456 | LOW3.98 | vim 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.33 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-59856 | LOW3.98 | vim 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.34 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-59858 | LOW3.98 | vim 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.34 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW3.82 | curl 7.81.0-1ubuntu1.21 fixed in 7.81.0-1ubuntu1.25 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-5773 | LOW3.82 | curl 7.81.0-1ubuntu1.21 fixed in 7.81.0-1ubuntu1.24 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW3.82 | curl 7.81.0-1ubuntu1.21 fixed in 7.81.0-1ubuntu1.24 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-41992 | LOW3.82 | gzip 1.10-4ubuntu4.1 fixed in 1.10-4ubuntu4.2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69421 | LOW3.82 | openssl 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.21 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-26269 | LOW3.82 | vim 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.26 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-9547 | LOW3.77 | curl 7.81.0-1ubuntu1.21 fixed in 7.81.0-1ubuntu1.25 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-34182 | LOW3.77 | openssl 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.25 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-69419 | LOW3.77 | openssl 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.21 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-33412 | LOW3.72 | vim 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.27 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-41411 | LOW3.72 | vim 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.29 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-25749 | LOW3.72 | vim 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.26 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-31879 | LOW3.66 | wget 1.21.2-2ubuntu1.1 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-35177 | LOW3.62 | vim 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.33 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-58471 | LOW3.62 | wget 1.21.2-2ubuntu1.1 fixed in 1.21.2-2ubuntu1.3 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-58472 | LOW3.62 | wget 1.21.2-2ubuntu1.1 fixed in 1.21.2-2ubuntu1.3 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-4878 | LOW3.57 | libcap2-bin 1:2.44-1ubuntu0.22.04.2 fixed in 1:2.44-1ubuntu0.22.04.3 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-46483 | LOW3.57 | vim 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.31 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-31790 | LOW3.54 | openssl 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.23 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-1965 | LOW3.47 | curl 7.81.0-1ubuntu1.21 fixed in 7.81.0-1ubuntu1.23 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-28419 | LOW3.37 | vim 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.26 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW3.31 | curl 7.81.0-1ubuntu1.21 fixed in 7.81.0-1ubuntu1.24 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW3.31 | curl 7.81.0-1ubuntu1.21 fixed in 7.81.0-1ubuntu1.24 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-14524 | LOW3.31 | curl 7.81.0-1ubuntu1.21 fixed in 7.81.0-1ubuntu1.22 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-3784 | LOW3.31 | curl 7.81.0-1ubuntu1.21 fixed in 7.81.0-1ubuntu1.23 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | curl 7.81.0-1ubuntu1.21 fixed in 7.81.0-1ubuntu1.25 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-21968 | LOW3.31 | mysql-client 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.45-0ubuntu0.22.04.1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-22009 | LOW3.31 | mysql-client 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-22017 | LOW3.31 | mysql-client 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-34270 | LOW3.31 | mysql-client 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-34271 | LOW3.31 | mysql-client 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-34276 | LOW3.31 | mysql-client 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-34303 | LOW3.31 | mysql-client 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-34308 | LOW3.31 | mysql-client 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-58469 | LOW3.31 | wget 1.21.2-2ubuntu1.1 fixed in 1.21.2-2ubuntu1.3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2017-13716 | LOW3.3 | binutils 2.38-4ubuntu2.12 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010204 | LOW3.3 | binutils 2.38-4ubuntu2.12 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2025-69420 | LOW3.01 | openssl 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.21 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-22796 | LOW3.01 | openssl 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.21 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-42770 | LOW3.01 | openssl 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.25 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-9076 | LOW3.01 | openssl 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.25 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-15146 | LOW3.01 | wget 1.21.2-2ubuntu1.1 fixed in 1.21.2-2ubuntu1.4 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-34180 | LOW3 | openssl 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.25 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-3783 | LOW2.91 | curl 7.81.0-1ubuntu1.21 fixed in 7.81.0-1ubuntu1.23 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-45582 | LOW2.86 | tar 1.34+dfsg-1ubuntu0.1.22.04.2 fixed in 1.34+dfsg-1ubuntu0.1.22.04.4 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | binutils 2.38-4ubuntu2.12 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW2.8 | binutils 2.38-4ubuntu2.12 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2022-48064 | LOW2.8 | binutils 2.38-4ubuntu2.12 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW2.8 | gdb 12.1-0ubuntu1~22.04.2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-22795 | LOW2.8 | openssl 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.21 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-7383 | LOW2.8 | openssl 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.25 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-5704 | LOW2.8 | tar 1.34+dfsg-1ubuntu0.1.22.04.2 fixed in 1.34+dfsg-1ubuntu0.1.22.04.6 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-28418 | LOW2.8 | vim 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.26 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45130 | LOW2.8 | vim 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.30 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-55892 | LOW2.8 | vim 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.33 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-59857 | LOW2.8 | vim 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.34 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW2.7 | curl 7.81.0-1ubuntu1.21 fixed in 7.81.0-1ubuntu1.24 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-7168 | LOW2.7 | curl 7.81.0-1ubuntu1.21 fixed in 7.81.0-1ubuntu1.24 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-4873 | LOW2.7 | curl 7.81.0-1ubuntu1.21 fixed in 7.81.0-1ubuntu1.24 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-3592 | LOW2.7 | dnsutils 1:9.18.39-0ubuntu0.22.04.2 fixed in 1:9.18.39-0ubuntu0.22.04.4 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-5950 | LOW2.7 | dnsutils 1:9.18.39-0ubuntu0.22.04.2 fixed in 1:9.18.39-0ubuntu0.22.04.4 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-42766 | LOW2.7 | openssl 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.25 | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2026-42767 | LOW2.7 | openssl 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.25 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-44656 | LOW2.7 | vim 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.30 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-47167 | LOW2.7 | vim 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.32 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-58470 | LOW2.7 | wget 1.21.2-2ubuntu1.1 fixed in 1.21.2-2ubuntu1.3 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-34743 | LOW2.7 | xz-utils 5.2.5-2ubuntu1 fixed in 5.2.5-2ubuntu1.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-21936 | LOW2.5 | mysql-client 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.45-0ubuntu0.22.04.1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-21937 | LOW2.5 | mysql-client 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.45-0ubuntu0.22.04.1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-21941 | LOW2.5 | mysql-client 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.45-0ubuntu0.22.04.1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-21948 | LOW2.5 | mysql-client 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.45-0ubuntu0.22.04.1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-21964 | LOW2.5 | mysql-client 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.45-0ubuntu0.22.04.1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-21998 | LOW2.5 | mysql-client 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-22002 | LOW2.5 | mysql-client 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-22004 | LOW2.5 | mysql-client 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-22005 | LOW2.5 | mysql-client 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-34267 | LOW2.5 | mysql-client 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-34278 | LOW2.5 | mysql-client 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-34293 | LOW2.5 | mysql-client 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-34304 | LOW2.5 | mysql-client 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-35236 | LOW2.5 | mysql-client 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-35237 | LOW2.5 | mysql-client 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-35238 | LOW2.5 | mysql-client 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-35239 | LOW2.5 | mysql-client 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-35240 | LOW2.5 | mysql-client 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.45 | curl 7.81.0-1ubuntu1.21 fixed in 7.81.0-1ubuntu1.22 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | bsdutils 1:2.37.2-4ubuntu3.4 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | curl 7.81.0-1ubuntu1.21 fixed in 7.81.0-1ubuntu1.22 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-41991 | LOW2.4 | gzip 1.10-4ubuntu4.1 fixed in 1.10-4ubuntu4.2 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | mount 2.37.2-4ubuntu3.4 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68160 | LOW2.4 | openssl 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.21 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | util-linux 2.37.2-4ubuntu3.4 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-57452 | LOW2.4 | vim 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.33 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-28420 | LOW2.24 | vim 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.26 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-42307 | LOW2.24 | vim 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.30 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-22015 | LOW2.19 | mysql-client 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69418 | LOW2.04 | openssl 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.21 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils 2.38-4ubuntu2.12 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-45446 | LOW1.89 | openssl 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.25 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-56433 | LOW1.84 | passwd 1:4.8.1-2ubuntu2.2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils 2.38-4ubuntu2.12 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-29383 | LOW1.68 | passwd 1:4.8.1-2ubuntu2.2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.43 | binutils 2.38-4ubuntu2.12 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-22001 | LOW1.38 | mysql-client 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-28422 | LOW1.12 | vim 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.26 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-54349 | NONE0 | iperf3 3.9-1+deb11u1build0.22.04.1 fixed in 3.9-1+deb11u1ubuntu0.1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-54349 | NONE0 | libiperf0 3.9-1+deb11u1build0.22.04.1 fixed in 3.9-1+deb11u1ubuntu0.1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-45674 | NONE0 | io.netty:netty-resolver-dns 4.1.128.Final fixed in 4.2.15.Final, 4.1.135.Final | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-47691 | NONE0 | io.netty:netty-resolver-dns 4.1.128.Final fixed in 4.2.15.Final, 4.1.135.Final | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-68121 | NONE0 | stdlib v1.23.12 fixed in 1.24.13, 1.25.7, 1.26.0-rc.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2025-14087 | NONE0 | libglib2.0-0 2.72.4-0ubuntu2.6 fixed in 2.72.4-0ubuntu2.7 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-42010 | NONE0 | libgnutls30 3.7.3-4ubuntu1.7 fixed in 3.7.3-4ubuntu1.9 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-8376 | NONE0 | libperl-dev 5.34.0-3ubuntu1.5 fixed in 5.34.0-3ubuntu1.7 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-8376 | NONE0 | libperl5.34 5.34.0-3ubuntu1.5 fixed in 5.34.0-3ubuntu1.7 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-15467 | NONE0 | libssl3 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.21 | 47.6% High Exploitation Risk | Not Applicable |
| CVE-2026-31789 | NONE0 | libssl3 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.23 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6653 | NONE0 | libxml2 2.9.13+dfsg-1ubuntu0.10 fixed in 2.9.13+dfsg-1ubuntu0.12 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-23112 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-177.187 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-23112 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-177.187 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-8376 | NONE0 | perl 5.34.0-3ubuntu1.5 fixed in 5.34.0-3ubuntu1.7 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-8376 | NONE0 | perl-base 5.34.0-3ubuntu1.5 fixed in 5.34.0-3ubuntu1.7 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-8376 | NONE0 | perl-modules-5.34 5.34.0-3ubuntu1.5 fixed in 5.34.0-3ubuntu1.7 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-42581 | NONE0 | io.netty:netty-codec-http 4.1.128.Final fixed in 4.2.13.Final, 4.1.133.Final | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-56817 | NONE0 | io.netty:netty-codec-xml 4.1.128.Final fixed in 4.2.16.Final, 4.1.136.Final | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-33845 | NONE0 | libgnutls30 3.7.3-4ubuntu1.7 fixed in 3.7.3-4ubuntu1.9 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-42496 | NONE0 | libperl-dev 5.34.0-3ubuntu1.5 fixed in 5.34.0-3ubuntu1.7 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-42496 | NONE0 | libperl5.34 5.34.0-3ubuntu1.5 fixed in 5.34.0-3ubuntu1.7 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-45445 | NONE0 | libssl3 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.25 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2021-46848 | NONE0 | libtasn1-6 4.18.0-4ubuntu0.1 fixed in 4.18.0-4ubuntu0.2 | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2022-44940 | NONE0 | patchelf 0.14.3-1 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-42496 | NONE0 | perl 5.34.0-3ubuntu1.5 fixed in 5.34.0-3ubuntu1.7 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-42496 | NONE0 | perl-base 5.34.0-3ubuntu1.5 fixed in 5.34.0-3ubuntu1.7 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-42496 | NONE0 | perl-modules-5.34 5.34.0-3ubuntu1.5 fixed in 5.34.0-3ubuntu1.7 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-42579 | NONE0 | io.netty:netty-codec-dns 4.1.128.Final fixed in 4.2.13.Final, 4.1.133.Final | 1.0% Theoretical Threat | Not Applicable |
| CVE-2026-42584 | NONE0 | io.netty:netty-codec-http 4.1.128.Final fixed in 4.2.13.Final, 4.1.133.Final | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-56820 | NONE0 | io.netty:netty-handler-ssl-ocsp 4.1.128.Final fixed in 4.2.16.Final, 4.1.136.Final | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-2332 | NONE0 | org.eclipse.jetty:jetty-http 12.0.29 fixed in 12.1.7, 12.0.33 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-43037 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-23395 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43037 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-23395 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-47162 | NONE0 | vim-common 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.32 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-47162 | NONE0 | vim-runtime 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.32 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-47162 | NONE0 | xxd 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.32 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-42013 | NONE0 | libgnutls30 3.7.3-4ubuntu1.7 fixed in 3.7.3-4ubuntu1.9 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-5260 | NONE0 | libgnutls30 3.7.3-4ubuntu1.7 fixed in 3.7.3-4ubuntu1.9 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-0966 | NONE0 | libssh-4 0.9.6-2ubuntu0.22.04.5 fixed in 0.9.6-2ubuntu0.22.04.6 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-31788 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31788 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-34982 | NONE0 | vim-common 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.27 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-52859 | NONE0 | vim-common 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.32 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-34982 | NONE0 | vim-runtime 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.27 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-52859 | NONE0 | vim-runtime 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.32 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-34982 | NONE0 | xxd 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.27 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-52859 | NONE0 | xxd 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.32 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39821 | NONE0 | golang.org/x/net v0.33.0 fixed in 0.55.0 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-0861 | NONE0 | libc-bin 2.35-0ubuntu3.11 fixed in 2.35-0ubuntu3.13 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-0861 | NONE0 | libc-dev-bin 2.35-0ubuntu3.11 fixed in 2.35-0ubuntu3.13 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-0861 | NONE0 | libc6 2.35-0ubuntu3.11 fixed in 2.35-0ubuntu3.13 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-0861 | NONE0 | libc6-dev 2.35-0ubuntu3.11 fixed in 2.35-0ubuntu3.13 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-8925 | NONE0 | libcurl3-gnutls 7.81.0-1ubuntu1.21 fixed in 7.81.0-1ubuntu1.25 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-15079 | NONE0 | libcurl3-gnutls 7.81.0-1ubuntu1.21 fixed in 7.81.0-1ubuntu1.22 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-8286 | NONE0 | libcurl3-gnutls 7.81.0-1ubuntu1.21 fixed in 7.81.0-1ubuntu1.25 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-8925 | NONE0 | libcurl4 7.81.0-1ubuntu1.21 fixed in 7.81.0-1ubuntu1.25 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-15079 | NONE0 | libcurl4 7.81.0-1ubuntu1.21 fixed in 7.81.0-1ubuntu1.22 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-8286 | NONE0 | libcurl4 7.81.0-1ubuntu1.21 fixed in 7.81.0-1ubuntu1.25 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-6100 | NONE0 | libpython3.10 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.16 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-6100 | NONE0 | libpython3.10-minimal 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.16 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-6100 | NONE0 | libpython3.10-stdlib 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.16 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-45447 | NONE0 | libssl3 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.25 | 5.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-28387 | NONE0 | libssl3 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.23 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-43114 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43112 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43114 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43112 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-6100 | NONE0 | python3.10 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.16 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-6100 | NONE0 | python3.10-minimal 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.16 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-54512 | NONE0 | com.fasterxml.jackson.core:jackson-databind 2.16.0 fixed in 2.18.8, 3.1.4, 2.21.4 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-54513 | NONE0 | com.fasterxml.jackson.core:jackson-databind 2.16.0 fixed in 2.18.8, 2.21.4, 3.1.4 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-44249 | NONE0 | io.netty:netty-handler 4.1.128.Final fixed in 4.2.15.Final, 4.1.135.Final | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-25681 | NONE0 | golang.org/x/net v0.33.0 fixed in 0.55.0 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-27136 | NONE0 | golang.org/x/net v0.33.0 fixed in 0.55.0 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43133 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43133 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-25210 | NONE0 | libexpat1 2.4.7-1ubuntu0.6 fixed in 2.4.7-1ubuntu0.7 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-25210 | NONE0 | libexpat1-dev 2.4.7-1ubuntu0.6 fixed in 2.4.7-1ubuntu0.7 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | libncurses6 6.3-2ubuntu0.1 fixed in 6.3-2ubuntu0.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | libncursesw6 6.3-2ubuntu0.1 fixed in 6.3-2ubuntu0.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-29111 | NONE0 | libsystemd0 249.11-0ubuntu3.17 fixed in 249.11-0ubuntu3.19 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | libtinfo6 6.3-2ubuntu0.1 fixed in 6.3-2ubuntu0.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-29111 | NONE0 | libudev1 249.11-0ubuntu3.17 fixed in 249.11-0ubuntu3.19 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37777 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-71068 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-23216 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31402 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-49359 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49910 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49935 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50095 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50212 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50213 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50234 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-2640 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-177.187 | 16.1% High Exploitation Risk | Not Applicable |
| CVE-2023-32629 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-177.187 | 10.4% High Exploitation Risk | Not Applicable |
| CVE-2023-53629 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53673 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53179 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-21780 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-171.181 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-21812 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22040 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-22041 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-37778 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-37849 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-174.184 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37899 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2025-37924 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-185.195 | 11.0% High Exploitation Risk | Not Applicable |
| CVE-2025-37926 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-37952 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-38129 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38236 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-38248 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-38349 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38437 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-38552 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-39863 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39952 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39967 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40149 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68817 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-71073 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71082 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71089 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71162 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23001 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23074 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-174.184 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23111 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-174.184 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-23171 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23208 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23209 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23226 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-23227 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23378 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23410 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23411 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23428 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31431 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-179.189 | 94.5% Actively Exploited | Not Applicable |
| CVE-2026-31532 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31709 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31720 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31729 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31759 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43049 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43284 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-181.191 | 93.2% Actively Exploited | Not Applicable |
| CVE-2026-43329 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43378 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43499 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-43500 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-181.191 | 92.9% Actively Exploited | Not Applicable |
| CVE-2026-45891 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46274 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46300 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-181.191 | 7.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-46333 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-181.191 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2026-53148 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53262 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53359 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2013-7445 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 2.7% Low-Moderate Risk | Not Applicable |
| CVE-2020-14356 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2022-3238 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48744 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48771 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48990 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48998 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49471 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49635 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-50071 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50090 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50163 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50240 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50303 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-0030 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-2007 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-26242 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52452 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52624 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-52751 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52837 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52916 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52921 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53037 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53072 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53187 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53218 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54207 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-26699 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26742 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26842 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35862 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-179.189 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35932 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35949 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36012 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36898 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36914 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36921 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38556 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40900 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40954 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40989 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41045 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41050 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41069 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41074 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42117 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42118 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42147 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43842 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46729 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46811 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46813 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46820 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46830 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46833 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46836 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47745 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49880 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49931 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49991 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49992 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50063 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50112 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50246 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53098 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53133 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56538 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-56604 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21927 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-21945 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-21967 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-22022 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37903 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37928 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-37947 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-38022 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38201 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38369 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38734 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-39873 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39955 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40258 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40277 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71078 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71091 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71238 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23078 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23083 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23089 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23098 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23193 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23281 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23408 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23447 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23448 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31452 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31578 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31581 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31696 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43196 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43250 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45839 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45902 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45916 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45920 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45936 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45946 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45984 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46004 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46047 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46068 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46069 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46075 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46122 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46163 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46180 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46189 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46219 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46234 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46241 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46243 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52943 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52962 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52969 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52992 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53004 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53136 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53137 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53294 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53296 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63794 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64600 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2017-13165 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2018-12930 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-12931 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-19378 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2019-19814 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 3.3% Low-Moderate Risk | Not Applicable |
| CVE-2021-26934 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49722 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49980 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50256 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50406 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50492 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50518 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50552 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-33053 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53052 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53320 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53510 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53544 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53596 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-26983 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35868 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50217 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-56609 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57887 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21734 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21863 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21915 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22083 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23133 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37786 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37822 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37861 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37957 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38069 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38117 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38118 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38131 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38239 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38250 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38259 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38361 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38422 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38485 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38584 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38595 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38702 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39797 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39810 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39859 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39880 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-39911 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39913 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39945 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39951 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71075 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71086 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71137 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71152 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71220 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22980 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23068 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23073 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23221 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23234 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23262 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23359 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23361 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31399 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31455 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31485 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31489 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31493 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31500 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31527 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31576 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31580 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31583 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31686 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31702 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31715 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31747 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31748 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43015 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43020 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43027 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43205 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43328 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43426 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43458 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45866 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45867 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45879 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45885 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46267 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46285 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46294 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46301 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53059 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53089 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53112 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53115 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53117 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53120 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53129 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53156 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53157 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53195 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37777 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-71068 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-23216 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31402 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-49359 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49910 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49935 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50095 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50212 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50213 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50234 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-2640 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-177.187 | 16.1% High Exploitation Risk | Not Applicable |
| CVE-2023-32629 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-177.187 | 10.4% High Exploitation Risk | Not Applicable |
| CVE-2023-53629 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53673 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53179 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-21780 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-171.181 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-21812 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22040 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-22041 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-37778 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-37849 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-174.184 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37899 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2025-37924 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-185.195 | 11.0% High Exploitation Risk | Not Applicable |
| CVE-2025-37926 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-37952 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-38129 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38236 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-38248 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-38349 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38437 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-38552 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-39863 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39952 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39967 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40149 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68817 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-71073 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71082 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71089 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71162 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23001 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23074 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-174.184 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23111 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-174.184 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-23171 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23208 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23209 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23226 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-23227 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23378 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23410 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23411 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23428 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31431 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-179.189 | 94.5% Actively Exploited | Not Applicable |
| CVE-2026-31532 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31709 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31720 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31729 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31759 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43049 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43284 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-181.191 | 93.2% Actively Exploited | Not Applicable |
| CVE-2026-43329 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43378 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43499 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-43500 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-181.191 | 92.9% Actively Exploited | Not Applicable |
| CVE-2026-45891 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46274 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46300 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-181.191 | 7.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-46333 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-181.191 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2026-53148 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53262 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53359 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2013-7445 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 2.7% Low-Moderate Risk | Not Applicable |
| CVE-2020-14356 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2022-3238 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48744 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48771 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48990 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48998 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49471 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49635 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-50071 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50090 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50163 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50240 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50303 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-0030 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-2007 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-26242 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52452 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52624 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-52751 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52837 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52916 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52921 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53037 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53072 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53187 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53218 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54207 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-26699 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26742 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26842 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35862 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-179.189 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35932 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35949 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36012 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36898 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36914 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36921 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38556 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40900 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40954 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40989 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41045 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41050 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41069 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41074 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42117 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42118 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42147 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43842 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46729 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46811 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46813 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46820 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46830 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46833 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46836 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47745 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49880 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49931 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49991 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49992 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50063 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50112 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50246 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53098 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53133 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56538 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-56604 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21927 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-21945 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-21967 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-22022 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37903 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37928 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-37947 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-38022 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38201 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38369 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38734 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-39873 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39955 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40258 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40277 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71078 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71091 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71238 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23078 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23083 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23089 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23098 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23193 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23281 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23408 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23447 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23448 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31452 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31578 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31581 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31696 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43196 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43250 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45839 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45902 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45916 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45920 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45936 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45946 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45984 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46004 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46047 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46068 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46069 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46075 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46122 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46163 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46180 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46189 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46219 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46234 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46241 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46243 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52943 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52962 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52969 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52992 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53004 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53136 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53137 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53294 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53296 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63794 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64600 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2017-13165 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2018-12930 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-12931 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-19378 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2019-19814 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 3.3% Low-Moderate Risk | Not Applicable |
| CVE-2021-26934 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49722 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49980 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50256 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50406 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50492 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50518 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50552 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-33053 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53052 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53320 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53510 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53544 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53596 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-26983 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35868 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50217 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-56609 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57887 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21734 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21863 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21915 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22083 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23133 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37786 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37822 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37861 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37957 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38069 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38117 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38118 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38131 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38239 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38250 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38259 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38361 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38422 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38485 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38584 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38595 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38702 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39797 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39810 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39859 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39880 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-39911 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39913 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39945 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39951 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71075 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71086 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71137 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71152 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71220 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22980 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23068 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23073 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23221 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23234 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23262 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23359 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23361 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31399 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31455 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31485 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31489 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31493 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31500 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31527 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31576 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31580 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31583 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31686 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31702 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31715 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31747 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31748 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43015 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43020 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43027 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43205 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43328 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43426 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43458 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45866 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45867 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45879 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45885 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46267 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46285 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46294 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46301 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53059 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53089 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53112 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53115 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53117 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53120 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53129 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53156 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53157 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53195 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-base 6.3-2ubuntu0.1 fixed in 6.3-2ubuntu0.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-bin 6.3-2ubuntu0.1 fixed in 6.3-2ubuntu0.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-28417 | NONE0 | vim-common 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.26 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-28421 | NONE0 | vim-common 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.26 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-39881 | NONE0 | vim-common 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.28 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-52858 | NONE0 | vim-common 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.32 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52860 | NONE0 | vim-common 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.32 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-55693 | NONE0 | vim-common 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.33 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-55895 | NONE0 | vim-common 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.33 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-57455 | NONE0 | vim-common 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.33 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-57456 | NONE0 | vim-common 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.33 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-59856 | NONE0 | vim-common 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.34 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-59858 | NONE0 | vim-common 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.34 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-28417 | NONE0 | vim-runtime 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.26 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-28421 | NONE0 | vim-runtime 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.26 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-39881 | NONE0 | vim-runtime 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.28 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-52858 | NONE0 | vim-runtime 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.32 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52860 | NONE0 | vim-runtime 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.32 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-55693 | NONE0 | vim-runtime 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.33 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-55895 | NONE0 | vim-runtime 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.33 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-57455 | NONE0 | vim-runtime 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.33 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-57456 | NONE0 | vim-runtime 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.33 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-59856 | NONE0 | vim-runtime 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.34 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-59858 | NONE0 | vim-runtime 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.34 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-28417 | NONE0 | xxd 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.26 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-28421 | NONE0 | xxd 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.26 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-39881 | NONE0 | xxd 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.28 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-52858 | NONE0 | xxd 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.32 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52860 | NONE0 | xxd 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.32 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-55693 | NONE0 | xxd 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.33 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-55895 | NONE0 | xxd 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.33 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-57455 | NONE0 | xxd 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.33 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-57456 | NONE0 | xxd 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.33 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-59856 | NONE0 | xxd 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.34 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-59858 | NONE0 | xxd 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.34 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-39822 | NONE0 | stdlib v1.23.12 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-13601 | NONE0 | libglib2.0-0 2.72.4-0ubuntu2.6 fixed in 2.72.4-0ubuntu2.7 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-39971 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39971 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-1519 | NONE0 | bind9-dnsutils 1:9.18.39-0ubuntu0.22.04.2 fixed in 1:9.18.39-0ubuntu0.22.04.3 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2026-3039 | NONE0 | bind9-dnsutils 1:9.18.39-0ubuntu0.22.04.2 fixed in 1:9.18.39-0ubuntu0.22.04.4 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-5946 | NONE0 | bind9-dnsutils 1:9.18.39-0ubuntu0.22.04.2 fixed in 1:9.18.39-0ubuntu0.22.04.4 | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2026-1519 | NONE0 | bind9-host 1:9.18.39-0ubuntu0.22.04.2 fixed in 1:9.18.39-0ubuntu0.22.04.3 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2026-3039 | NONE0 | bind9-host 1:9.18.39-0ubuntu0.22.04.2 fixed in 1:9.18.39-0ubuntu0.22.04.4 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-5946 | NONE0 | bind9-host 1:9.18.39-0ubuntu0.22.04.2 fixed in 1:9.18.39-0ubuntu0.22.04.4 | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2026-1519 | NONE0 | bind9-libs 1:9.18.39-0ubuntu0.22.04.2 fixed in 1:9.18.39-0ubuntu0.22.04.3 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2026-3039 | NONE0 | bind9-libs 1:9.18.39-0ubuntu0.22.04.2 fixed in 1:9.18.39-0ubuntu0.22.04.4 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-5946 | NONE0 | bind9-libs 1:9.18.39-0ubuntu0.22.04.2 fixed in 1:9.18.39-0ubuntu0.22.04.4 | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2024-53580 | NONE0 | iperf3 3.9-1+deb11u1build0.22.04.1 fixed in 3.9-1+deb11u1ubuntu0.1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-32316 | NONE0 | jq 1.6-2.1ubuntu3.1 fixed in 1.6-2.1ubuntu3.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-40164 | NONE0 | jq 1.6-2.1ubuntu3.1 fixed in 1.6-2.1ubuntu3.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-8927 | NONE0 | libcurl3-gnutls 7.81.0-1ubuntu1.21 fixed in 7.81.0-1ubuntu1.25 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-5773 | NONE0 | libcurl3-gnutls 7.81.0-1ubuntu1.21 fixed in 7.81.0-1ubuntu1.24 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-6276 | NONE0 | libcurl3-gnutls 7.81.0-1ubuntu1.21 fixed in 7.81.0-1ubuntu1.24 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-8927 | NONE0 | libcurl4 7.81.0-1ubuntu1.21 fixed in 7.81.0-1ubuntu1.25 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-5773 | NONE0 | libcurl4 7.81.0-1ubuntu1.21 fixed in 7.81.0-1ubuntu1.24 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-6276 | NONE0 | libcurl4 7.81.0-1ubuntu1.21 fixed in 7.81.0-1ubuntu1.24 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-1352 | NONE0 | libdebuginfod-common 0.186-1ubuntu0.1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1352 | NONE0 | libdebuginfod1 0.186-1ubuntu0.1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1352 | NONE0 | libdw1 0.186-1ubuntu0.1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1352 | NONE0 | libelf1 0.186-1ubuntu0.1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-41989 | NONE0 | libgcrypt20 1.9.4-3ubuntu3 fixed in 1.9.4-3ubuntu3.2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-33846 | NONE0 | libgnutls30 3.7.3-4ubuntu1.7 fixed in 3.7.3-4ubuntu1.9 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2026-42009 | NONE0 | libgnutls30 3.7.3-4ubuntu1.7 fixed in 3.7.3-4ubuntu1.9 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2026-40355 | NONE0 | libgssapi-krb5-2 1.19.2-2ubuntu0.7 fixed in 1.19.2-2ubuntu0.8 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-40356 | NONE0 | libgssapi-krb5-2 1.19.2-2ubuntu0.7 fixed in 1.19.2-2ubuntu0.8 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-53580 | NONE0 | libiperf0 3.9-1+deb11u1build0.22.04.1 fixed in 3.9-1+deb11u1ubuntu0.1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-32316 | NONE0 | libjq1 1.6-2.1ubuntu3.1 fixed in 1.6-2.1ubuntu3.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-40164 | NONE0 | libjq1 1.6-2.1ubuntu3.1 fixed in 1.6-2.1ubuntu3.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-40355 | NONE0 | libk5crypto3 1.19.2-2ubuntu0.7 fixed in 1.19.2-2ubuntu0.8 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-40356 | NONE0 | libk5crypto3 1.19.2-2ubuntu0.7 fixed in 1.19.2-2ubuntu0.8 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-40355 | NONE0 | libkrb5-3 1.19.2-2ubuntu0.7 fixed in 1.19.2-2ubuntu0.8 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-40356 | NONE0 | libkrb5-3 1.19.2-2ubuntu0.7 fixed in 1.19.2-2ubuntu0.8 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-40355 | NONE0 | libkrb5support0 1.19.2-2ubuntu0.7 fixed in 1.19.2-2ubuntu0.8 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-40356 | NONE0 | libkrb5support0 1.19.2-2ubuntu0.7 fixed in 1.19.2-2ubuntu0.8 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-27135 | NONE0 | libnghttp2-14 1.43.0-1ubuntu0.2 fixed in 1.43.0-1ubuntu0.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2022-41409 | NONE0 | libpcre2-8-0 10.39-3ubuntu0.1 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2022-0391 | NONE0 | libpython2.7 2.7.18-13ubuntu1.5 No fix yet | 8.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-45061 | NONE0 | libpython2.7 2.7.18-13ubuntu1.5 No fix yet | 2.5% Low-Moderate Risk | Not Applicable |
| CVE-2025-8194 | NONE0 | libpython2.7 2.7.18-13ubuntu1.5 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2019-17514 | NONE0 | libpython2.7 2.7.18-13ubuntu1.5 No fix yet | 4.7% Low-Moderate Risk | Not Applicable |
| CVE-2019-9674 | NONE0 | libpython2.7 2.7.18-13ubuntu1.5 No fix yet | 5.5% Low-Moderate Risk | Not Applicable |
| CVE-2024-7592 | NONE0 | libpython2.7 2.7.18-13ubuntu1.5 No fix yet | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-0391 | NONE0 | libpython2.7-dev 2.7.18-13ubuntu1.5 No fix yet | 8.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-45061 | NONE0 | libpython2.7-dev 2.7.18-13ubuntu1.5 No fix yet | 2.5% Low-Moderate Risk | Not Applicable |
| CVE-2025-8194 | NONE0 | libpython2.7-dev 2.7.18-13ubuntu1.5 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2019-17514 | NONE0 | libpython2.7-dev 2.7.18-13ubuntu1.5 No fix yet | 4.7% Low-Moderate Risk | Not Applicable |
| CVE-2019-9674 | NONE0 | libpython2.7-dev 2.7.18-13ubuntu1.5 No fix yet | 5.5% Low-Moderate Risk | Not Applicable |
| CVE-2024-7592 | NONE0 | libpython2.7-dev 2.7.18-13ubuntu1.5 No fix yet | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-0391 | NONE0 | libpython2.7-minimal 2.7.18-13ubuntu1.5 No fix yet | 8.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-45061 | NONE0 | libpython2.7-minimal 2.7.18-13ubuntu1.5 No fix yet | 2.5% Low-Moderate Risk | Not Applicable |
| CVE-2025-8194 | NONE0 | libpython2.7-minimal 2.7.18-13ubuntu1.5 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2019-17514 | NONE0 | libpython2.7-minimal 2.7.18-13ubuntu1.5 No fix yet | 4.7% Low-Moderate Risk | Not Applicable |
| CVE-2019-9674 | NONE0 | libpython2.7-minimal 2.7.18-13ubuntu1.5 No fix yet | 5.5% Low-Moderate Risk | Not Applicable |
| CVE-2024-7592 | NONE0 | libpython2.7-minimal 2.7.18-13ubuntu1.5 No fix yet | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-0391 | NONE0 | libpython2.7-stdlib 2.7.18-13ubuntu1.5 No fix yet | 8.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-45061 | NONE0 | libpython2.7-stdlib 2.7.18-13ubuntu1.5 No fix yet | 2.5% Low-Moderate Risk | Not Applicable |
| CVE-2025-8194 | NONE0 | libpython2.7-stdlib 2.7.18-13ubuntu1.5 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2019-17514 | NONE0 | libpython2.7-stdlib 2.7.18-13ubuntu1.5 No fix yet | 4.7% Low-Moderate Risk | Not Applicable |
| CVE-2019-9674 | NONE0 | libpython2.7-stdlib 2.7.18-13ubuntu1.5 No fix yet | 5.5% Low-Moderate Risk | Not Applicable |
| CVE-2024-7592 | NONE0 | libpython2.7-stdlib 2.7.18-13ubuntu1.5 No fix yet | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2025-13836 | NONE0 | libpython3.10 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.13 | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2025-69534 | NONE0 | libpython3.10 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.16 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-3644 | NONE0 | libpython3.10 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.16 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-4224 | NONE0 | libpython3.10 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.16 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-13836 | NONE0 | libpython3.10-minimal 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.13 | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2025-69534 | NONE0 | libpython3.10-minimal 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.16 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-3644 | NONE0 | libpython3.10-minimal 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.16 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-4224 | NONE0 | libpython3.10-minimal 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.16 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-13836 | NONE0 | libpython3.10-stdlib 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.13 | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2025-69534 | NONE0 | libpython3.10-stdlib 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.16 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-3644 | NONE0 | libpython3.10-stdlib 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.16 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-4224 | NONE0 | libpython3.10-stdlib 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.16 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-3731 | NONE0 | libssh-4 0.9.6-2ubuntu0.22.04.5 fixed in 0.9.6-2ubuntu0.22.04.7 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-69421 | NONE0 | libssl3 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.21 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-28388 | NONE0 | libssl3 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.23 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-28389 | NONE0 | libssl3 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.23 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-28390 | NONE0 | libssl3 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.23 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2022-4899 | NONE0 | libzstd1 1.4.8+dfsg-3build1 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2026-43501 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-31669 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43186 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-46195 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-53071 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53266 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-0400 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2022-25836 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-36347 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38501 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2025-39973 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40210 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40240 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-68349 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-22998 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-43110 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43190 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-20426 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2026-43501 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-31669 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43186 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-46195 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-53071 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53266 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-0400 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2022-25836 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-36347 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38501 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2025-39973 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40210 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40240 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-68349 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-22998 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-43110 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43190 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-20426 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2022-0391 | NONE0 | python2.7 2.7.18-13ubuntu1.5 No fix yet | 8.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-45061 | NONE0 | python2.7 2.7.18-13ubuntu1.5 No fix yet | 2.5% Low-Moderate Risk | Not Applicable |
| CVE-2025-8194 | NONE0 | python2.7 2.7.18-13ubuntu1.5 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2019-17514 | NONE0 | python2.7 2.7.18-13ubuntu1.5 No fix yet | 4.7% Low-Moderate Risk | Not Applicable |
| CVE-2019-9674 | NONE0 | python2.7 2.7.18-13ubuntu1.5 No fix yet | 5.5% Low-Moderate Risk | Not Applicable |
| CVE-2024-7592 | NONE0 | python2.7 2.7.18-13ubuntu1.5 No fix yet | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-0391 | NONE0 | python2.7-dev 2.7.18-13ubuntu1.5 No fix yet | 8.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-45061 | NONE0 | python2.7-dev 2.7.18-13ubuntu1.5 No fix yet | 2.5% Low-Moderate Risk | Not Applicable |
| CVE-2025-8194 | NONE0 | python2.7-dev 2.7.18-13ubuntu1.5 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2019-17514 | NONE0 | python2.7-dev 2.7.18-13ubuntu1.5 No fix yet | 4.7% Low-Moderate Risk | Not Applicable |
| CVE-2019-9674 | NONE0 | python2.7-dev 2.7.18-13ubuntu1.5 No fix yet | 5.5% Low-Moderate Risk | Not Applicable |
| CVE-2024-7592 | NONE0 | python2.7-dev 2.7.18-13ubuntu1.5 No fix yet | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-0391 | NONE0 | python2.7-minimal 2.7.18-13ubuntu1.5 No fix yet | 8.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-45061 | NONE0 | python2.7-minimal 2.7.18-13ubuntu1.5 No fix yet | 2.5% Low-Moderate Risk | Not Applicable |
| CVE-2025-8194 | NONE0 | python2.7-minimal 2.7.18-13ubuntu1.5 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2019-17514 | NONE0 | python2.7-minimal 2.7.18-13ubuntu1.5 No fix yet | 4.7% Low-Moderate Risk | Not Applicable |
| CVE-2019-9674 | NONE0 | python2.7-minimal 2.7.18-13ubuntu1.5 No fix yet | 5.5% Low-Moderate Risk | Not Applicable |
| CVE-2024-7592 | NONE0 | python2.7-minimal 2.7.18-13ubuntu1.5 No fix yet | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2025-13836 | NONE0 | python3.10 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.13 | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2025-69534 | NONE0 | python3.10 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.16 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-3644 | NONE0 | python3.10 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.16 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-4224 | NONE0 | python3.10 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.16 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-13836 | NONE0 | python3.10-minimal 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.13 | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2025-69534 | NONE0 | python3.10-minimal 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.16 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-3644 | NONE0 | python3.10-minimal 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.16 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-4224 | NONE0 | python3.10-minimal 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.16 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-26269 | NONE0 | vim-common 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.26 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-26269 | NONE0 | vim-runtime 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.26 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-26269 | NONE0 | xxd 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.26 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-42583 | NONE0 | io.netty:netty-codec 4.1.128.Final fixed in 4.1.133.Final | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-59901 | NONE0 | io.netty:netty-codec 4.1.128.Final fixed in 4.1.136.Final | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-44893 | NONE0 | io.netty:netty-codec-haproxy 4.1.128.Final fixed in 4.2.15.Final, 4.1.135.Final | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-48059 | NONE0 | io.netty:netty-codec-haproxy 4.1.128.Final fixed in 4.2.15.Final, 4.1.135.Final | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-55851 | NONE0 | io.netty:netty-codec-haproxy 4.1.128.Final fixed in 4.2.16.Final, 4.1.136.Final | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-33870 | NONE0 | io.netty:netty-codec-http 4.1.128.Final fixed in 4.1.132.Final, 4.2.10.Final | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-42587 | NONE0 | io.netty:netty-codec-http 4.1.128.Final fixed in 4.2.13.Final, 4.1.133.Final | 1.0% Theoretical Threat | Not Applicable |
| CVE-2026-55831 | NONE0 | io.netty:netty-codec-http 4.1.128.Final fixed in 4.2.16.Final, 4.1.136.Final | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-55833 | NONE0 | io.netty:netty-codec-http 4.1.128.Final fixed in 4.2.16.Final, 4.1.136.Final | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-56745 | NONE0 | io.netty:netty-codec-http 4.1.128.Final fixed in 4.2.16.Final, 4.1.136.Final | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-42585 | NONE0 | io.netty:netty-codec-http 4.1.128.Final fixed in 4.2.13.Final, 4.1.133.Final | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-56746 | NONE0 | io.netty:netty-codec-http 4.1.128.Final fixed in 4.2.16.Final, 4.1.136.Final | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-59899 | NONE0 | io.netty:netty-codec-http 4.1.128.Final fixed in 4.2.16.Final, 4.1.136.Final | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-33871 | NONE0 | io.netty:netty-codec-http2 4.1.128.Final fixed in 4.1.132.Final, 4.2.11.Final | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-42587 | NONE0 | io.netty:netty-codec-http2 4.1.128.Final fixed in 4.2.13.Final, 4.1.133.Final | 1.0% Theoretical Threat | Not Applicable |
| CVE-2026-56819 | NONE0 | io.netty:netty-codec-http2 4.1.128.Final fixed in 4.2.16.Final, 4.1.136.Final | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-48043 | NONE0 | io.netty:netty-codec-http2 4.1.128.Final fixed in 4.1.135.Final, 4.2.15.Final | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-44248 | NONE0 | io.netty:netty-codec-mqtt 4.1.128.Final fixed in 4.2.13.Final, 4.1.133.Final | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-44250 | NONE0 | io.netty:netty-codec-redis 4.1.128.Final fixed in 4.2.15.Final, 4.1.135.Final | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-44890 | NONE0 | io.netty:netty-codec-redis 4.1.128.Final fixed in 4.2.15.Final, 4.1.135.Final | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-48006 | NONE0 | io.netty:netty-codec-redis 4.1.128.Final fixed in 4.2.15.Final, 4.1.135.Final | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-50011 | NONE0 | io.netty:netty-codec-redis 4.1.128.Final fixed in 4.2.15.Final, 4.1.135.Final | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-44891 | NONE0 | io.netty:netty-codec-stomp 4.1.128.Final fixed in 4.2.16.Final, 4.1.136.Final | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-45416 | NONE0 | io.netty:netty-handler 4.1.128.Final fixed in 4.2.15.Final, 4.1.135.Final | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-50010 | NONE0 | io.netty:netty-handler 4.1.128.Final fixed in 4.2.15.Final, 4.1.135.Final | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-42578 | NONE0 | io.netty:netty-handler-proxy 4.1.128.Final fixed in 4.1.133.Final, 4.2.13.Final | 1.0% Theoretical Threat | Not Applicable |
| CVE-2026-46340 | NONE0 | io.netty:netty-transport-sctp 4.1.128.Final fixed in 4.2.15.Final, 4.1.135.Final | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-45205 | NONE0 | org.apache.commons:commons-configuration2 2.11.0 fixed in 2.15.0 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-34479 | NONE0 | org.apache.logging.log4j:log4j-1.2-api 2.25.2 fixed in 2.25.4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-34478 | NONE0 | org.apache.logging.log4j:log4j-core 2.25.2 fixed in 2.25.4 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-34480 | NONE0 | org.apache.logging.log4j:log4j-core 2.25.2 fixed in 2.25.4 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2025-14813 | NONE0 | org.bouncycastle:bcprov-jdk18on 1.78.1 fixed in 1.80.2, 1.81.1, 1.84 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-1605 | NONE0 | org.eclipse.jetty:jetty-server 12.0.29 fixed in 12.1.6, 12.0.32 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-10051 | NONE0 | org.eclipse.jetty:jetty-server 12.0.29 fixed in 12.0.36, 12.1.10 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-33814 | NONE0 | golang.org/x/net v0.33.0 fixed in 0.53.0 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2025-61726 | NONE0 | stdlib v1.23.12 fixed in 1.24.12, 1.25.6 | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2025-61729 | NONE0 | stdlib v1.23.12 fixed in 1.24.11, 1.25.5 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-25679 | NONE0 | stdlib v1.23.12 fixed in 1.25.8, 1.26.1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-27145 | NONE0 | stdlib v1.23.12 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-32280 | NONE0 | stdlib v1.23.12 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-32281 | NONE0 | stdlib v1.23.12 fixed in 1.25.9, 1.26.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-32283 | NONE0 | stdlib v1.23.12 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-33811 | NONE0 | stdlib v1.23.12 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-33814 | NONE0 | stdlib v1.23.12 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-39820 | NONE0 | stdlib v1.23.12 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-39836 | NONE0 | stdlib v1.23.12 fixed in 1.25.10, 1.26.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-42499 | NONE0 | stdlib v1.23.12 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-42504 | NONE0 | stdlib v1.23.12 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-58183 | NONE0 | stdlib v1.23.12 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-61728 | NONE0 | stdlib v1.23.12 fixed in 1.24.12, 1.25.6 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-9547 | NONE0 | libcurl3-gnutls 7.81.0-1ubuntu1.21 fixed in 7.81.0-1ubuntu1.25 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-9547 | NONE0 | libcurl4 7.81.0-1ubuntu1.21 fixed in 7.81.0-1ubuntu1.25 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-3833 | NONE0 | libgnutls30 3.7.3-4ubuntu1.7 fixed in 3.7.3-4ubuntu1.9 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-42011 | NONE0 | libgnutls30 3.7.3-4ubuntu1.7 fixed in 3.7.3-4ubuntu1.9 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-34182 | NONE0 | libssl3 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.25 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69419 | NONE0 | libssl3 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.21 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40170 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2019-14899 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2025-40170 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2019-14899 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-56822 | NONE0 | io.netty:netty-handler-ssl-ocsp 4.1.128.Final fixed in 4.2.16.Final, 4.1.136.Final | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-29481 | NONE0 | libbpf0 1:0.5.0-1ubuntu22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43038 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31607 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43074 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43078 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-179.189 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53781 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40269 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40304 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68800 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23243 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43038 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31607 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43074 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43078 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-179.189 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53781 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40269 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40304 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68800 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23243 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-33412 | NONE0 | vim-common 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.27 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-41411 | NONE0 | vim-common 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.29 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-25749 | NONE0 | vim-common 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.26 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-33412 | NONE0 | vim-runtime 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.27 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-41411 | NONE0 | vim-runtime 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.29 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-25749 | NONE0 | vim-runtime 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.26 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-33412 | NONE0 | xxd 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.27 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-41411 | NONE0 | xxd 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.29 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-25749 | NONE0 | xxd 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.26 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-42012 | NONE0 | libgnutls30 3.7.3-4ubuntu1.7 fixed in 3.7.3-4ubuntu1.9 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-1299 | NONE0 | libpython3.10 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.16 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-4786 | NONE0 | libpython3.10 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.16 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-1299 | NONE0 | libpython3.10-minimal 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.16 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-4786 | NONE0 | libpython3.10-minimal 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.16 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-1299 | NONE0 | libpython3.10-stdlib 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.16 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-4786 | NONE0 | libpython3.10-stdlib 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.16 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46135 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-22984 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-23455 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-185.195 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2026-46259 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-49172 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49218 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49234 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49401 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49518 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49961 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50551 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52682 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52701 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53254 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53376 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53575 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53751 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-6610 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-14040 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-26954 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-35937 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35939 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36013 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-36915 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41013 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41935 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49861 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49928 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50164 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53147 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53216 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57945 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57982 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58015 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58054 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21946 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-21985 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22038 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-22039 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-22104 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22107 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22121 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37879 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-38081 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38329 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38330 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38340 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38556 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38679 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38728 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-39744 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39750 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39761 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39869 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39883 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39901 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39943 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40064 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40082 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40322 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40349 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40351 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68168 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68183 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68324 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68366 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68724 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71093 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71112 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71116 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-71133 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71136 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23076 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23099 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23204 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23235 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23315 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23318 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23388 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23397 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31568 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31614 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31685 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31778 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43040 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43051 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43052 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43141 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43241 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43281 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43386 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43427 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43449 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43450 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43453 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45893 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45957 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45994 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46022 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46033 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46053 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46056 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46064 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46120 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46150 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46191 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46209 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52968 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53138 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53149 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53179 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53303 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53309 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53330 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-41014 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43126 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43380 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43414 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53255 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46135 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-22984 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-23455 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-185.195 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2026-46259 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-49172 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49218 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49234 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49401 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49518 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49961 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50551 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52682 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52701 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53254 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53376 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53575 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53751 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-6610 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-14040 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-26954 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-35937 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35939 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36013 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-36915 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41013 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41935 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49861 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49928 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50164 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53147 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53216 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57945 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57982 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58015 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58054 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21946 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-21985 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22038 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-22039 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-22104 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22107 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22121 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37879 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-38081 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38329 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38330 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38340 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38556 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38679 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38728 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-39744 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39750 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39761 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39869 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39883 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39901 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39943 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40064 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40082 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40322 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40349 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40351 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68168 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68183 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68324 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68366 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68724 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71093 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71112 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71116 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-71133 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71136 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23076 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23099 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23204 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23235 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23315 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23318 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23388 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23397 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31568 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31614 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31685 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31778 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43040 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43051 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43052 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43141 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43241 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43281 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43386 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43427 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43449 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43450 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43453 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45893 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45957 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45994 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46022 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46033 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46053 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46056 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46064 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46120 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46150 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46191 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46209 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52968 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53138 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53149 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53179 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53303 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53309 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53330 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-41014 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43126 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43380 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43414 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53255 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-1299 | NONE0 | python3.10 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.16 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-4786 | NONE0 | python3.10 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.16 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-1299 | NONE0 | python3.10-minimal 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.16 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-4786 | NONE0 | python3.10-minimal 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.16 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-35177 | NONE0 | vim-common 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.33 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-35177 | NONE0 | vim-runtime 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.33 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-35177 | NONE0 | xxd 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.33 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-42586 | NONE0 | io.netty:netty-codec-redis 4.1.128.Final fixed in 4.2.13.Final, 4.1.133.Final | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68973 | NONE0 | gpgv 2.2.27-3ubuntu2.4 fixed in 2.2.27-3ubuntu2.5 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-4878 | NONE0 | libcap2 1:2.44-1ubuntu0.22.04.2 fixed in 1:2.44-1ubuntu0.22.04.3 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-5222 | NONE0 | libicu70 70.1-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43304 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46043 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-52989 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-52993 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53002 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-54518 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-23191 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23392 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31419 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-179.189 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31586 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31656 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31663 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31694 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43116 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43198 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43206 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43341 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43370 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43493 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-43494 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-181.191 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43503 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-181.191 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-45852 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46119 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46275 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46319 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52924 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53006 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53036 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53072 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53185 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53212 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53224 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53239 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53254 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53256 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53264 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53270 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53275 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-3864 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2022-1247 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-2961 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52586 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49855 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50106 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50286 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-57876 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37776 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-39759 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39826 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39905 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40135 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-40154 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40158 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40168 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40248 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40259 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40271 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-68285 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-68287 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68301 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-71203 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71221 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23050 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23054 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23270 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23454 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31408 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43050 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43158 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43226 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43233 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43334 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43339 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45856 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45859 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-45860 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-45942 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45970 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46015 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46052 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46054 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46090 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46099 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46116 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46123 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46133 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-46149 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46174 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46181 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46227 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46266 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46324 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52912 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52917 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52918 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-52920 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-52933 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52935 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52942 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52945 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-52947 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52956 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52957 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-52986 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-52991 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52998 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53000 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53005 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53009 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53011 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53016 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53049 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53075 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53091 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53131 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53133 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53223 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53228 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53246 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53268 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53354 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53355 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53357 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53381 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53384 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53388 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53391 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53392 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53397 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53398 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53399 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63800 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63801 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63807 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63808 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63809 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63823 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63824 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63826 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63829 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63830 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-63831 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63875 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63887 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-63888 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-63889 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63891 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63898 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63899 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63901 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63912 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-63913 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-63914 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63916 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63917 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63919 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-63920 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63921 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63922 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-63924 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-63925 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63928 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63940 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63947 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63956 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63957 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63958 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63962 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63971 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63975 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63984 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63992 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63993 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63994 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64001 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64002 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64007 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64009 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64011 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64015 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64018 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64025 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64026 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64032 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64034 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64047 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64048 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64098 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64102 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64109 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64111 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64113 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64114 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64115 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64137 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64174 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64189 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64191 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64192 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64255 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64266 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64268 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-64271 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64276 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64277 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64280 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64296 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64298 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64303 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-64304 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64305 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64306 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64312 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64317 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64320 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-64322 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64323 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64324 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64340 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64341 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64342 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64355 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64364 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64372 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64375 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64378 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64379 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64380 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64401 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64422 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64434 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64448 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64456 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64470 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64471 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64475 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64483 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64508 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64523 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64527 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64530 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64531 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64534 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64539 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64543 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64548 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64551 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64554 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64556 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64557 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64560 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-45885 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-21739 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31508 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45894 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53053 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53062 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53078 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53189 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53230 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53253 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43304 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46043 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-52989 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-52993 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53002 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-54518 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-23191 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23392 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31419 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-179.189 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31586 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31656 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31663 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31694 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43116 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43198 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43206 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43341 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43370 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43493 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-43494 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-181.191 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43503 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-181.191 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-45852 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46119 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46275 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46319 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52924 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53006 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53036 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53072 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53185 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53212 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53224 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53239 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53254 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53256 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53264 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53270 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53275 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-3864 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2022-1247 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-2961 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52586 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49855 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50106 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50286 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-57876 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37776 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-39759 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39826 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39905 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40135 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-40154 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40158 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40168 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40248 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40259 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40271 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-68285 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-68287 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68301 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-71203 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71221 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23050 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23054 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23270 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23454 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31408 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43050 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43158 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43226 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43233 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43334 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43339 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45856 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45859 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-45860 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-45942 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45970 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46015 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46052 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46054 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46090 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46099 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46116 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46123 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46133 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-46149 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46174 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46181 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46227 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46266 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46324 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52912 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52917 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52918 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-52920 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-52933 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52935 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52942 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52945 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-52947 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52956 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52957 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-52986 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-52991 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52998 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53000 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53005 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53009 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53011 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53016 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53049 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53075 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53091 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53131 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53133 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53223 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53228 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53246 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53268 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53354 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53355 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53357 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53381 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53384 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53388 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53391 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53392 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53397 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53398 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53399 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63800 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63801 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63807 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63808 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63809 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63823 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63824 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63826 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63829 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63830 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-63831 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63875 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63887 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-63888 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-63889 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63891 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63898 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63899 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63901 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63912 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-63913 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-63914 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63916 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63917 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63919 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-63920 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63921 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63922 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-63924 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-63925 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63928 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63940 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63947 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63956 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63957 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63958 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63962 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63971 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63975 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63984 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63992 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63993 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63994 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64001 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64002 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64007 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64009 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64011 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64015 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64018 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64025 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64026 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64032 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64034 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64047 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64048 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64098 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64102 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64109 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64111 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64113 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64114 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64115 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64137 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64174 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64189 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64191 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64192 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64255 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64266 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64268 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-64271 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64276 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64277 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64280 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64296 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64298 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64303 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-64304 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64305 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64306 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64312 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64317 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64320 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-64322 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64323 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64324 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64340 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64341 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64342 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64355 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64364 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64372 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64375 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64378 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64379 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64380 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64401 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64422 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64434 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64448 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64456 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64470 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64471 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64475 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64483 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64508 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64523 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64527 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64530 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64531 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64534 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64539 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64543 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64548 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64551 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64554 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64556 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64557 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64560 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-45885 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-21739 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31508 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45894 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53053 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53062 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53078 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53189 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53230 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53253 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46483 | NONE0 | vim-common 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.31 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-46483 | NONE0 | vim-runtime 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.31 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-46483 | NONE0 | xxd 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.31 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-1965 | NONE0 | libcurl3-gnutls 7.81.0-1ubuntu1.21 fixed in 7.81.0-1ubuntu1.23 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-1965 | NONE0 | libcurl4 7.81.0-1ubuntu1.21 fixed in 7.81.0-1ubuntu1.23 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-22185 | NONE0 | liblmdb0 0.9.24-1build2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-0938 | NONE0 | libpython2.7 2.7.18-13ubuntu1.5 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2025-0938 | NONE0 | libpython2.7-dev 2.7.18-13ubuntu1.5 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2025-0938 | NONE0 | libpython2.7-minimal 2.7.18-13ubuntu1.5 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2025-0938 | NONE0 | libpython2.7-stdlib 2.7.18-13ubuntu1.5 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2026-53196 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40345 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68346 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53196 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40345 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68346 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-0938 | NONE0 | python2.7 2.7.18-13ubuntu1.5 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2025-0938 | NONE0 | python2.7-dev 2.7.18-13ubuntu1.5 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2025-0938 | NONE0 | python2.7-minimal 2.7.18-13ubuntu1.5 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2026-45673 | NONE0 | io.netty:netty-resolver-dns 4.1.128.Final fixed in 4.2.15.Final, 4.1.135.Final | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46331 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-15794 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2022-50616 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53095 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40257 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-57795 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21714 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46331 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-15794 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2022-50616 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53095 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40257 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-57795 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21714 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-42014 | NONE0 | libgnutls30 3.7.3-4ubuntu1.7 fixed in 3.7.3-4ubuntu1.9 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21759 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 7.4% Low-Moderate Risk | Not Applicable |
| CVE-2022-50851 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40261 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-45991 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53267 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21759 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 7.4% Low-Moderate Risk | Not Applicable |
| CVE-2022-50851 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40261 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-45991 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53267 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-28419 | NONE0 | vim-common 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.26 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-28419 | NONE0 | vim-runtime 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.26 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-28419 | NONE0 | xxd 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.26 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-39979 | NONE0 | jq 1.6-2.1ubuntu3.1 fixed in 1.6-2.1ubuntu3.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-6238 | NONE0 | libc-bin 2.35-0ubuntu3.11 fixed in 2.35-0ubuntu3.14 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-6238 | NONE0 | libc-dev-bin 2.35-0ubuntu3.11 fixed in 2.35-0ubuntu3.14 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-6238 | NONE0 | libc6 2.35-0ubuntu3.11 fixed in 2.35-0ubuntu3.14 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-6238 | NONE0 | libc6-dev 2.35-0ubuntu3.11 fixed in 2.35-0ubuntu3.14 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-5545 | NONE0 | libcurl3-gnutls 7.81.0-1ubuntu1.21 fixed in 7.81.0-1ubuntu1.24 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-6429 | NONE0 | libcurl3-gnutls 7.81.0-1ubuntu1.21 fixed in 7.81.0-1ubuntu1.24 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-14524 | NONE0 | libcurl3-gnutls 7.81.0-1ubuntu1.21 fixed in 7.81.0-1ubuntu1.22 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-3784 | NONE0 | libcurl3-gnutls 7.81.0-1ubuntu1.21 fixed in 7.81.0-1ubuntu1.23 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-8924 | NONE0 | libcurl3-gnutls 7.81.0-1ubuntu1.21 fixed in 7.81.0-1ubuntu1.25 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-5545 | NONE0 | libcurl4 7.81.0-1ubuntu1.21 fixed in 7.81.0-1ubuntu1.24 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-6429 | NONE0 | libcurl4 7.81.0-1ubuntu1.21 fixed in 7.81.0-1ubuntu1.24 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-14524 | NONE0 | libcurl4 7.81.0-1ubuntu1.21 fixed in 7.81.0-1ubuntu1.22 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-3784 | NONE0 | libcurl4 7.81.0-1ubuntu1.21 fixed in 7.81.0-1ubuntu1.23 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-8924 | NONE0 | libcurl4 7.81.0-1ubuntu1.21 fixed in 7.81.0-1ubuntu1.25 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-34969 | NONE0 | libdbus-1-3 1.12.20-2ubuntu4.1 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2025-14512 | NONE0 | libglib2.0-0 2.72.4-0ubuntu2.6 fixed in 2.72.4-0ubuntu2.7 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-39979 | NONE0 | libjq1 1.6-2.1ubuntu3.1 fixed in 1.6-2.1ubuntu3.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | libncurses6 6.3-2ubuntu0.1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | libncursesw6 6.3-2ubuntu0.1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | libtinfo6 6.3-2ubuntu0.1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2026-53176 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2015-8553 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-1193 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-53785 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39969 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40273 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40336 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68284 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-68354 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68362 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23179 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31588 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64535 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-0564 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-53176 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2015-8553 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-1193 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-53785 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39969 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40273 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40336 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68284 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-68354 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68362 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23179 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31588 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64535 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-0564 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-21968 | NONE0 | mysql-client-8.0 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.45-0ubuntu0.22.04.1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-22009 | NONE0 | mysql-client-8.0 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-22017 | NONE0 | mysql-client-8.0 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-34270 | NONE0 | mysql-client-8.0 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-34271 | NONE0 | mysql-client-8.0 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-34276 | NONE0 | mysql-client-8.0 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-34303 | NONE0 | mysql-client-8.0 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-34308 | NONE0 | mysql-client-8.0 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-21968 | NONE0 | mysql-client-core-8.0 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.45-0ubuntu0.22.04.1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-22009 | NONE0 | mysql-client-core-8.0 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-22017 | NONE0 | mysql-client-core-8.0 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-34270 | NONE0 | mysql-client-core-8.0 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-34271 | NONE0 | mysql-client-core-8.0 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-34276 | NONE0 | mysql-client-core-8.0 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-34303 | NONE0 | mysql-client-core-8.0 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-34308 | NONE0 | mysql-client-core-8.0 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | ncurses-base 6.3-2ubuntu0.1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | ncurses-bin 6.3-2ubuntu0.1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2026-59888 | NONE0 | com.fasterxml.jackson.core:jackson-databind 2.16.0 fixed in 2.18.8, 2.21.4 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-67735 | NONE0 | io.netty:netty-codec-http 4.1.128.Final fixed in 4.2.8.Final, 4.1.129.Final | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-41417 | NONE0 | io.netty:netty-codec-http 4.1.128.Final fixed in 4.1.133.Final, 4.2.13.Final | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-42580 | NONE0 | io.netty:netty-codec-http 4.1.128.Final fixed in 4.2.13.Final, 4.1.133.Final | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-59900 | NONE0 | io.netty:netty-codec-http2 4.1.128.Final fixed in 4.2.16.Final, 4.1.136.Final | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-59920 | NONE0 | io.netty:netty-codec-stomp 4.1.128.Final fixed in 4.2.16.Final, 4.1.136.Final | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-0636 | NONE0 | org.bouncycastle:bcprov-jdk18on 1.78.1 fixed in 1.84 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-11143 | NONE0 | org.eclipse.jetty:jetty-http 12.0.29 fixed in 12.0.31, 12.1.5 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22872 | NONE0 | golang.org/x/net v0.33.0 fixed in 0.38.0 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-25680 | NONE0 | golang.org/x/net v0.33.0 fixed in 0.55.0 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-61727 | NONE0 | stdlib v1.23.12 fixed in 1.24.11, 1.25.5 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39825 | NONE0 | stdlib v1.23.12 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-40225 | NONE0 | libsystemd0 249.11-0ubuntu3.17 fixed in 249.11-0ubuntu3.19 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-40226 | NONE0 | libsystemd0 249.11-0ubuntu3.17 fixed in 249.11-0ubuntu3.21 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-40225 | NONE0 | libudev1 249.11-0ubuntu3.17 fixed in 249.11-0ubuntu3.19 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-40226 | NONE0 | libudev1 249.11-0ubuntu3.17 fixed in 249.11-0ubuntu3.21 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23450 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-31502 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31516 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52910 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53033 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53090 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39978 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40074 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40309 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40321 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68371 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23456 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-44032 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-44033 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-44034 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-45888 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-23450 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-31502 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31516 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52910 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53033 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53090 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39978 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40074 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40309 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40321 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68371 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23456 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-44032 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-44033 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-44034 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-45888 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-32282 | NONE0 | stdlib v1.23.12 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-0964 | NONE0 | libssh-4 0.9.6-2ubuntu0.22.04.5 fixed in 0.9.6-2ubuntu0.22.04.6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31504 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-179.189 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-40918 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-57893 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40307 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68282 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31504 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-179.189 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-40918 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-57893 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40307 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68282 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-5958 | NONE0 | sed 4.8-1ubuntu2 fixed in 4.8-1ubuntu2.1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-13757 | NONE0 | libp11-kit0 0.24.0-6build1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-0450 | NONE0 | libpython2.7 2.7.18-13ubuntu1.5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-0450 | NONE0 | libpython2.7-dev 2.7.18-13ubuntu1.5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-0450 | NONE0 | libpython2.7-minimal 2.7.18-13ubuntu1.5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-0450 | NONE0 | libpython2.7-stdlib 2.7.18-13ubuntu1.5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-23253 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-54081 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40048 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-40146 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68757 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71066 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23253 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-54081 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40048 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-40146 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68757 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71066 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-0450 | NONE0 | python2.7 2.7.18-13ubuntu1.5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-0450 | NONE0 | python2.7-dev 2.7.18-13ubuntu1.5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-0450 | NONE0 | python2.7-minimal 2.7.18-13ubuntu1.5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39956 | NONE0 | jq 1.6-2.1ubuntu3.1 fixed in 1.6-2.1ubuntu3.2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-39956 | NONE0 | libjq1 1.6-2.1ubuntu3.1 fixed in 1.6-2.1ubuntu3.2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6019 | NONE0 | libpython3.10 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.16 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6019 | NONE0 | libpython3.10-minimal 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.16 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6019 | NONE0 | libpython3.10-stdlib 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.16 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40190 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31449 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31700 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31708 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52829 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-53850 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40019 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-168.178 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40071 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40080 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40279 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40355 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68245 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68342 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68343 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68736 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68764 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68815 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68819 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43134 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31464 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31570 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40190 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31449 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31700 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31708 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52829 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-53850 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40019 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-168.178 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40071 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40080 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40279 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40355 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68245 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68342 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68343 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68736 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68764 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68815 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68819 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43134 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31464 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31570 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-6019 | NONE0 | python3.10 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.16 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6019 | NONE0 | python3.10-minimal 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.16 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-42502 | NONE0 | golang.org/x/net v0.33.0 fixed in 0.55.0 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-32289 | NONE0 | stdlib v1.23.12 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49465 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52481 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-31649 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-49465 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52481 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-31649 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-26306 | NONE0 | iperf3 3.9-1+deb11u1build0.22.04.1 fixed in 3.9-1+deb11u1ubuntu0.1 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2025-15281 | NONE0 | libc-bin 2.35-0ubuntu3.11 fixed in 2.35-0ubuntu3.13 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-5435 | NONE0 | libc-bin 2.35-0ubuntu3.11 fixed in 2.35-0ubuntu3.14 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-15281 | NONE0 | libc-dev-bin 2.35-0ubuntu3.11 fixed in 2.35-0ubuntu3.13 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-5435 | NONE0 | libc-dev-bin 2.35-0ubuntu3.11 fixed in 2.35-0ubuntu3.14 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-15281 | NONE0 | libc6 2.35-0ubuntu3.11 fixed in 2.35-0ubuntu3.13 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-5435 | NONE0 | libc6 2.35-0ubuntu3.11 fixed in 2.35-0ubuntu3.14 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-15281 | NONE0 | libc6-dev 2.35-0ubuntu3.11 fixed in 2.35-0ubuntu3.13 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-5435 | NONE0 | libc6-dev 2.35-0ubuntu3.11 fixed in 2.35-0ubuntu3.14 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-2236 | NONE0 | libgcrypt20 1.9.4-3ubuntu3 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2024-26306 | NONE0 | libiperf0 3.9-1+deb11u1build0.22.04.1 fixed in 3.9-1+deb11u1ubuntu0.1 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-9669 | NONE0 | libpython3.10 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.16 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-9669 | NONE0 | libpython3.10-minimal 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.16 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-9669 | NONE0 | libpython3.10-stdlib 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.16 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31790 | NONE0 | libssl3 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.23 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2025-69420 | NONE0 | libssl3 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.21 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-22796 | NONE0 | libssl3 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.21 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-42770 | NONE0 | libssl3 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.25 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-9076 | NONE0 | libssl3 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.25 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-7008 | NONE0 | libsystemd0 249.11-0ubuntu3.17 fixed in 249.11-0ubuntu3.21 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2025-13151 | NONE0 | libtasn1-6 4.18.0-4ubuntu0.1 fixed in 4.18.0-4ubuntu0.2 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2023-7008 | NONE0 | libudev1 249.11-0ubuntu3.17 fixed in 249.11-0ubuntu3.21 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-0990 | NONE0 | libxml2 2.9.13+dfsg-1ubuntu0.10 fixed in 2.9.13+dfsg-1ubuntu0.11 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2021-3714 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2023-53764 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40083 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40242 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40324 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-1121 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 4.2% Low-Moderate Risk | Not Applicable |
| CVE-2024-35870 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-3714 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2023-53764 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40083 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40242 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40324 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-1121 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 4.2% Low-Moderate Risk | Not Applicable |
| CVE-2024-35870 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-9669 | NONE0 | python3.10 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.16 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-9669 | NONE0 | python3.10-minimal 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.16 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-34477 | NONE0 | org.apache.logging.log4j:log4j-core 2.25.2 fixed in 2.25.4 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-23240 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-23271 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31414 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-53789 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54107 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39994 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39998 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40111 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40118 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40167 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40194 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40237 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40272 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40323 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40340 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68742 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23239 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31426 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43279 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46065 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46113 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52923 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31392 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23240 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-23271 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31414 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-53789 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54107 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39994 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39998 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40111 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40118 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40167 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40194 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40237 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40272 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40323 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40340 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68742 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23239 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31426 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43279 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46065 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46113 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52923 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31392 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-53864 | NONE0 | com.nimbusds:nimbus-jose-jwt 10.0.1 fixed in 10.0.2, 9.37.4 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-3783 | NONE0 | libcurl3-gnutls 7.81.0-1ubuntu1.21 fixed in 7.81.0-1ubuntu1.23 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-3783 | NONE0 | libcurl4 7.81.0-1ubuntu1.21 fixed in 7.81.0-1ubuntu1.23 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49138 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49569 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40319 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46024 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-49138 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49569 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40319 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46024 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-59921 | NONE0 | io.netty:netty-codec-http 4.1.128.Final fixed in 4.2.16.Final, 4.1.136.Final | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-56821 | NONE0 | io.netty:netty-handler-ssl-ocsp 4.1.128.Final fixed in 4.2.16.Final, 4.1.136.Final | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-36350 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-36357 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-68801 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68816 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36350 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-36357 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-68801 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68816 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69651 | NONE0 | binutils-common 2.38-4ubuntu2.12 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2017-13716 | NONE0 | binutils-common 2.38-4ubuntu2.12 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010204 | NONE0 | binutils-common 2.38-4ubuntu2.12 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2022-27943 | NONE0 | binutils-common 2.38-4ubuntu2.12 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2022-48064 | NONE0 | binutils-common 2.38-4ubuntu2.12 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-69651 | NONE0 | binutils-x86-64-linux-gnu 2.38-4ubuntu2.12 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2017-13716 | NONE0 | binutils-x86-64-linux-gnu 2.38-4ubuntu2.12 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010204 | NONE0 | binutils-x86-64-linux-gnu 2.38-4ubuntu2.12 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2022-27943 | NONE0 | binutils-x86-64-linux-gnu 2.38-4ubuntu2.12 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2022-48064 | NONE0 | binutils-x86-64-linux-gnu 2.38-4ubuntu2.12 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2022-27943 | NONE0 | gcc-12-base 12.3.0-1ubuntu1~22.04.2 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-33947 | NONE0 | jq 1.6-2.1ubuntu3.1 fixed in 1.6-2.1ubuntu3.2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-41256 | NONE0 | jq 1.6-2.1ubuntu3.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-41257 | NONE0 | jq 1.6-2.1ubuntu3.1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43896 | NONE0 | jq 1.6-2.1ubuntu3.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-44777 | NONE0 | jq 1.6-2.1ubuntu3.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69651 | NONE0 | libbinutils 2.38-4ubuntu2.12 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2017-13716 | NONE0 | libbinutils 2.38-4ubuntu2.12 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010204 | NONE0 | libbinutils 2.38-4ubuntu2.12 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2022-27943 | NONE0 | libbinutils 2.38-4ubuntu2.12 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2022-48064 | NONE0 | libbinutils 2.38-4ubuntu2.12 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-69651 | NONE0 | libctf-nobfd0 2.38-4ubuntu2.12 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2017-13716 | NONE0 | libctf-nobfd0 2.38-4ubuntu2.12 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010204 | NONE0 | libctf-nobfd0 2.38-4ubuntu2.12 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2022-27943 | NONE0 | libctf-nobfd0 2.38-4ubuntu2.12 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2022-48064 | NONE0 | libctf-nobfd0 2.38-4ubuntu2.12 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-69651 | NONE0 | libctf0 2.38-4ubuntu2.12 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2017-13716 | NONE0 | libctf0 2.38-4ubuntu2.12 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010204 | NONE0 | libctf0 2.38-4ubuntu2.12 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2022-27943 | NONE0 | libctf0 2.38-4ubuntu2.12 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2022-48064 | NONE0 | libctf0 2.38-4ubuntu2.12 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-66382 | NONE0 | libexpat1 2.4.7-1ubuntu0.6 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-66382 | NONE0 | libexpat1-dev 2.4.7-1ubuntu0.6 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-27943 | NONE0 | libgcc-s1 12.3.0-1ubuntu1~22.04.2 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-33947 | NONE0 | libjq1 1.6-2.1ubuntu3.1 fixed in 1.6-2.1ubuntu3.2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-41256 | NONE0 | libjq1 1.6-2.1ubuntu3.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-41257 | NONE0 | libjq1 1.6-2.1ubuntu3.1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43896 | NONE0 | libjq1 1.6-2.1ubuntu3.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-44777 | NONE0 | libjq1 1.6-2.1ubuntu3.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-13837 | NONE0 | libpython3.10 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.14 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-13837 | NONE0 | libpython3.10-minimal 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.14 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-13837 | NONE0 | libpython3.10-stdlib 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.14 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-0967 | NONE0 | libssh-4 0.9.6-2ubuntu0.22.04.5 fixed in 0.9.6-2ubuntu0.22.04.6 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-22795 | NONE0 | libssl3 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.21 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-7383 | NONE0 | libssl3 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.25 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2022-27943 | NONE0 | libstdc++6 12.3.0-1ubuntu1~22.04.2 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-31637 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-45988 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-56692 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71315 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23066 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23105 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23222 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23273 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-177.187 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23340 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23351 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-179.189 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23391 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23449 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31403 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31447 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31454 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31469 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31473 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31507 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31548 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31665 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31673 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31678 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31680 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31758 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43009 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43016 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43030 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43033 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-179.189 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43060 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43091 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43093 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43111 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43153 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43214 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43365 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43406 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43407 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43437 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43456 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43502 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45850 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45864 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45899 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46273 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46304 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46320 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52909 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52958 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53050 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53086 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53159 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53269 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2015-7837 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2016-8660 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-4095 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-47432 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47658 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-0480 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-38457 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-40133 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-4543 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2022-48628 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48633 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48673 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48706 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48766 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48887 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48929 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48976 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48979 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49069 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49108 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49123 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49124 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49125 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49133 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49134 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49161 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49167 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49173 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49177 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49178 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49203 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49245 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49296 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49303 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49306 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49317 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49333 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49342 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49393 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49420 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49469 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49476 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49484 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49496 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49504 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49516 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49528 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49529 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49531 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49533 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49534 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49539 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49543 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49547 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49552 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49562 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49622 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49699 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49742 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-49750 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-49759 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-49764 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49766 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-49773 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-49783 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-49803 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49810 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-49829 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-49833 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-49858 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-49901 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-49932 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49940 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49943 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-49955 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49965 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49971 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49974 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49997 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50002 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50009 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50015 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50016 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50073 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50116 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50166 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50167 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50178 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50195 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50224 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50230 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50232 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50236 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50260 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50266 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50284 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50304 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50316 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50322 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50332 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50354 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50357 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50380 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50383 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50390 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50393 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50407 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50418 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50425 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50461 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50464 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50467 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50479 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50500 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50527 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50539 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50550 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50554 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50571 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50627 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50704 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50746 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50748 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50772 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50815 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50862 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50863 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50871 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-0160 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31082 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-52485 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52569 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52576 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52582 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52590 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52591 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52625 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52632 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52634 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52648 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52653 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52657 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52660 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52671 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52673 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52676 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52700 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52732 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52737 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52761 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52831 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52857 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52879 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52888 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52905 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52920 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52939 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52981 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53002 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53008 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53009 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53010 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53036 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53042 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53068 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53093 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53105 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53115 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53149 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53152 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53168 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53180 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53198 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53209 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53221 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53231 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53240 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53247 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53248 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53258 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53261 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53292 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53323 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53325 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53332 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53347 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53348 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53353 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53355 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53362 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53366 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53367 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53370 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53371 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53382 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53383 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53385 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53387 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53410 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53421 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53424 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53429 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53434 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53438 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53460 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53466 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53483 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53491 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53509 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53529 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53538 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53539 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53540 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53545 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53547 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53558 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53561 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53562 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53574 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53584 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53588 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53602 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53609 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53620 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53627 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53628 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53635 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53647 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53651 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53657 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53662 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53671 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53682 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53685 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53694 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53702 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53721 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53743 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53753 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53765 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53767 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53780 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53806 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53822 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53829 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53846 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53849 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53867 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54002 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54016 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54019 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54023 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54028 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54052 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54067 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54088 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54121 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54129 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54190 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54234 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54237 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54242 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54259 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54271 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54280 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54324 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-14027 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26595 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26605 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26647 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26656 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26658 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-26691 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26714 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26719 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26740 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26756 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26759 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26767 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26770 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26807 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26844 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26853 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26866 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26876 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26938 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26948 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26953 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27002 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27005 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27014 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27025 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27032 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27035 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27041 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27056 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27057 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27062 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27389 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27400 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27418 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27435 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35784 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35794 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35799 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35801 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35803 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35808 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35826 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35832 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35839 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35843 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35865 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35875 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35878 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-35908 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35924 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35926 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35931 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35942 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35945 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35946 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35956 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35959 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-35971 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35995 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35998 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35999 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36000 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36009 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36021 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36026 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36244 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36478 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-36479 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36900 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36903 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36909 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36911 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36917 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36918 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36920 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36922 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36924 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36948 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36951 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36966 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-37021 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38543 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38554 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38557 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38564 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38594 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38608 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38625 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39282 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39298 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-40966 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40972 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-40975 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40977 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-40979 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40998 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40999 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41001 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41008 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41023 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41030 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41031 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41036 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41062 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41067 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41075 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41079 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41082 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41088 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42067 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42091 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42110 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42122 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42125 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42128 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42129 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42139 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42239 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42273 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42319 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42320 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42321 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43823 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43824 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43831 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43832 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43844 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43872 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-43899 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43911 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43912 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44950 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44961 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44962 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44963 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44970 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-45010 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-45015 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46678 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46681 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46705 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46715 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46716 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46717 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46718 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46720 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46726 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46727 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46728 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46730 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46733 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46748 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46749 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46754 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46762 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46765 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46770 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46775 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46802 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46803 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46806 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46808 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46823 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46834 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46835 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46842 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46843 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46848 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46857 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46860 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46861 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47141 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47658 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47661 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47662 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47664 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47666 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47678 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47683 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47703 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47704 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47728 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47736 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47794 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47809 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-48873 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49568 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49870 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49888 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49891 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49893 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49898 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49899 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49901 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49904 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49905 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49906 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49908 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49909 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49910 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49911 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49912 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49914 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49915 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49916 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49917 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49918 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49919 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49920 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49921 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49922 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49923 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49929 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49932 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49939 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49940 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49945 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49970 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49978 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49987 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49988 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49990 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49994 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50012 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50014 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50017 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50028 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50034 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50048 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50056 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50060 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-179.189 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50098 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50138 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50146 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50166 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50187 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50271 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50284 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50285 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50289 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50298 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-52559 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-52560 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53056 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53079 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53091 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53114 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53175 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53187 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53190 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53195 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53196 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53210 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53219 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53220 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53221 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53224 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53234 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53687 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-54683 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56368 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56544 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56557 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56565 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56566 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56583 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56584 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56588 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56591 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56592 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56607 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56611 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56639 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56641 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56647 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56657 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56660 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56665 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56671 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56677 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-56703 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56707 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56709 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56712 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56717 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56718 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56719 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56722 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56727 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56782 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57804 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57809 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57843 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57852 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57872 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57875 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57888 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57895 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57924 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57950 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57952 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57975 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57976 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57993 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57999 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58011 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58012 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58018 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58019 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58053 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58077 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58089 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58094 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58095 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58096 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58097 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58098 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58100 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58238 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-58241 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21629 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-21634 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21635 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21649 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21656 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21658 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21667 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21672 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21673 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-21682 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21696 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21712 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21723 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21730 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21738 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21750 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21752 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21768 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21792 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21801 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21816 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21817 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21819 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21821 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21831 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21832 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21833 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21838 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21861 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21872 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21881 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21885 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-21891 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21894 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21899 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21908 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21918 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21931 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21944 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21955 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-21972 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21976 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21986 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-22019 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22026 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22028 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22037 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 65.7% Actively Exploited | Not Applicable |
| CVE-2025-22042 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-22043 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-22053 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-22057 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22058 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22072 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22090 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22103 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22105 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22109 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22111 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22113 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22124 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22125 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22127 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-23130 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23131 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23132 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23141 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23143 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23155 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23160 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23162 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37743 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37744 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37745 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37746 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37747 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37775 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37806 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37807 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37820 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37833 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37834 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37842 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37852 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37853 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37855 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37856 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37870 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37876 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37877 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37878 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37880 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37884 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37907 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37931 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37938 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37945 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37951 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37954 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37956 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37959 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37961 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37980 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37984 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38006 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38011 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38014 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38015 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38020 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38029 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38033 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38036 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38038 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38039 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38040 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38041 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38042 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38045 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38047 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38057 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-38059 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38060 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38062 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38063 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38064 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38070 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38071 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38080 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38092 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-38096 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38097 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38098 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38099 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38105 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38125 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38126 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38127 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38140 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38162 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38166 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38168 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38189 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38191 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2025-38192 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38199 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38202 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38205 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38207 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38208 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38215 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38225 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38244 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38261 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38264 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-38269 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38272 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38275 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38300 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38321 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38331 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-38333 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38334 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38343 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38353 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38359 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38360 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38368 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38373 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38408 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38409 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38426 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38436 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38438 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38449 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38491 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38503 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38507 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38520 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38531 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38544 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38560 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38562 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 7.6% Low-Moderate Risk | Not Applicable |
| CVE-2025-38590 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-38591 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38615 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38621 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38626 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38643 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38644 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38659 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38665 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38692 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38705 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38709 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38710 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38716 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39677 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39692 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39705 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39706 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39707 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39715 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39716 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39720 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-39732 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39745 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39746 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39747 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39748 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39753 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39762 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39763 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39764 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39770 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-39771 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39779 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39781 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39789 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39800 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39819 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39827 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39829 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39833 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39838 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39850 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39851 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-39876 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39885 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39886 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39907 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39908 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39923 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39925 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39929 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-39931 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39932 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-39933 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39934 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39937 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39940 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39942 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-39947 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39949 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39953 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39989 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39990 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40005 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40020 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40026 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40027 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40029 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40030 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40040 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40042 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40044 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40049 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40053 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-40057 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40070 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40075 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40078 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40088 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40092 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40094 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40099 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40100 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40102 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40103 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40104 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40105 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40109 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40115 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40125 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40140 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40153 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40160 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40164 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40171 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40195 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40196 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40205 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40211 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40219 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40231 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40251 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40253 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40264 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40280 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40283 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40284 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40287 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40305 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40325 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40334 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40339 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40346 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40347 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-40360 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40362 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40363 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68171 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68173 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68176 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68178 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68185 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68188 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68192 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-68193 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68194 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68200 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68204 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68206 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-68211 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68219 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68223 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68227 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68229 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68231 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68236 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68244 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68261 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-68265 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68281 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68283 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-68288 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68295 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68297 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68307 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68308 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68309 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68310 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68313 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68317 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68321 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-68331 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68333 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68334 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68336 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-68337 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-68340 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68345 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68358 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68363 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68365 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-68372 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68378 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68379 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68725 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68732 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68734 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68758 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68774 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-68776 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68778 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68780 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68783 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68785 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68794 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-68795 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68798 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68802 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68803 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-68813 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68814 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68818 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-68820 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68821 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68822 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71064 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71077 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71079 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71081 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71083 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71084 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71085 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71087 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71094 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71095 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71096 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71097 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71098 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71102 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71104 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71105 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71107 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71108 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71109 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71113 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71114 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71115 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71118 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71120 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-71121 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71125 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71127 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71131 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71132 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71147 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71150 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71154 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71158 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71160 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71161 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-71163 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71180 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71182 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71183 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-71184 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71185 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71186 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71188 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71190 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71191 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71194 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71202 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71204 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-71222 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71223 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71227 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71229 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71232 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71233 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71235 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71236 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71237 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71239 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71265 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71266 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71267 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71268 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71269 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71272 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71273 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71285 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71287 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71289 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-71290 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71291 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71292 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-71293 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71294 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71295 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71297 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71299 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71300 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71302 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22976 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22977 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22979 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22982 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22990 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-22991 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-22992 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-22996 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-22997 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-22999 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23000 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23003 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-23011 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23019 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23020 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23021 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23026 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23031 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23038 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23047 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23058 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23060 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-174.184 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23061 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23063 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23064 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23069 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23075 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23080 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23084 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23085 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23086 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23087 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23088 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23090 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23091 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23093 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23095 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23096 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23097 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23100 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23108 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23113 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23119 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23120 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23121 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23124 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23125 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23128 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23133 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23137 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23138 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23141 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23145 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23146 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23150 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23154 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23157 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23164 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23170 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23190 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23196 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23202 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23206 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23213 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23214 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23215 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23217 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23220 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23228 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23229 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23236 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23237 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23238 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23241 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23242 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-23247 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23255 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23256 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23257 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23258 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23259 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23260 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23261 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23264 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23265 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23266 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23267 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23272 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23274 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-179.189 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23276 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23277 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23278 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23279 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23285 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23286 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23287 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23289 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23290 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23291 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23292 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23293 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23296 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23298 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23300 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23303 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23304 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23307 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23310 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23312 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23324 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23330 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23334 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23335 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23339 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23347 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23352 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23356 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23357 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23362 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23365 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23367 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23368 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23370 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23371 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23374 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23379 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23381 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23382 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23389 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23396 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23398 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23399 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23401 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23403 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23404 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23405 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23409 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23420 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23434 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23438 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23439 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23442 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23446 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23460 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23462 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-23465 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23468 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23472 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23474 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31391 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31394 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31400 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31407 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31410 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31411 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31412 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31415 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31416 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31418 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31420 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31421 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31422 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31423 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31424 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31425 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31427 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31428 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31441 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31450 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31451 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31461 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31462 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31467 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31480 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31483 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31486 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31487 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31492 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31495 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31496 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31497 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31498 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31503 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31509 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31510 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31512 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31515 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31518 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31519 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31520 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31521 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31522 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31524 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31531 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31533 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-179.189 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31537 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31540 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31545 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31546 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31549 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31550 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31551 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31552 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31555 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31557 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31560 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31565 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31577 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31579 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31585 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31590 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31592 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31594 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31595 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31596 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31599 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31603 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31605 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31606 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31610 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31615 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31616 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31617 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31618 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31619 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31623 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31624 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31625 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31628 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31630 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31634 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31642 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31651 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31658 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31660 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31661 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31662 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31664 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31670 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31671 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31672 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31674 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31675 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31676 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31677 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31679 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31681 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31682 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31684 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31687 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31692 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31698 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31699 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31701 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31704 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31721 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31722 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31723 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31724 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31725 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31726 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31737 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31738 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31749 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31752 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31754 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31755 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31756 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31762 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31763 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31767 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31770 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31773 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31777 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31781 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43014 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43021 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43022 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43024 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43025 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43026 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43028 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43032 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43035 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43036 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43041 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43042 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43043 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43045 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43046 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43048 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43054 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43058 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43061 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43062 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43064 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43065 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43066 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43068 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43069 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43072 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43073 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43077 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-179.189 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43079 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43080 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43085 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43088 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43089 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43098 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43099 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43101 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43103 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43104 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43105 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43107 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43109 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43113 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43115 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43118 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43119 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43123 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43124 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43127 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43129 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43130 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43131 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43132 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43135 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43136 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43137 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43139 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43140 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43143 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43145 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43147 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43148 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43149 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43152 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43156 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43159 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43161 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43162 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43165 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43167 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43168 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43170 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43171 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43172 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43173 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43182 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43183 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43187 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43189 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43191 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43194 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43195 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43200 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43201 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43202 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43204 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43209 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43213 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43216 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43218 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43219 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43220 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43223 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43225 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43227 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43228 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43230 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43231 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43234 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43242 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43243 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43244 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43246 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43251 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43253 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43255 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43257 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43261 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43262 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43264 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43266 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43267 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43268 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43269 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43270 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43271 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43273 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43277 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43287 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43288 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43289 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43292 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43294 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43295 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43296 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43298 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43299 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43300 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43302 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43305 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43306 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43308 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43309 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43310 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43311 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43312 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43313 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43314 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43315 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43316 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43317 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43318 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43319 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43320 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43327 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43333 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43338 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43340 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43343 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43344 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43350 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43355 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43357 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43359 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43361 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43362 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43363 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43381 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43382 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43387 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43398 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43400 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43405 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43409 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43410 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43411 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43413 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43416 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43419 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43421 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43424 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43425 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43428 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43429 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43432 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43436 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43445 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43451 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43452 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43459 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43466 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43469 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43471 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43472 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43473 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43474 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43475 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43483 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43491 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43492 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43496 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45834 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45835 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45836 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45840 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45842 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45843 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-45846 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45847 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45848 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45855 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45857 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45873 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45890 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45904 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45912 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45915 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45917 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45919 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45923 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45924 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45930 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45934 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45940 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45941 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45944 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45948 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45954 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45960 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45961 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45964 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45965 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45968 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45969 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45974 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45978 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45981 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45983 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45985 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45986 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45987 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45997 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45999 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46000 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46002 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46003 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46009 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46012 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46014 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46018 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46019 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46021 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46023 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46026 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46027 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46028 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-179.189 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46032 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46037 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46038 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46040 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46044 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46046 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46049 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46050 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46051 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46059 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46070 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46072 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46077 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46078 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46080 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46082 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46083 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46086 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46088 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46091 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46092 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46098 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46101 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46102 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46103 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46107 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46108 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46127 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46128 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46132 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46137 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46146 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46151 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46153 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46157 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46158 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46160 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46161 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46167 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46168 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46169 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46170 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46172 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46178 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46184 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46186 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46193 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46196 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46200 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46214 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46220 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46225 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46226 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46229 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46231 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46233 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46235 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46236 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46247 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46302 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46303 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46321 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46322 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52913 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52915 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52916 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52921 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52925 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52926 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52927 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52928 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52929 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52930 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52936 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52937 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52939 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52944 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52946 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-52948 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52954 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-52960 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52963 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52970 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52972 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52975 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52977 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52981 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-52984 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52985 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52988 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52990 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52995 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52999 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53001 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53003 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53012 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53015 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53017 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53018 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53021 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53022 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53023 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53034 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53037 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53039 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53056 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53064 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53066 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53069 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53074 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53076 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53077 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53080 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53083 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53088 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53107 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53122 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53128 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53134 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53139 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53150 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53167 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53168 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53181 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53199 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53208 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53218 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53219 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53220 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53221 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53227 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53245 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53252 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53263 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53284 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53287 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53289 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53291 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53292 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53295 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53304 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53306 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53313 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53314 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53317 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53320 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53325 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53327 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53331 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53332 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53337 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53339 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53345 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53349 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53353 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53358 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53369 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53376 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53377 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53379 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53382 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53385 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53393 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53400 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53402 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53403 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63798 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63803 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63810 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63822 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63832 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63858 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63860 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63865 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63867 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63868 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63870 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63872 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63890 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63892 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63893 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-63897 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63900 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63902 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63903 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63904 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63926 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63927 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63942 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63948 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63961 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63963 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63964 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63973 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63976 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-63983 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63985 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63990 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63991 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63999 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64004 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64005 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64006 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64012 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64014 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64039 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64046 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64076 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64077 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64078 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64079 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64103 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64106 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64112 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64116 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64118 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64123 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64125 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-64126 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64133 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64144 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64153 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64155 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64170 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64173 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64176 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64177 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64178 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64179 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64185 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64187 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64190 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64206 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64210 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64212 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64213 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64220 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64222 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64225 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64227 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64231 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64237 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64243 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64245 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64275 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64279 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64294 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64299 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64301 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64313 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64315 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64316 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64329 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64330 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64332 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64333 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64334 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64335 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64336 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64338 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64343 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64344 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64346 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64347 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64351 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64352 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64360 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64362 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64363 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64370 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64373 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64374 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64381 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64388 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64403 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64405 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64406 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64408 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64411 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64412 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64413 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64423 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64424 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64428 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64430 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64435 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64436 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64452 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64454 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64455 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64463 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64465 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64478 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64487 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64488 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64496 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64507 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64510 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64512 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64513 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64514 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64524 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64529 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64537 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64540 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64541 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64544 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64545 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64546 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64547 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64553 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2017-13693 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-12928 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-12929 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-3114 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49651 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-4133 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27010 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27011 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49968 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50009 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53093 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58237 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21645 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21693 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37800 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71304 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71313 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23103 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23198 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23336 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23444 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31446 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31448 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31453 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31667 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31771 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43071 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43180 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43211 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43352 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43353 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43480 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43484 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45838 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45841 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45844 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45858 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45862 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45868 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45869 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45870 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45871 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45872 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45875 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45877 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45883 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45911 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46147 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46245 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46249 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46252 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46253 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46254 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46280 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46291 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46292 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46299 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46307 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46312 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52982 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53035 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53047 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53048 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53060 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53061 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53063 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53065 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53070 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53073 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53082 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53093 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53096 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53106 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53111 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53135 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53146 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53147 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53158 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53177 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53207 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53213 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53225 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53226 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53229 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53232 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53236 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53237 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53238 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53249 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53258 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53265 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31637 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-45988 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-56692 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71315 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23066 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23105 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23222 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23273 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-177.187 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23340 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23351 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-179.189 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23391 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23449 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31403 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31447 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31454 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31469 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31473 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31507 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31548 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31665 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31673 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31678 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31680 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31758 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43009 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43016 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43030 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43033 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-179.189 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43060 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43091 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43093 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43111 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43153 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43214 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43365 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43406 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43407 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43437 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43456 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43502 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45850 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45864 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45899 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46273 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46304 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46320 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52909 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52958 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53050 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53086 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53159 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53269 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2015-7837 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2016-8660 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-4095 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-47432 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47658 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-0480 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-38457 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-40133 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-4543 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2022-48628 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48633 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48673 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48706 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48766 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48887 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48929 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48976 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48979 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49069 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49108 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49123 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49124 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49125 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49133 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49134 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49161 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49167 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49173 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49177 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49178 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49203 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49245 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49296 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49303 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49306 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49317 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49333 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49342 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49393 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49420 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49469 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49476 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49484 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49496 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49504 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49516 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49528 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49529 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49531 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49533 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49534 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49539 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49543 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49547 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49552 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49562 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49622 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49699 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49742 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-49750 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-49759 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-49764 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49766 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-49773 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-49783 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-49803 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49810 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-49829 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-49833 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-49858 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-49901 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-49932 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49940 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49943 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-49955 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49965 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49971 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49974 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49997 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50002 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50009 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50015 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50016 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50073 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50116 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50166 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50167 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50178 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50195 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50224 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50230 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50232 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50236 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50260 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50266 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50284 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50304 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50316 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50322 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50332 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50354 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50357 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50380 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50383 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50390 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50393 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50407 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50418 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50425 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50461 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50464 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50467 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50479 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50500 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50527 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50539 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50550 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50554 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50571 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50627 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50704 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50746 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50748 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50772 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50815 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50862 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50863 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50871 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-0160 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31082 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-52485 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52569 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52576 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52582 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52590 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52591 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52625 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52632 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52634 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52648 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52653 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52657 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52660 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52671 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52673 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52676 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52700 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52732 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52737 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52761 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52831 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52857 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52879 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52888 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52905 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52920 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52939 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52981 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53002 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53008 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53009 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53010 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53036 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53042 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53068 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53093 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53105 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53115 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53149 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53152 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53168 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53180 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53198 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53209 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53221 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53231 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53240 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53247 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53248 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53258 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53261 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53292 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53323 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53325 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53332 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53347 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53348 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53353 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53355 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53362 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53366 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53367 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53370 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53371 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53382 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53383 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53385 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53387 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53410 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53421 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53424 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53429 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53434 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53438 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53460 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53466 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53483 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53491 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53509 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53529 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53538 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53539 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53540 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53545 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53547 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53558 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53561 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53562 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53574 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53584 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53588 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53602 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53609 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53620 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53627 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53628 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53635 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53647 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53651 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53657 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53662 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53671 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53682 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53685 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53694 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53702 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53721 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53743 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53753 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53765 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53767 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53780 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53806 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53822 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53829 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53846 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53849 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53867 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54002 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54016 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54019 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54023 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54028 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54052 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54067 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54088 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54121 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54129 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54190 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54234 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54237 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54242 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54259 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54271 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54280 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54324 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-14027 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26595 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26605 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26647 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26656 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26658 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-26691 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26714 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26719 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26740 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26756 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26759 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26767 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26770 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26807 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26844 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26853 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26866 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26876 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26938 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26948 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26953 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27002 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27005 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27014 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27025 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27032 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27035 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27041 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27056 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27057 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27062 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27389 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27400 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27418 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27435 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35784 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35794 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35799 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35801 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35803 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35808 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35826 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35832 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35839 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35843 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35865 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35875 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35878 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-35908 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35924 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35926 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35931 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35942 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35945 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35946 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35956 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35959 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-35971 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35995 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35998 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35999 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36000 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36009 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36021 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36026 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36244 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36478 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-36479 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36900 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36903 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36909 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36911 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36917 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36918 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36920 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36922 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36924 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36948 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36951 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36966 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-37021 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38543 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38554 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38557 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38564 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38594 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38608 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38625 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39282 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39298 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-40966 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40972 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-40975 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40977 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-40979 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40998 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40999 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41001 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41008 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41023 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41030 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41031 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41036 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41062 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41067 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41075 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41079 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41082 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41088 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42067 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42091 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42110 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42122 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42125 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42128 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42129 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42139 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42239 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42273 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42319 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42320 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42321 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43823 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43824 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43831 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43832 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43844 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43872 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-43899 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43911 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43912 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44950 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44961 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44962 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44963 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44970 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-45010 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-45015 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46678 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46681 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46705 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46715 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46716 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46717 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46718 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46720 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46726 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46727 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46728 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46730 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46733 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46748 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46749 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46754 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46762 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46765 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46770 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46775 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46802 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46803 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46806 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46808 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46823 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46834 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46835 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46842 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46843 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46848 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46857 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46860 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46861 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47141 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47658 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47661 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47662 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47664 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47666 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47678 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47683 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47703 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47704 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47728 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47736 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47794 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47809 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-48873 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49568 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49870 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49888 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49891 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49893 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49898 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49899 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49901 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49904 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49905 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49906 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49908 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49909 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49910 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49911 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49912 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49914 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49915 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49916 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49917 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49918 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49919 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49920 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49921 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49922 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49923 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49929 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49932 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49939 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49940 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49945 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49970 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49978 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49987 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49988 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49990 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49994 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50012 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50014 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50017 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50028 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50034 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50048 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50056 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50060 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-179.189 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50098 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50138 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50146 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50166 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50187 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50271 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50284 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50285 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50289 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50298 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-52559 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-52560 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53056 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53079 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53091 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53114 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53175 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53187 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53190 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53195 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53196 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53210 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53219 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53220 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53221 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53224 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53234 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53687 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-54683 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56368 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56544 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56557 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56565 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56566 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56583 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56584 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56588 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56591 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56592 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56607 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56611 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56639 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56641 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56647 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56657 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56660 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56665 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56671 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56677 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-56703 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56707 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56709 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56712 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56717 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56718 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56719 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56722 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56727 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56782 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57804 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57809 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57843 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57852 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57872 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57875 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57888 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57895 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57924 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57950 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57952 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57975 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57976 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57993 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57999 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58011 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58012 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58018 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58019 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58053 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58077 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58089 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58094 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58095 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58096 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58097 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58098 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58100 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58238 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-58241 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21629 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-21634 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21635 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21649 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21656 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21658 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21667 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21672 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21673 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-21682 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21696 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21712 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21723 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21730 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21738 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21750 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21752 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21768 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21792 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21801 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21816 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21817 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21819 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21821 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21831 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21832 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21833 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21838 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21861 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21872 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21881 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21885 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-21891 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21894 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21899 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21908 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21918 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21931 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21944 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21955 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-21972 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21976 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21986 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-22019 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22026 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22028 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22037 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 65.7% Actively Exploited | Not Applicable |
| CVE-2025-22042 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-22043 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-22053 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-22057 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22058 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22072 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22090 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22103 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22105 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22109 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22111 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22113 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22124 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22125 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22127 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-23130 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23131 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23132 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23141 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23143 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23155 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23160 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23162 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37743 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37744 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37745 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37746 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37747 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37775 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37806 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37807 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37820 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37833 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37834 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37842 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37852 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37853 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37855 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37856 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37870 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37876 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37877 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37878 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37880 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37884 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37907 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37931 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37938 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37945 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37951 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37954 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37956 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37959 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37961 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37980 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37984 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38006 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38011 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38014 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38015 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38020 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38029 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38033 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38036 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38038 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38039 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38040 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38041 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38042 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38045 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38047 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38057 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-38059 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38060 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38062 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38063 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38064 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38070 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38071 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38080 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38092 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-38096 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38097 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38098 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38099 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38105 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38125 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38126 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38127 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38140 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38162 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38166 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38168 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38189 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38191 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2025-38192 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38199 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38202 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38205 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38207 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38208 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38215 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38225 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38244 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38261 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38264 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-38269 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38272 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38275 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38300 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38321 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38331 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-38333 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38334 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38343 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38353 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38359 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38360 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38368 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38373 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38408 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38409 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38426 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38436 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38438 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38449 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38491 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38503 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38507 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38520 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38531 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38544 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38560 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38562 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 7.6% Low-Moderate Risk | Not Applicable |
| CVE-2025-38590 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-38591 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38615 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38621 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38626 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38643 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38644 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38659 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38665 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38692 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38705 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38709 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38710 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38716 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39677 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39692 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39705 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39706 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39707 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39715 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39716 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39720 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-39732 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39745 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39746 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39747 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39748 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39753 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39762 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39763 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39764 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39770 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-39771 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39779 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39781 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39789 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39800 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39819 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39827 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39829 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39833 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39838 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39850 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39851 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-39876 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39885 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39886 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39907 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39908 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39923 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39925 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39929 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-39931 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39932 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-39933 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39934 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39937 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39940 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39942 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-39947 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39949 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39953 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39989 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39990 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40005 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40020 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40026 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40027 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40029 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40030 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40040 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40042 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40044 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40049 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40053 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-40057 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40070 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40075 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40078 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40088 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40092 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40094 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40099 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40100 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40102 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40103 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40104 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40105 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40109 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40115 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40125 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40140 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40153 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40160 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40164 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40171 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40195 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40196 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40205 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40211 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40219 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40231 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40251 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40253 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40264 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40280 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40283 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40284 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40287 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40305 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40325 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40334 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40339 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40346 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40347 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-40360 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40362 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40363 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68171 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68173 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68176 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68178 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68185 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68188 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68192 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-68193 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68194 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68200 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68204 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68206 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-68211 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68219 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68223 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68227 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68229 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68231 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68236 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68244 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68261 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-68265 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68281 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68283 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-68288 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68295 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68297 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68307 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68308 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68309 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68310 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68313 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68317 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68321 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-68331 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68333 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68334 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68336 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-68337 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-68340 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68345 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68358 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68363 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68365 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-68372 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68378 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68379 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68725 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68732 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68734 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68758 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68774 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-68776 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68778 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68780 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68783 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68785 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68794 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-68795 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68798 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68802 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68803 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-68813 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68814 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68818 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-68820 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68821 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68822 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71064 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71077 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71079 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71081 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71083 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71084 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71085 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71087 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71094 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71095 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71096 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71097 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71098 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71102 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71104 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71105 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71107 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71108 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71109 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71113 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71114 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71115 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71118 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71120 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-71121 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71125 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71127 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71131 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71132 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71147 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71150 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71154 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71158 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71160 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71161 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-71163 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71180 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71182 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71183 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-71184 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71185 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71186 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71188 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71190 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71191 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71194 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71202 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71204 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-71222 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71223 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71227 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71229 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71232 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71233 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71235 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71236 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71237 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71239 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71265 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71266 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71267 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71268 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71269 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71272 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71273 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71285 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71287 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71289 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-71290 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71291 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71292 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-71293 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71294 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71295 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71297 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71299 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71300 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71302 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22976 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22977 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22979 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22982 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22990 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-22991 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-22992 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-22996 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-22997 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-22999 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23000 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23003 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-23011 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23019 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23020 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23021 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23026 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23031 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23038 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23047 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23058 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23060 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-174.184 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23061 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23063 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23064 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23069 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23075 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23080 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23084 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23085 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23086 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23087 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23088 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23090 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23091 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23093 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23095 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23096 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23097 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23100 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23108 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23113 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23119 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23120 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23121 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23124 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23125 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23128 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23133 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23137 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23138 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23141 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23145 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23146 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23150 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23154 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23157 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23164 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23170 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23190 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23196 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23202 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23206 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23213 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23214 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23215 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23217 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23220 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23228 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23229 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23236 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23237 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23238 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23241 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23242 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-23247 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23255 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23256 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23257 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23258 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23259 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23260 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23261 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23264 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23265 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23266 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23267 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23272 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23274 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-179.189 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23276 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23277 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23278 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23279 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23285 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23286 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23287 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23289 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23290 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23291 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23292 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23293 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23296 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23298 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23300 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23303 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23304 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23307 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23310 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23312 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23324 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23330 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23334 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23335 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23339 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23347 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23352 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23356 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23357 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23362 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23365 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23367 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23368 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23370 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23371 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23374 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23379 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23381 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23382 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23389 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23396 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23398 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23399 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23401 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23403 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23404 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23405 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23409 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23420 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23434 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23438 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23439 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23442 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23446 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23460 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23462 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-23465 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23468 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23472 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23474 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31391 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31394 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31400 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31407 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31410 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31411 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31412 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31415 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31416 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31418 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31420 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31421 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31422 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31423 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31424 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31425 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31427 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31428 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31441 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31450 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31451 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31461 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31462 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31467 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31480 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31483 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31486 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31487 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31492 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31495 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31496 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31497 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31498 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31503 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31509 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31510 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31512 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31515 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31518 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31519 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31520 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31521 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31522 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31524 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31531 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31533 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-179.189 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31537 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31540 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31545 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31546 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31549 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31550 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31551 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31552 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31555 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31557 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31560 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31565 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31577 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31579 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31585 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31590 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31592 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31594 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31595 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31596 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31599 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31603 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31605 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31606 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31610 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31615 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31616 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31617 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31618 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31619 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31623 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31624 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31625 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31628 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31630 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31634 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31642 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31651 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31658 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31660 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31661 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31662 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31664 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31670 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31671 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31672 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31674 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31675 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31676 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31677 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31679 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31681 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31682 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31684 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31687 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31692 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31698 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31699 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31701 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31704 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31721 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31722 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31723 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31724 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31725 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31726 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31737 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31738 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31749 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31752 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31754 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31755 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31756 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31762 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31763 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31767 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31770 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31773 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31777 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31781 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43014 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43021 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43022 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43024 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43025 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43026 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43028 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43032 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43035 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43036 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43041 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43042 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43043 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43045 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43046 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43048 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43054 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43058 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43061 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43062 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43064 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43065 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43066 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43068 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43069 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43072 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43073 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43077 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-179.189 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43079 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43080 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43085 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43088 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43089 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43098 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43099 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43101 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43103 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43104 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43105 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43107 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43109 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43113 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43115 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43118 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43119 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43123 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43124 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43127 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43129 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43130 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43131 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43132 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43135 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43136 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43137 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43139 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43140 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43143 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43145 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43147 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43148 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43149 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43152 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43156 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43159 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43161 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43162 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43165 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43167 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43168 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43170 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43171 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43172 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43173 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43182 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43183 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43187 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43189 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43191 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43194 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43195 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43200 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43201 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43202 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43204 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43209 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43213 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43216 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43218 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43219 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43220 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43223 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43225 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43227 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43228 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43230 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43231 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43234 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43242 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43243 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43244 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43246 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43251 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43253 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43255 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43257 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43261 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43262 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43264 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43266 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43267 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43268 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43269 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43270 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43271 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43273 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43277 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43287 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43288 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43289 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43292 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43294 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43295 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43296 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43298 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43299 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43300 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43302 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43305 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43306 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43308 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43309 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43310 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43311 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43312 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43313 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43314 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43315 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43316 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43317 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43318 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43319 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43320 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43327 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43333 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43338 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43340 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43343 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43344 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43350 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43355 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43357 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43359 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43361 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43362 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43363 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43381 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43382 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43387 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43398 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43400 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43405 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43409 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43410 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43411 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43413 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43416 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43419 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43421 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43424 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43425 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43428 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43429 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43432 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43436 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43445 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43451 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43452 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43459 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43466 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43469 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43471 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43472 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43473 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43474 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43475 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43483 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43491 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43492 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43496 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45834 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45835 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45836 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45840 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45842 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45843 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-45846 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45847 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45848 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45855 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45857 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45873 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45890 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45904 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45912 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45915 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45917 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45919 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45923 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45924 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45930 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45934 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45940 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45941 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45944 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45948 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45954 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45960 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45961 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45964 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45965 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45968 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45969 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45974 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45978 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45981 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45983 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45985 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45986 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45987 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45997 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45999 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46000 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46002 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46003 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46009 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46012 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46014 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46018 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46019 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46021 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46023 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46026 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46027 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46028 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-179.189 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46032 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46037 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46038 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46040 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46044 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46046 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46049 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46050 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46051 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46059 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46070 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46072 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46077 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46078 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46080 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46082 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46083 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46086 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46088 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46091 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46092 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46098 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46101 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46102 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46103 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46107 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46108 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46127 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46128 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46132 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46137 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46146 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46151 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46153 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46157 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46158 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46160 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46161 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46167 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46168 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46169 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46170 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46172 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46178 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46184 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46186 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46193 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46196 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46200 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46214 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46220 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46225 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46226 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46229 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46231 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46233 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46235 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46236 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46247 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46302 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46303 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46321 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46322 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52913 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52915 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52916 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52921 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52925 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52926 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52927 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52928 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52929 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52930 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52936 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52937 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52939 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52944 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52946 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-52948 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52954 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-52960 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52963 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52970 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52972 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52975 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52977 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52981 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-52984 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52985 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52988 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52990 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52995 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52999 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53001 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53003 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53012 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53015 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53017 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53018 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53021 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53022 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53023 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53034 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53037 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53039 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53056 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53064 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53066 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53069 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53074 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53076 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53077 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53080 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53083 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53088 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53107 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53122 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53128 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53134 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53139 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53150 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53167 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53168 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53181 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53199 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53208 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53218 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53219 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53220 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53221 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53227 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53245 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53252 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53263 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53284 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53287 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53289 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53291 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53292 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53295 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53304 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53306 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53313 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53314 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53317 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53320 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53325 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53327 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53331 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53332 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53337 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53339 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53345 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53349 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53353 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53358 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53369 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53376 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53377 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53379 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53382 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53385 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53393 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53400 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53402 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53403 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63798 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63803 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63810 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63822 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63832 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63858 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63860 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63865 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63867 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63868 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63870 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63872 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63890 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63892 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63893 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-63897 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63900 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63902 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63903 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63904 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63926 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63927 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63942 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63948 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63961 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63963 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63964 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63973 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63976 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-63983 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63985 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63990 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63991 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63999 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64004 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64005 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64006 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64012 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64014 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64039 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64046 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64076 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64077 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64078 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64079 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64103 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64106 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64112 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64116 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64118 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64123 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64125 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-64126 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64133 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64144 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64153 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64155 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64170 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64173 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64176 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64177 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64178 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64179 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64185 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64187 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64190 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64206 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64210 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64212 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64213 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64220 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64222 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64225 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64227 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64231 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64237 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64243 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64245 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64275 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64279 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64294 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64299 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64301 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64313 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64315 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64316 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64329 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64330 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64332 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64333 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64334 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64335 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64336 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64338 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64343 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64344 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64346 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64347 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64351 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64352 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64360 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64362 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64363 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64370 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64373 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64374 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64381 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64388 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64403 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64405 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64406 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64408 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64411 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64412 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64413 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64423 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64424 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64428 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64430 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64435 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64436 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64452 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64454 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64455 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64463 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64465 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64478 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64487 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64488 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64496 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64507 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64510 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64512 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64513 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64514 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64524 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64529 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64537 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64540 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64541 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64544 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64545 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64546 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64547 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64553 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2017-13693 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-12928 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-12929 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-3114 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49651 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-4133 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27010 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27011 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49968 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50009 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53093 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58237 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21645 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21693 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37800 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71304 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71313 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23103 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23198 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23336 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23444 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31446 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31448 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31453 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31667 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31771 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43071 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43180 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43211 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43352 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43353 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43480 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43484 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45838 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45841 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45844 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45858 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45862 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45868 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45869 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45870 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45871 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45872 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45875 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45877 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45883 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45911 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46147 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46245 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46249 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46252 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46253 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46254 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46280 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46291 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46292 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46299 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46307 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46312 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52982 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53035 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53047 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53048 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53060 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53061 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53063 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53065 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53070 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53073 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53082 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53093 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53096 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53106 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53111 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53135 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53146 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53147 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53158 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53177 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53207 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53213 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53225 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53226 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53229 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53232 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53236 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53237 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53238 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53249 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53258 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53265 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-13837 | NONE0 | python3.10 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.14 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-13837 | NONE0 | python3.10-minimal 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.14 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-28418 | NONE0 | vim-common 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.26 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45130 | NONE0 | vim-common 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.30 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-55892 | NONE0 | vim-common 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.33 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-59857 | NONE0 | vim-common 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.34 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-28418 | NONE0 | vim-runtime 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.26 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45130 | NONE0 | vim-runtime 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.30 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-55892 | NONE0 | vim-runtime 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.33 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-59857 | NONE0 | vim-runtime 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.34 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-28418 | NONE0 | xxd 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.26 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45130 | NONE0 | xxd 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.30 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-55892 | NONE0 | xxd 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.33 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-59857 | NONE0 | xxd 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.34 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-59919 | NONE0 | io.netty:netty-codec-haproxy 4.1.128.Final fixed in 4.2.16.Final, 4.1.136.Final | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-32288 | NONE0 | stdlib v1.23.12 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-1489 | NONE0 | libglib2.0-0 2.72.4-0ubuntu2.6 fixed in 2.72.4-0ubuntu2.9 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-58055 | NONE0 | libnghttp2-14 1.43.0-1ubuntu0.2 fixed in 1.43.0-1ubuntu0.4 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-42506 | NONE0 | golang.org/x/net v0.33.0 fixed in 0.55.0 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-27142 | NONE0 | stdlib v1.23.12 fixed in 1.25.8, 1.26.1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39823 | NONE0 | stdlib v1.23.12 fixed in 1.25.10, 1.26.3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39826 | NONE0 | stdlib v1.23.12 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-3592 | NONE0 | bind9-dnsutils 1:9.18.39-0ubuntu0.22.04.2 fixed in 1:9.18.39-0ubuntu0.22.04.4 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-5950 | NONE0 | bind9-dnsutils 1:9.18.39-0ubuntu0.22.04.2 fixed in 1:9.18.39-0ubuntu0.22.04.4 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-3592 | NONE0 | bind9-host 1:9.18.39-0ubuntu0.22.04.2 fixed in 1:9.18.39-0ubuntu0.22.04.4 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-5950 | NONE0 | bind9-host 1:9.18.39-0ubuntu0.22.04.2 fixed in 1:9.18.39-0ubuntu0.22.04.4 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-3592 | NONE0 | bind9-libs 1:9.18.39-0ubuntu0.22.04.2 fixed in 1:9.18.39-0ubuntu0.22.04.4 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-5950 | NONE0 | bind9-libs 1:9.18.39-0ubuntu0.22.04.2 fixed in 1:9.18.39-0ubuntu0.22.04.4 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2023-7250 | NONE0 | iperf3 3.9-1+deb11u1build0.22.04.1 fixed in 3.9-1+deb11u1ubuntu0.1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2025-54350 | NONE0 | iperf3 3.9-1+deb11u1build0.22.04.1 fixed in 3.9-1+deb11u1ubuntu0.1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-33948 | NONE0 | jq 1.6-2.1ubuntu3.1 fixed in 1.6-2.1ubuntu3.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-0915 | NONE0 | libc-bin 2.35-0ubuntu3.11 fixed in 2.35-0ubuntu3.13 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-4046 | NONE0 | libc-bin 2.35-0ubuntu3.11 fixed in 2.35-0ubuntu3.14 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-0915 | NONE0 | libc-dev-bin 2.35-0ubuntu3.11 fixed in 2.35-0ubuntu3.13 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-4046 | NONE0 | libc-dev-bin 2.35-0ubuntu3.11 fixed in 2.35-0ubuntu3.14 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-0915 | NONE0 | libc6 2.35-0ubuntu3.11 fixed in 2.35-0ubuntu3.13 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-4046 | NONE0 | libc6 2.35-0ubuntu3.11 fixed in 2.35-0ubuntu3.14 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-0915 | NONE0 | libc6-dev 2.35-0ubuntu3.11 fixed in 2.35-0ubuntu3.13 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-4046 | NONE0 | libc6-dev 2.35-0ubuntu3.11 fixed in 2.35-0ubuntu3.14 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-6253 | NONE0 | libcurl3-gnutls 7.81.0-1ubuntu1.21 fixed in 7.81.0-1ubuntu1.24 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-7168 | NONE0 | libcurl3-gnutls 7.81.0-1ubuntu1.21 fixed in 7.81.0-1ubuntu1.24 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-4873 | NONE0 | libcurl3-gnutls 7.81.0-1ubuntu1.21 fixed in 7.81.0-1ubuntu1.24 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-6253 | NONE0 | libcurl4 7.81.0-1ubuntu1.21 fixed in 7.81.0-1ubuntu1.24 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-7168 | NONE0 | libcurl4 7.81.0-1ubuntu1.21 fixed in 7.81.0-1ubuntu1.24 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-4873 | NONE0 | libcurl4 7.81.0-1ubuntu1.21 fixed in 7.81.0-1ubuntu1.24 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-14831 | NONE0 | libgnutls30 3.7.3-4ubuntu1.7 fixed in 3.7.3-4ubuntu1.8 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-42015 | NONE0 | libgnutls30 3.7.3-4ubuntu1.7 fixed in 3.7.3-4ubuntu1.9 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2023-7250 | NONE0 | libiperf0 3.9-1+deb11u1build0.22.04.1 fixed in 3.9-1+deb11u1ubuntu0.1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2025-54350 | NONE0 | libiperf0 3.9-1+deb11u1build0.22.04.1 fixed in 3.9-1+deb11u1ubuntu0.1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-33948 | NONE0 | libjq1 1.6-2.1ubuntu3.1 fixed in 1.6-2.1ubuntu3.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-34743 | NONE0 | liblzma5 5.2.5-2ubuntu1 fixed in 5.2.5-2ubuntu1.1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-4189 | NONE0 | libpython2.7 2.7.18-13ubuntu1.5 No fix yet | 2.7% Low-Moderate Risk | Not Applicable |
| CVE-2023-27043 | NONE0 | libpython2.7 2.7.18-13ubuntu1.5 No fix yet | 2.5% Low-Moderate Risk | Not Applicable |
| CVE-2025-12084 | NONE0 | libpython2.7 2.7.18-13ubuntu1.5 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2021-4189 | NONE0 | libpython2.7-dev 2.7.18-13ubuntu1.5 No fix yet | 2.7% Low-Moderate Risk | Not Applicable |
| CVE-2023-27043 | NONE0 | libpython2.7-dev 2.7.18-13ubuntu1.5 No fix yet | 2.5% Low-Moderate Risk | Not Applicable |
| CVE-2025-12084 | NONE0 | libpython2.7-dev 2.7.18-13ubuntu1.5 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2021-4189 | NONE0 | libpython2.7-minimal 2.7.18-13ubuntu1.5 No fix yet | 2.7% Low-Moderate Risk | Not Applicable |
| CVE-2023-27043 | NONE0 | libpython2.7-minimal 2.7.18-13ubuntu1.5 No fix yet | 2.5% Low-Moderate Risk | Not Applicable |
| CVE-2025-12084 | NONE0 | libpython2.7-minimal 2.7.18-13ubuntu1.5 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2021-4189 | NONE0 | libpython2.7-stdlib 2.7.18-13ubuntu1.5 No fix yet | 2.7% Low-Moderate Risk | Not Applicable |
| CVE-2023-27043 | NONE0 | libpython2.7-stdlib 2.7.18-13ubuntu1.5 No fix yet | 2.5% Low-Moderate Risk | Not Applicable |
| CVE-2025-12084 | NONE0 | libpython2.7-stdlib 2.7.18-13ubuntu1.5 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-12084 | NONE0 | libpython3.10 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.14 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-3276 | NONE0 | libpython3.10 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.16 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-12084 | NONE0 | libpython3.10-minimal 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.14 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-3276 | NONE0 | libpython3.10-minimal 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.16 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-12084 | NONE0 | libpython3.10-stdlib 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.14 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-3276 | NONE0 | libpython3.10-stdlib 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.16 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-42766 | NONE0 | libssl3 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.25 | 1.0% Theoretical Threat | Not Applicable |
| CVE-2026-42767 | NONE0 | libssl3 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.25 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2022-3523 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2022-50700 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54181 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47689 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-39968 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39972 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40204 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40353 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68367 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71225 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23457 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53194 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64538 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-3523 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2022-50700 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54181 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47689 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-39968 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39972 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40204 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40353 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68367 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71225 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23457 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53194 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64538 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-4189 | NONE0 | python2.7 2.7.18-13ubuntu1.5 No fix yet | 2.7% Low-Moderate Risk | Not Applicable |
| CVE-2023-27043 | NONE0 | python2.7 2.7.18-13ubuntu1.5 No fix yet | 2.5% Low-Moderate Risk | Not Applicable |
| CVE-2025-12084 | NONE0 | python2.7 2.7.18-13ubuntu1.5 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2021-4189 | NONE0 | python2.7-dev 2.7.18-13ubuntu1.5 No fix yet | 2.7% Low-Moderate Risk | Not Applicable |
| CVE-2023-27043 | NONE0 | python2.7-dev 2.7.18-13ubuntu1.5 No fix yet | 2.5% Low-Moderate Risk | Not Applicable |
| CVE-2025-12084 | NONE0 | python2.7-dev 2.7.18-13ubuntu1.5 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2021-4189 | NONE0 | python2.7-minimal 2.7.18-13ubuntu1.5 No fix yet | 2.7% Low-Moderate Risk | Not Applicable |
| CVE-2023-27043 | NONE0 | python2.7-minimal 2.7.18-13ubuntu1.5 No fix yet | 2.5% Low-Moderate Risk | Not Applicable |
| CVE-2025-12084 | NONE0 | python2.7-minimal 2.7.18-13ubuntu1.5 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-12084 | NONE0 | python3.10 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.14 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-3276 | NONE0 | python3.10 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.16 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-12084 | NONE0 | python3.10-minimal 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.14 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-3276 | NONE0 | python3.10-minimal 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.16 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-44656 | NONE0 | vim-common 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.30 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-47167 | NONE0 | vim-common 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.32 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-44656 | NONE0 | vim-runtime 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.30 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-47167 | NONE0 | vim-runtime 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.32 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-44656 | NONE0 | xxd 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.30 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-47167 | NONE0 | xxd 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.32 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-54514 | NONE0 | com.fasterxml.jackson.core:jackson-databind 2.16.0 fixed in 2.18.8, 2.21.4, 3.1.4 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-54515 | NONE0 | com.fasterxml.jackson.core:jackson-databind 2.16.0 fixed in 3.1.4, 2.18.9, 2.21.5, 2.22.1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-50020 | NONE0 | io.netty:netty-codec-http 4.1.128.Final fixed in 4.2.15.Final, 4.1.135.Final | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-59898 | NONE0 | io.netty:netty-codec-http 4.1.128.Final fixed in 4.2.16.Final, 4.1.136.Final | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-47244 | NONE0 | io.netty:netty-codec-http2 4.1.128.Final fixed in 4.2.15.Final, 4.1.135.Final | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-50560 | NONE0 | io.netty:netty-codec-http2 4.1.128.Final fixed in 4.2.15.Final, 4.1.135.Final | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-47911 | NONE0 | golang.org/x/net v0.33.0 fixed in 0.45.0 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-58190 | NONE0 | golang.org/x/net v0.33.0 fixed in 0.45.0 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-47912 | NONE0 | stdlib v1.23.12 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-58185 | NONE0 | stdlib v1.23.12 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-58187 | NONE0 | stdlib v1.23.12 fixed in 1.24.9, 1.25.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-58188 | NONE0 | stdlib v1.23.12 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-58189 | NONE0 | stdlib v1.23.12 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-61723 | NONE0 | stdlib v1.23.12 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-61724 | NONE0 | stdlib v1.23.12 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-61725 | NONE0 | stdlib v1.23.12 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-61730 | NONE0 | stdlib v1.23.12 fixed in 1.24.12, 1.25.6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-42505 | NONE0 | stdlib v1.23.12 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-42507 | NONE0 | stdlib v1.23.12 fixed in 1.25.11, 1.26.4 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-58186 | NONE0 | stdlib v1.23.12 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-39970 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40217 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40338 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40343 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-39970 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40217 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40338 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40343 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2022-50721 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40178 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71193 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23035 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50721 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40178 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71193 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23035 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-5450 | NONE0 | libc-bin 2.35-0ubuntu3.11 fixed in 2.35-0ubuntu3.14 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-5928 | NONE0 | libc-bin 2.35-0ubuntu3.11 fixed in 2.35-0ubuntu3.14 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-5450 | NONE0 | libc-dev-bin 2.35-0ubuntu3.11 fixed in 2.35-0ubuntu3.14 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-5928 | NONE0 | libc-dev-bin 2.35-0ubuntu3.11 fixed in 2.35-0ubuntu3.14 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-5450 | NONE0 | libc6 2.35-0ubuntu3.11 fixed in 2.35-0ubuntu3.14 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-5928 | NONE0 | libc6 2.35-0ubuntu3.11 fixed in 2.35-0ubuntu3.14 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-5450 | NONE0 | libc6-dev 2.35-0ubuntu3.11 fixed in 2.35-0ubuntu3.14 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-5928 | NONE0 | libc6-dev 2.35-0ubuntu3.11 fixed in 2.35-0ubuntu3.14 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-11850 | NONE0 | libgssapi-krb5-2 1.19.2-2ubuntu0.7 fixed in 1.19.2-2ubuntu0.8 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-11850 | NONE0 | libk5crypto3 1.19.2-2ubuntu0.7 fixed in 1.19.2-2ubuntu0.8 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-11850 | NONE0 | libkrb5-3 1.19.2-2ubuntu0.7 fixed in 1.19.2-2ubuntu0.8 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-11850 | NONE0 | libkrb5support0 1.19.2-2ubuntu0.7 fixed in 1.19.2-2ubuntu0.8 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-34180 | NONE0 | libssl3 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.25 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2025-40121 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23180 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40121 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23180 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-21936 | NONE0 | mysql-client-8.0 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.45-0ubuntu0.22.04.1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-21937 | NONE0 | mysql-client-8.0 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.45-0ubuntu0.22.04.1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-21941 | NONE0 | mysql-client-8.0 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.45-0ubuntu0.22.04.1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-21948 | NONE0 | mysql-client-8.0 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.45-0ubuntu0.22.04.1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-21964 | NONE0 | mysql-client-8.0 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.45-0ubuntu0.22.04.1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-21998 | NONE0 | mysql-client-8.0 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-22002 | NONE0 | mysql-client-8.0 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-22004 | NONE0 | mysql-client-8.0 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-22005 | NONE0 | mysql-client-8.0 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-34267 | NONE0 | mysql-client-8.0 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-34278 | NONE0 | mysql-client-8.0 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-34293 | NONE0 | mysql-client-8.0 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-34304 | NONE0 | mysql-client-8.0 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-35236 | NONE0 | mysql-client-8.0 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-35237 | NONE0 | mysql-client-8.0 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-35238 | NONE0 | mysql-client-8.0 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-35239 | NONE0 | mysql-client-8.0 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-35240 | NONE0 | mysql-client-8.0 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-21936 | NONE0 | mysql-client-core-8.0 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.45-0ubuntu0.22.04.1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-21937 | NONE0 | mysql-client-core-8.0 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.45-0ubuntu0.22.04.1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-21941 | NONE0 | mysql-client-core-8.0 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.45-0ubuntu0.22.04.1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-21948 | NONE0 | mysql-client-core-8.0 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.45-0ubuntu0.22.04.1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-21964 | NONE0 | mysql-client-core-8.0 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.45-0ubuntu0.22.04.1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-21998 | NONE0 | mysql-client-core-8.0 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-22002 | NONE0 | mysql-client-core-8.0 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-22004 | NONE0 | mysql-client-core-8.0 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-22005 | NONE0 | mysql-client-core-8.0 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-34267 | NONE0 | mysql-client-core-8.0 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-34278 | NONE0 | mysql-client-core-8.0 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-34293 | NONE0 | mysql-client-core-8.0 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-34304 | NONE0 | mysql-client-core-8.0 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-35236 | NONE0 | mysql-client-core-8.0 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-35237 | NONE0 | mysql-client-core-8.0 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-35238 | NONE0 | mysql-client-core-8.0 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-35239 | NONE0 | mysql-client-core-8.0 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-35240 | NONE0 | mysql-client-core-8.0 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-14017 | NONE0 | libcurl3-gnutls 7.81.0-1ubuntu1.21 fixed in 7.81.0-1ubuntu1.22 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-14017 | NONE0 | libcurl4 7.81.0-1ubuntu1.21 fixed in 7.81.0-1ubuntu1.22 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-modules 1.4.0-11ubuntu2.6 fixed in 1.4.0-11ubuntu2.7 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-modules-bin 1.4.0-11ubuntu2.6 fixed in 1.4.0-11ubuntu2.7 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-runtime 1.4.0-11ubuntu2.6 fixed in 1.4.0-11ubuntu2.7 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam0g 1.4.0-11ubuntu2.6 fixed in 1.4.0-11ubuntu2.7 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-15282 | NONE0 | libpython2.7 2.7.18-13ubuntu1.5 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-0672 | NONE0 | libpython2.7 2.7.18-13ubuntu1.5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-15282 | NONE0 | libpython2.7-dev 2.7.18-13ubuntu1.5 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-0672 | NONE0 | libpython2.7-dev 2.7.18-13ubuntu1.5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-15282 | NONE0 | libpython2.7-minimal 2.7.18-13ubuntu1.5 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-0672 | NONE0 | libpython2.7-minimal 2.7.18-13ubuntu1.5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-15282 | NONE0 | libpython2.7-stdlib 2.7.18-13ubuntu1.5 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-0672 | NONE0 | libpython2.7-stdlib 2.7.18-13ubuntu1.5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-15282 | NONE0 | libpython3.10 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.14 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-0672 | NONE0 | libpython3.10 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.14 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-15282 | NONE0 | libpython3.10-minimal 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.14 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-0672 | NONE0 | libpython3.10-minimal 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.14 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-15282 | NONE0 | libpython3.10-stdlib 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.14 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-0672 | NONE0 | libpython3.10-stdlib 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.14 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-15282 | NONE0 | python2.7 2.7.18-13ubuntu1.5 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-0672 | NONE0 | python2.7 2.7.18-13ubuntu1.5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-15282 | NONE0 | python2.7-dev 2.7.18-13ubuntu1.5 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-0672 | NONE0 | python2.7-dev 2.7.18-13ubuntu1.5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-15282 | NONE0 | python2.7-minimal 2.7.18-13ubuntu1.5 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-0672 | NONE0 | python2.7-minimal 2.7.18-13ubuntu1.5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-15282 | NONE0 | python3.10 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.14 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-0672 | NONE0 | python3.10 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.14 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-15282 | NONE0 | python3.10-minimal 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.14 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-0672 | NONE0 | python3.10-minimal 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.14 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-68161 | NONE0 | org.apache.logging.log4j:log4j-core 2.25.2 fixed in 2.25.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-27456 | NONE0 | libblkid1 2.37.2-4ubuntu3.4 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-15224 | NONE0 | libcurl3-gnutls 7.81.0-1ubuntu1.21 fixed in 7.81.0-1ubuntu1.22 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-15224 | NONE0 | libcurl4 7.81.0-1ubuntu1.21 fixed in 7.81.0-1ubuntu1.22 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-1376 | NONE0 | libdebuginfod-common 0.186-1ubuntu0.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-1376 | NONE0 | libdebuginfod1 0.186-1ubuntu0.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-1376 | NONE0 | libdw1 0.186-1ubuntu0.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-1376 | NONE0 | libelf1 0.186-1ubuntu0.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-27456 | NONE0 | libmount1 2.37.2-4ubuntu3.4 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-27456 | NONE0 | libsmartcols1 2.37.2-4ubuntu3.4 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68160 | NONE0 | libssl3 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.21 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-27456 | NONE0 | libuuid1 2.37.2-4ubuntu3.4 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52955 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-57857 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21947 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-38561 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-168.178 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-23004 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23169 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43047 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-1205 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-48816 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49967 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50350 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-52589 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53178 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53401 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53447 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53452 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53478 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53520 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53794 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53816 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54035 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54071 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54149 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54185 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54201 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54323 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26869 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27408 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36024 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36927 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36949 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-37354 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38306 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-39293 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-39508 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42107 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42253 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43866 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46870 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-49859 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50135 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53176 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53178 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56788 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-57974 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21651 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21732 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21825 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37920 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38232 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38234 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38440 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38524 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-38717 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39726 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39754 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39825 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39884 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39927 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39961 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39977 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39980 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39992 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39996 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40006 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40011 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40016 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40039 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40085 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40110 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40120 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40134 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40139 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40179 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40187 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-40215 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40220 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40244 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40250 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40252 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-40254 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40331 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40342 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-68214 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68239 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68241 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-68264 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68296 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68312 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68745 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-71074 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71111 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71274 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23071 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23101 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23110 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23118 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23126 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23167 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23181 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23207 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23212 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23302 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23348 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23452 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23463 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31393 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31466 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31523 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31697 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31728 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31751 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43053 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43163 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43275 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43342 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43383 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43420 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43430 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43439 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43448 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45905 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45949 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46159 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46187 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53108 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53352 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2017-0537 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-52749 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50183 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52955 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-57857 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21947 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-38561 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-168.178 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-23004 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23169 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43047 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-1205 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-48816 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49967 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50350 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-52589 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53178 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53401 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53447 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53452 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53478 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53520 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53794 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53816 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54035 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54071 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54149 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54185 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54201 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54323 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26869 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27408 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36024 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36927 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36949 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-37354 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38306 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-39293 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-39508 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42107 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42253 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43866 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46870 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-49859 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50135 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53176 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53178 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56788 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-57974 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21651 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21732 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21825 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37920 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38232 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38234 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38440 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38524 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-38717 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39726 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39754 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39825 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39884 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39927 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39961 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39977 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39980 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39992 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39996 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40006 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40011 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40016 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40039 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40085 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40110 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40120 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40134 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40139 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40179 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40187 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-40215 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40220 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40244 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40250 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40252 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-40254 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40331 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40342 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-68214 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68239 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68241 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-68264 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68296 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68312 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68745 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-71074 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71111 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71274 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23071 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23101 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23110 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23118 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23126 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23167 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23181 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23207 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23212 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23302 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23348 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23452 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23463 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31393 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31466 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31523 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31697 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31728 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31751 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43053 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43163 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43275 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43342 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43383 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43420 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43430 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43439 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43448 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45905 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45949 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46159 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46187 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53108 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53352 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2017-0537 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-52749 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50183 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-57452 | NONE0 | vim-common 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.33 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-57452 | NONE0 | vim-runtime 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.33 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-57452 | NONE0 | xxd 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.33 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2019-15213 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-4010 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-49934 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-15213 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-4010 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-49934 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-0865 | NONE0 | libpython2.7 2.7.18-13ubuntu1.5 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-0865 | NONE0 | libpython2.7-dev 2.7.18-13ubuntu1.5 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-0865 | NONE0 | libpython2.7-minimal 2.7.18-13ubuntu1.5 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-0865 | NONE0 | libpython2.7-stdlib 2.7.18-13ubuntu1.5 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-11468 | NONE0 | libpython3.10 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.14 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-0865 | NONE0 | libpython3.10 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.14 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-1502 | NONE0 | libpython3.10 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.16 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-11468 | NONE0 | libpython3.10-minimal 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.14 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-0865 | NONE0 | libpython3.10-minimal 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.14 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-1502 | NONE0 | libpython3.10-minimal 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.16 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-11468 | NONE0 | libpython3.10-stdlib 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.14 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-0865 | NONE0 | libpython3.10-stdlib 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.14 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-1502 | NONE0 | libpython3.10-stdlib 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.16 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-69277 | NONE0 | libsodium23 1.0.18-1build2 fixed in 1.0.18-1ubuntu0.22.04.1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-45896 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40308 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40312 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-45896 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40308 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40312 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-0865 | NONE0 | python2.7 2.7.18-13ubuntu1.5 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-0865 | NONE0 | python2.7-dev 2.7.18-13ubuntu1.5 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-0865 | NONE0 | python2.7-minimal 2.7.18-13ubuntu1.5 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-11468 | NONE0 | python3.10 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.14 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-0865 | NONE0 | python3.10 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.14 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-1502 | NONE0 | python3.10 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.16 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-11468 | NONE0 | python3.10-minimal 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.14 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-0865 | NONE0 | python3.10-minimal 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.14 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-1502 | NONE0 | python3.10-minimal 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.16 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-43895 | NONE0 | jq 1.6-2.1ubuntu3.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43895 | NONE0 | libjq1 1.6-2.1ubuntu3.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23458 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2018-17977 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-50720 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52508 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53733 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54247 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54253 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54263 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26648 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26662 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26672 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26757 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26758 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36910 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38628 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40001 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40021 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40081 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40123 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40183 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-40198 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40200 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40206 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40281 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68768 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2020-14304 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-23458 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2018-17977 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-50720 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52508 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53733 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54247 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54253 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54263 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26648 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26662 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26672 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26757 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26758 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36910 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38628 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40001 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40021 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40081 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40123 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40183 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-40198 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40200 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40206 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40281 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68768 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2020-14304 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-28420 | NONE0 | vim-common 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.26 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-42307 | NONE0 | vim-common 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.30 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-28420 | NONE0 | vim-runtime 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.26 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-42307 | NONE0 | vim-runtime 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.30 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-28420 | NONE0 | xxd 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.26 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-42307 | NONE0 | xxd 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.30 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2025-22870 | NONE0 | golang.org/x/net v0.33.0 fixed in 0.36.0 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-6069 | NONE0 | libpython2.7 2.7.18-13ubuntu1.5 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-6069 | NONE0 | libpython2.7-dev 2.7.18-13ubuntu1.5 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-6069 | NONE0 | libpython2.7-minimal 2.7.18-13ubuntu1.5 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-6069 | NONE0 | libpython2.7-stdlib 2.7.18-13ubuntu1.5 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-40275 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40275 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-22015 | NONE0 | mysql-client-8.0 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-22015 | NONE0 | mysql-client-core-8.0 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6069 | NONE0 | python2.7 2.7.18-13ubuntu1.5 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-6069 | NONE0 | python2.7-dev 2.7.18-13ubuntu1.5 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-6069 | NONE0 | python2.7-minimal 2.7.18-13ubuntu1.5 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-1484 | NONE0 | libglib2.0-0 2.72.4-0ubuntu2.6 fixed in 2.72.4-0ubuntu2.9 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-41848 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-41848 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-48646 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40173 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-48646 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40173 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-9820 | NONE0 | libgnutls30 3.7.3-4ubuntu1.7 fixed in 3.7.3-4ubuntu1.8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69418 | NONE0 | libssl3 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.21 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45536 | NONE0 | io.netty:netty-transport-native-epoll 4.1.128.Final fixed in 4.2.15.Final, 4.1.135.Final | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45536 | NONE0 | io.netty:netty-transport-native-kqueue 4.1.128.Final fixed in 4.2.15.Final, 4.1.135.Final | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1152 | NONE0 | binutils-common 2.38-4ubuntu2.12 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1152 | NONE0 | binutils-x86-64-linux-gnu 2.38-4ubuntu2.12 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1152 | NONE0 | libbinutils 2.38-4ubuntu2.12 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-7883 | NONE0 | libclang-cpp11 1:11.1.0-6 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-1152 | NONE0 | libctf-nobfd0 2.38-4ubuntu2.12 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1152 | NONE0 | libctf0 2.38-4ubuntu2.12 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-0988 | NONE0 | libglib2.0-0 2.72.4-0ubuntu2.6 fixed in 2.72.4-0ubuntu2.8 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-3360 | NONE0 | libglib2.0-0 2.72.4-0ubuntu2.6 fixed in 2.72.4-0ubuntu2.7 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-7039 | NONE0 | libglib2.0-0 2.72.4-0ubuntu2.6 fixed in 2.72.4-0ubuntu2.7 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-3832 | NONE0 | libgnutls30 3.7.3-4ubuntu1.7 fixed in 3.7.3-4ubuntu1.9 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-7883 | NONE0 | libllvm11 1:11.1.0-6 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-11168 | NONE0 | libpython2.7 2.7.18-13ubuntu1.5 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-11168 | NONE0 | libpython2.7-dev 2.7.18-13ubuntu1.5 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-11168 | NONE0 | libpython2.7-minimal 2.7.18-13ubuntu1.5 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-11168 | NONE0 | libpython2.7-stdlib 2.7.18-13ubuntu1.5 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-45446 | NONE0 | libssl3 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.25 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-0989 | NONE0 | libxml2 2.9.13+dfsg-1ubuntu0.10 fixed in 2.9.13+dfsg-1ubuntu0.11 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-53791 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53791 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-11168 | NONE0 | python2.7 2.7.18-13ubuntu1.5 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-11168 | NONE0 | python2.7-dev 2.7.18-13ubuntu1.5 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-11168 | NONE0 | python2.7-minimal 2.7.18-13ubuntu1.5 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-26958 | NONE0 | filippo.io/edwards25519 v1.1.0 fixed in 1.1.1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-56433 | NONE0 | login 1:4.8.1-2ubuntu2.2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-68740 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2020-35501 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68740 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2020-35501 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69652 | NONE0 | binutils-common 2.38-4ubuntu2.12 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69652 | NONE0 | binutils-x86-64-linux-gnu 2.38-4ubuntu2.12 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69652 | NONE0 | libbinutils 2.38-4ubuntu2.12 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69652 | NONE0 | libctf-nobfd0 2.38-4ubuntu2.12 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69652 | NONE0 | libctf0 2.38-4ubuntu2.12 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-13462 | NONE0 | libpython3.10 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.16 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-2297 | NONE0 | libpython3.10 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.16 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-4519 | NONE0 | libpython3.10 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.16 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-13462 | NONE0 | libpython3.10-minimal 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.16 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-2297 | NONE0 | libpython3.10-minimal 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.16 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-4519 | NONE0 | libpython3.10-minimal 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.16 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-13462 | NONE0 | libpython3.10-stdlib 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.16 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-2297 | NONE0 | libpython3.10-stdlib 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.16 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-4519 | NONE0 | libpython3.10-stdlib 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.16 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-0965 | NONE0 | libssh-4 0.9.6-2ubuntu0.22.04.5 fixed in 0.9.6-2ubuntu0.22.04.6 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-40228 | NONE0 | libsystemd0 249.11-0ubuntu3.17 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-40228 | NONE0 | libudev1 249.11-0ubuntu3.17 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-8732 | NONE0 | libxml2 2.9.13+dfsg-1ubuntu0.10 fixed in 2.9.13+dfsg-1ubuntu0.11 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52926 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48667 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48668 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50628 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50778 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50811 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52561 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53992 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54145 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54172 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54227 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54233 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54261 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54320 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47738 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50057 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50211 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57898 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40035 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40268 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40303 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40341 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68191 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68746 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68782 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-71224 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-22978 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31668 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-52926 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48667 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48668 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50628 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50778 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50811 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52561 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53992 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54145 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54172 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54227 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54233 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54261 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54320 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47738 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50057 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50211 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57898 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40035 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40268 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40303 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40341 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68191 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68746 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68782 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-71224 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-22978 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31668 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-29383 | NONE0 | login 1:4.8.1-2ubuntu2.2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-13462 | NONE0 | python3.10 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.16 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-2297 | NONE0 | python3.10 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.16 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-4519 | NONE0 | python3.10 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.16 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-13462 | NONE0 | python3.10-minimal 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.16 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-2297 | NONE0 | python3.10-minimal 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.16 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-4519 | NONE0 | python3.10-minimal 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.16 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-0968 | NONE0 | libssh-4 0.9.6-2ubuntu0.22.04.5 fixed in 0.9.6-2ubuntu0.22.04.6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-8277 | NONE0 | libssh-4 0.9.6-2ubuntu0.22.04.5 fixed in 0.9.6-2ubuntu0.22.04.6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-0992 | NONE0 | libxml2 2.9.13+dfsg-1ubuntu0.10 fixed in 2.9.13+dfsg-1ubuntu0.11 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69645 | NONE0 | binutils-common 2.38-4ubuntu2.12 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69645 | NONE0 | binutils-x86-64-linux-gnu 2.38-4ubuntu2.12 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69645 | NONE0 | libbinutils 2.38-4ubuntu2.12 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69645 | NONE0 | libctf-nobfd0 2.38-4ubuntu2.12 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69645 | NONE0 | libctf0 2.38-4ubuntu2.12 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-1485 | NONE0 | libglib2.0-0 2.72.4-0ubuntu2.6 fixed in 2.72.4-0ubuntu2.9 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22001 | NONE0 | mysql-client-8.0 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-22001 | NONE0 | mysql-client-core-8.0 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-24515 | NONE0 | libexpat1 2.4.7-1ubuntu0.6 fixed in 2.4.7-1ubuntu0.7 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-24515 | NONE0 | libexpat1-dev 2.4.7-1ubuntu0.6 fixed in 2.4.7-1ubuntu0.7 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68788 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68788 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-27139 | NONE0 | stdlib v1.23.12 fixed in 1.25.8, 1.26.1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50583 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50583 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-28422 | NONE0 | vim-common 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.26 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-28422 | NONE0 | vim-runtime 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.26 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-28422 | NONE0 | xxd 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.26 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-42155 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42155 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-0167 | NONE0 | curl 7.81.0-1ubuntu1.21 fixed in 7.81.0-1ubuntu1.23 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-8458 | NONE0 | curl 7.81.0-1ubuntu1.21 fixed in 7.81.0-1ubuntu1.25 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-0167 | NONE0 | libcurl3-gnutls 7.81.0-1ubuntu1.21 fixed in 7.81.0-1ubuntu1.23 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-8458 | NONE0 | libcurl3-gnutls 7.81.0-1ubuntu1.21 fixed in 7.81.0-1ubuntu1.25 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-0167 | NONE0 | libcurl4 7.81.0-1ubuntu1.21 fixed in 7.81.0-1ubuntu1.23 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-8458 | NONE0 | libcurl4 7.81.0-1ubuntu1.21 fixed in 7.81.0-1ubuntu1.25 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-8328 | NONE0 | libpython3.10 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.16 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-8328 | NONE0 | libpython3.10-minimal 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.16 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-8328 | NONE0 | libpython3.10-stdlib 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.16 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-11822 | NONE0 | libsqlite3-0 3.37.2-2ubuntu0.5 fixed in 3.37.2-2ubuntu0.6 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-11824 | NONE0 | libsqlite3-0 3.37.2-2ubuntu0.5 fixed in 3.37.2-2ubuntu0.6 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-50812 | NONE0 | libsqlite3-0 3.37.2-2ubuntu0.5 fixed in 3.37.2-2ubuntu0.7 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-50813 | NONE0 | libsqlite3-0 3.37.2-2ubuntu0.5 fixed in 3.37.2-2ubuntu0.7 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68263 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43011 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-43185 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-53215 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-23268 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23372 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23393 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31405 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31432 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31433 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-31476 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31478 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31536 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31627 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31657 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31659 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31695 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31705 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31706 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31712 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31716 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31780 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43075 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43076 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43236 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43490 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52911 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52914 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53040 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53043 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53046 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53068 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53130 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53178 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53186 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53198 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-50634 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50708 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50759 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50785 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53707 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53714 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53742 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53748 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53855 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54047 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54059 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54105 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54125 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54151 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54180 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54187 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36331 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-27558 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-39985 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39986 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39987 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39988 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39995 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40003 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40012 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40025 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40032 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40036 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40043 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40054 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40055 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40060 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40068 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40073 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40077 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40084 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40087 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-40093 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40095 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40097 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40106 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40107 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40112 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40116 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40124 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40126 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40127 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40137 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40180 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40188 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40192 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40193 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40208 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40223 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40233 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40243 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40245 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40247 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40262 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40263 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40266 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40278 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40282 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40285 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40286 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40288 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40289 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40306 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40310 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40311 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40313 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40314 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40315 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40317 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40332 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40333 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40335 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40337 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40354 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40356 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40358 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-54505 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-62626 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68174 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68175 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68177 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68184 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68190 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68196 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68201 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68217 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68220 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68230 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68238 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68246 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-68249 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68254 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-68255 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-68256 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-68257 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68258 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68266 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68286 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68289 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68290 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68302 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-68303 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68311 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68315 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-68318 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68322 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68325 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68327 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68328 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68330 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68332 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68335 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68339 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68344 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68364 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68727 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68728 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68733 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68755 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68759 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68765 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68767 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68769 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68771 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68772 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68777 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68781 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68786 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68787 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68796 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68797 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68799 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-68804 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68806 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-68808 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68809 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-71067 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71069 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71192 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71195 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71196 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71197 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71198 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71199 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23033 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23037 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23049 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23056 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23176 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23182 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23245 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23269 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23364 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-23406 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23407 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31409 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31417 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31477 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31494 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31597 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31598 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31602 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31611 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31612 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31622 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31626 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31629 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31683 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31707 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31711 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31768 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43117 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43184 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43203 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43245 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43336 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43373 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43377 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43476 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45935 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45956 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45958 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46006 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46062 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46112 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46124 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46175 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46177 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46197 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46198 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46199 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46205 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46206 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46208 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46212 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46218 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46230 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46238 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46328 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52919 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52922 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52931 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52934 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53024 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53025 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53041 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53045 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53329 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53356 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53368 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53374 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53375 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53383 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-53386 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53387 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53390 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53401 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63793 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63796 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63805 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63806 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63814 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63815 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63817 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63818 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63819 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63825 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-63827 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63828 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63833 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63834 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63835 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63836 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63846 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63847 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63848 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63854 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63855 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63856 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63862 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63879 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63881 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63882 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63895 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63905 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63908 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63915 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63930 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63931 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63933 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63934 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63954 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63959 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63960 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63967 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64010 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64033 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64055 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64056 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-64083 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64084 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64085 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64086 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64087 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64088 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64089 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-64090 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64091 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-64093 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64094 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64095 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64096 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64097 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64135 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64138 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64164 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64165 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64166 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64168 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64188 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64218 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64219 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64221 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64234 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64241 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64242 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64246 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64249 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64269 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-64270 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64272 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64273 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64274 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64318 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64331 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64337 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64345 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64348 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64350 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64359 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64361 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64371 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64389 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64390 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64391 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64392 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64393 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64394 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64395 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64396 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64397 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64398 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64399 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64400 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64420 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64425 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64429 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64432 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64438 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64440 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64441 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64442 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64443 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64444 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64445 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64446 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64449 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64450 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64461 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64462 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64468 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64469 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64484 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64494 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64495 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64497 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64500 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64503 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64504 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64505 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64528 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64532 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64533 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64536 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64549 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64550 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31396 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31761 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43207 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43232 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43249 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43283 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43291 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43324 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43497 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46250 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46265 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46270 | NONE0 | linux-libc-dev 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53161 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53216 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53217 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53273 | NONE0 | linux-libc-dev 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68263 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43011 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-43185 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-53215 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-23268 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23372 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23393 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31405 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31432 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31433 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-31476 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31478 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31536 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31627 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31657 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31659 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31695 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31705 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31706 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31712 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31716 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31780 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43075 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43076 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43236 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43490 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52911 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52914 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53040 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53043 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53046 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53068 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53130 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53178 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53186 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53198 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-50634 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50708 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50759 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50785 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53707 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53714 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53742 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53748 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53855 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54047 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54059 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54105 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54125 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54151 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54180 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54187 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36331 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-27558 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-39985 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39986 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39987 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39988 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39995 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40003 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40012 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40025 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40032 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40036 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40043 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40054 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40055 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40060 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40068 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40073 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40077 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40084 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40087 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-40093 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40095 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40097 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40106 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40107 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40112 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40116 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40124 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40126 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40127 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40137 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40180 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40188 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40192 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40193 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40208 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40223 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40233 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40243 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40245 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40247 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40262 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40263 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40266 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40278 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40282 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40285 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40286 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40288 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40289 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40306 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40310 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40311 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40313 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40314 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40315 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40317 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40332 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40333 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40335 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40337 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40354 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40356 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40358 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-54505 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-62626 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68174 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68175 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68177 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68184 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68190 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68196 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68201 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68217 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68220 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68230 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68238 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68246 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-68249 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68254 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-68255 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-68256 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-68257 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68258 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68266 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68286 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68289 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68290 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68302 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-68303 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68311 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68315 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-68318 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68322 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68325 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68327 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68328 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68330 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68332 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68335 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68339 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68344 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68364 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68727 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68728 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68733 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68755 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68759 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68765 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68767 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68769 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68771 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68772 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68777 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68781 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68786 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68787 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68796 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68797 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68799 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-68804 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68806 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-68808 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68809 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-71067 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71069 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71192 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71195 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71196 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71197 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71198 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71199 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23033 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23037 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23049 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23056 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23176 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23182 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23245 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23269 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23364 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-23406 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23407 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31409 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31417 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31477 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31494 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31597 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31598 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31602 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31611 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31612 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31622 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31626 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31629 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31683 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31707 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31711 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31768 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43117 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-185.195 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43184 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43203 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43245 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43336 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43373 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43377 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43476 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45935 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45956 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45958 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46006 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46062 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46112 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46124 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46175 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46177 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46197 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46198 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46199 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46205 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46206 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46208 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46212 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46218 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46230 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46238 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46328 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52919 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52922 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52931 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52934 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53024 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53025 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53041 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53045 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53329 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53356 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53368 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53374 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53375 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53383 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-53386 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53387 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53390 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53401 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63793 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63796 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63805 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63806 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63814 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63815 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63817 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63818 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63819 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63825 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-63827 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63828 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63833 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63834 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63835 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63836 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63846 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63847 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63848 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63854 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63855 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63856 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63862 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63879 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63881 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63882 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63895 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63905 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63908 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63915 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63930 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63931 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63933 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63934 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63954 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63959 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63960 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63967 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64010 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64033 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64055 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64056 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-64083 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64084 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64085 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64086 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64087 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64088 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64089 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-64090 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64091 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-64093 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64094 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64095 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64096 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64097 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64135 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64138 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64164 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64165 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64166 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64168 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64188 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64218 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64219 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64221 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64234 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64241 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64242 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64246 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64249 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64269 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-64270 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64272 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64273 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64274 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64318 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64331 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64337 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64345 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64348 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64350 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64359 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64361 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64371 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64389 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64390 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64391 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64392 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64393 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64394 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64395 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64396 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64397 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64398 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64399 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64400 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64420 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64425 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64429 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64432 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64438 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64440 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64441 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64442 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64443 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64444 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64445 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64446 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64449 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64450 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64461 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64462 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64468 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64469 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64484 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64494 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64495 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64497 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64500 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64503 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64504 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64505 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64528 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64532 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64533 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64536 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64549 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64550 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31396 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31761 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43207 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43232 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43249 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43283 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43291 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43324 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43497 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46250 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46265 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46270 | NONE0 | linux-tools-common 5.15.0-164.174 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53161 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53216 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53217 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53273 | NONE0 | linux-tools-common 5.15.0-164.174 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-34317 | NONE0 | mysql-client 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-34318 | NONE0 | mysql-client 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-34319 | NONE0 | mysql-client 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46862 | NONE0 | mysql-client 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.3 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46863 | NONE0 | mysql-client 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.3 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-34317 | NONE0 | mysql-client-8.0 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-34318 | NONE0 | mysql-client-8.0 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-34319 | NONE0 | mysql-client-8.0 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46862 | NONE0 | mysql-client-8.0 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.3 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46863 | NONE0 | mysql-client-8.0 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.3 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-34317 | NONE0 | mysql-client-core-8.0 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-34318 | NONE0 | mysql-client-core-8.0 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-34319 | NONE0 | mysql-client-core-8.0 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46862 | NONE0 | mysql-client-core-8.0 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.3 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46863 | NONE0 | mysql-client-core-8.0 8.0.44-0ubuntu0.22.04.2 fixed in 8.0.46-0ubuntu0.22.04.3 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-8328 | NONE0 | python3.10 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.16 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-8328 | NONE0 | python3.10-minimal 3.10.12-1~22.04.12 fixed in 3.10.12-1~22.04.16 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43961 | NONE0 | vim 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.31 | — | Not Applicable |
| CVE-2026-43961 | NONE0 | vim-common 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.31 | — | Not Applicable |
| CVE-2026-43961 | NONE0 | vim-runtime 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.31 | — | Not Applicable |
| CVE-2026-43961 | NONE0 | xxd 2:8.2.3995-1ubuntu2.24 fixed in 2:8.2.3995-1ubuntu2.31 | — | Not Applicable |
| GHSA-r7wm-3cxj-wff9 | NONE0 | com.fasterxml.jackson.core:jackson-core 2.16.0 fixed in 2.18.8, 2.21.4, 2.22.1 | — | Not Applicable |
| GHSA-72hv-8253-57qq | NONE0 | com.fasterxml.jackson.core:jackson-core 2.16.0 fixed in 2.21.1, 2.18.6 | — | Not Applicable |
| GHSA-mfg7-5gfp-c4w3 | NONE0 | io.netty:netty-codec-dns 4.1.128.Final fixed in 4.2.16.Final, 4.1.136.Final | — | Not Applicable |
| GHSA-v74w-7mr3-4qg3 | NONE0 | io.netty:netty-codec-xml 4.1.128.Final fixed in 4.2.16.Final, 4.1.136.Final | — | Not Applicable |
| CVE-2026-6790 | NONE0 | org.eclipse.jetty:jetty-server 12.0.29 fixed in 12.0.35, 12.1.9 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-8384 | NONE0 | org.eclipse.jetty:jetty-util 12.0.29 fixed in 12.0.35, 12.1.9 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-56740 | NONE0 | org.jline:jline-remote-telnet 3.30.6 fixed in 4.2.1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-56741 | NONE0 | org.jline:jline-remote-telnet 3.30.6 fixed in 4.2.1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46600 | NONE0 | golang.org/x/net v0.33.0 fixed in 0.56.0 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39824 | NONE0 | golang.org/x/sys v0.28.0 fixed in 0.44.0 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56852 | NONE0 | golang.org/x/text v0.21.0 fixed in 0.39.0 | 0.4% Theoretical Threat | Not Applicable |
Which CVEs are actually reachable — is the vulnerable code even linked and callable.
Live-container probes: default user, writable paths, capabilities, exposed ports.
A step-by-step hardened build plan, with parity tests proving nothing breaks.
Want to check another image? Run a full scan with the Docker Security Scanner.