Last scanned:
This image poses a critical security risk and must not be used in production, especially as an internet-facing service. An attacker could exploit vulnerabilities like CVE-2026-6653 and CVE-2026-45447 to achieve remote code execution, compromise cryptographic operations, or cause denial of service, potentially leading to full system compromise and data breach. Immediate remediation by rebuilding the image with patched dependencies is required; no compensating controls can fully mitigate these risks.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-6653 | HIGH8.33 | libxml2 2.9.13-14.el9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-45447 | HIGH8.1 | openssl-libs 1:3.5.5-1.el9 fixed in 1:3.5.5-4.el9_8 | 5.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-60002 | HIGH7.99 | openssh 9.9p1-7.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-60002 | HIGH7.99 | openssh-server 9.9p1-7.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58016 | HIGH7.73 | glib2 2.68.4-19.el9 fixed in 2.68.4-19.el9_8.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-33845 | HIGH7.73 | gnutls 3.8.10-3.el9 fixed in 3.8.10-4.el9_8 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-45445 | HIGH7.73 | openssl-libs 1:3.5.5-1.el9 fixed in 1:3.5.5-4.el9_8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-32635 | HIGH7.65 | librados2 2:20.2.1-0.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-32635 | HIGH7.65 | librbd1 2:20.2.1-0.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-33846 | HIGH7.5 | gnutls 3.8.10-3.el9 fixed in 3.8.10-4.el9_8 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42009 | HIGH7.5 | gnutls 3.8.10-3.el9 fixed in 3.8.10-4.el9_8 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-5121 | HIGH7.5 | libarchive 3.5.3-8.el9 fixed in 3.5.3-9.el9_7 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-28390 | HIGH7.5 | libldb 4.23.5-6.el9 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21680 | HIGH7.5 | librados2 2:20.2.1-0.el9 No fix yet | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21681 | HIGH7.5 | librados2 2:20.2.1-0.el9 No fix yet | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21680 | HIGH7.5 | librbd1 2:20.2.1-0.el9 No fix yet | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21681 | HIGH7.5 | librbd1 2:20.2.1-0.el9 No fix yet | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2026-28390 | HIGH7.5 | libwbclient 4.23.5-6.el9 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2025-27113 | HIGH7.5 | libxml2 2.9.13-14.el9 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-28390 | HIGH7.5 | openssl-libs 1:3.5.5-1.el9 fixed in 1:3.5.5-3.el9_8 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-34183 | HIGH7.5 | openssl-libs 1:3.5.5-1.el9 fixed in 1:3.5.5-4.el9_8 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-28388 | HIGH7.5 | openssl-libs 1:3.5.5-1.el9 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-28389 | HIGH7.5 | openssl-libs 1:3.5.5-1.el9 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-41409 | HIGH7.5 | pcre2 10.40-6.el9 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-3651 | HIGH7.5 | python3-idna 2.10-7.el9.1 fixed in 2.10-7.el9_4.1 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-28390 | HIGH7.5 | samba-client-libs 4.23.5-6.el9 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-28390 | HIGH7.5 | samba-common 4.23.5-6.el9 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-28390 | HIGH7.5 | samba-common-libs 4.23.5-6.el9 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2025-61726 | HIGH7.5 | stdlib v1.22.10 fixed in 1.24.12, 1.25.6 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2025-67030 | HIGH7.48 | librados2 2:20.2.1-0.el9 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-67030 | HIGH7.48 | librbd1 2:20.2.1-0.el9 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-14474 | HIGH7.48 | libsss_idmap 2.9.8-1.el9 fixed in 2.9.8-4.el9_8.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-14474 | HIGH7.48 | libsss_nss_idmap 2.9.8-1.el9 fixed in 2.9.8-4.el9_8.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-27516 | HIGH7.48 | python3-jinja2 2.11.3-8.el9 fixed in 2.11.3-8.el9_5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-14474 | HIGH7.48 | sssd-client 2.9.8-1.el9 fixed in 2.9.8-4.el9_8.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-58014 | HIGH7.31 | glib2 2.68.4-19.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58010 | MEDIUM6.97 | glib2 2.68.4-19.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58012 | MEDIUM6.97 | glib2 2.68.4-19.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58013 | MEDIUM6.97 | glib2 2.68.4-19.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42013 | MEDIUM6.97 | gnutls 3.8.10-3.el9 fixed in 3.8.10-4.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5260 | MEDIUM6.97 | gnutls 3.8.10-3.el9 fixed in 3.8.10-4.el9_8 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-35385 | MEDIUM6.88 | openssh 9.9p1-7.el9 fixed in 9.9p1-7.el9_8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-35414 | MEDIUM6.88 | openssh 9.9p1-7.el9 fixed in 9.9p1-7.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-35386 | MEDIUM6.88 | openssh 9.9p1-7.el9 fixed in 9.9p1-7.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-35385 | MEDIUM6.88 | openssh-server 9.9p1-7.el9 fixed in 9.9p1-7.el9_8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-35414 | MEDIUM6.88 | openssh-server 9.9p1-7.el9 fixed in 9.9p1-7.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-35386 | MEDIUM6.88 | openssh-server 9.9p1-7.el9 fixed in 9.9p1-7.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-28387 | MEDIUM6.88 | openssl-libs 1:3.5.5-1.el9 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-6100 | MEDIUM6.88 | python3 3.9.25-5.el9 fixed in 3.9.25-7.el9_8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-6100 | MEDIUM6.88 | python3-libs 3.9.25-5.el9 fixed in 3.9.25-7.el9_8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-68121 | MEDIUM6.8 | stdlib v1.22.10 fixed in 1.24.13, 1.25.7, 1.26.0-rc.3 | 0.8% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-14476 | MEDIUM6.8 | libsss_idmap 2.9.8-1.el9 fixed in 2.9.8-4.el9_8.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-14476 | MEDIUM6.8 | libsss_nss_idmap 2.9.8-1.el9 fixed in 2.9.8-4.el9_8.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-14476 | MEDIUM6.8 | sssd-client 2.9.8-1.el9 fixed in 2.9.8-4.el9_8.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-48864 | MEDIUM6.63 | libsolv 0.7.24-4.el9 fixed in 0.7.24-6.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-11979 | MEDIUM6.63 | libxml2 2.9.13-14.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-55549 | MEDIUM6.63 | libxslt 1.1.34-12.el9 fixed in 1.1.34-13.el9_6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-29111 | MEDIUM6.63 | systemd-libs 252-67.el9 fixed in 252-67.el9_8.2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-29111 | MEDIUM6.63 | systemd-pam 252-67.el9 fixed in 252-67.el9_8.2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-39822 | MEDIUM6.63 | stdlib v1.26.4 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-39822 | MEDIUM6.63 | stdlib v1.22.10 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-40403 | MEDIUM6.5 | libxslt 1.1.34-12.el9 fixed in 1.1.34-14.el9_7.1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-45186 | MEDIUM6.38 | expat 2.5.0-6.el9 fixed in 2.5.0-6.el9_8.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-58011 | MEDIUM6.38 | glib2 2.68.4-19.el9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-58015 | MEDIUM6.38 | glib2 2.68.4-19.el9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-32636 | MEDIUM6.38 | glib2 2.68.4-19.el9 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM6.38 | krb5-libs 1.21.1-9.el9 fixed in 1.21.1-10.el9_8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM6.38 | krb5-libs 1.21.1-9.el9 fixed in 1.21.1-10.el9_8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4424 | MEDIUM6.38 | libarchive 3.5.3-8.el9 fixed in 3.5.3-9.el9_7 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-14164 | MEDIUM6.38 | libarchive 3.5.3-8.el9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-6176 | MEDIUM6.38 | libbrotli 1.0.9-9.el9 fixed in 1.0.9-9.el9_7 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-41989 | MEDIUM6.38 | libgcrypt 1.10.0-11.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40170 | MEDIUM6.38 | libldb 4.23.5-6.el9 fixed in 4.23.5-10.el9_8 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-27135 | MEDIUM6.38 | libnghttp2 1.43.0-6.el9 fixed in 1.43.0-6.el9_7.1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-45736 | MEDIUM6.38 | librados2 2:20.2.1-0.el9 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-48779 | MEDIUM6.38 | librados2 2:20.2.1-0.el9 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-45736 | MEDIUM6.38 | librbd1 2:20.2.1-0.el9 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-48779 | MEDIUM6.38 | librbd1 2:20.2.1-0.el9 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-40170 | MEDIUM6.38 | libwbclient 4.23.5-6.el9 fixed in 4.23.5-10.el9_8 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-6732 | MEDIUM6.38 | libxml2 2.9.13-14.el9 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-59999 | MEDIUM6.38 | openssh 9.9p1-7.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-60000 | MEDIUM6.38 | openssh 9.9p1-7.el9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-59999 | MEDIUM6.38 | openssh-server 9.9p1-7.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-60000 | MEDIUM6.38 | openssh-server 9.9p1-7.el9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0994 | MEDIUM6.38 | protobuf 3.14.0-17.el9 fixed in 3.14.0-17.el9_7 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-15308 | MEDIUM6.38 | python3 3.9.25-5.el9 fixed in 3.9.25-7.el9_8.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-3644 | MEDIUM6.38 | python3 3.9.25-5.el9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4224 | MEDIUM6.38 | python3 3.9.25-5.el9 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-7210 | MEDIUM6.38 | python3 3.9.25-5.el9 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-49083 | MEDIUM6.38 | python3-cryptography 36.0.1-5.el9 fixed in 36.0.1-5.el9_6 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-15308 | MEDIUM6.38 | python3-libs 3.9.25-5.el9 fixed in 3.9.25-7.el9_8.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-3644 | MEDIUM6.38 | python3-libs 3.9.25-5.el9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4224 | MEDIUM6.38 | python3-libs 3.9.25-5.el9 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-7210 | MEDIUM6.38 | python3-libs 3.9.25-5.el9 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-0994 | MEDIUM6.38 | python3-protobuf 3.14.0-17.el9 fixed in 3.14.0-17.el9_7 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-23490 | MEDIUM6.38 | python3-pyasn1 0.4.8-7.el9 fixed in 0.4.8-7.el9_7 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-59885 | MEDIUM6.38 | python3-pyasn1 0.4.8-7.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-59886 | MEDIUM6.38 | python3-pyasn1 0.4.8-7.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-23490 | MEDIUM6.38 | python3-pyasn1-modules 0.4.8-7.el9 fixed in 0.4.8-7.el9_7 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-59885 | MEDIUM6.38 | python3-pyasn1-modules 0.4.8-7.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-59886 | MEDIUM6.38 | python3-pyasn1-modules 0.4.8-7.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-44432 | MEDIUM6.38 | python3-urllib3 1.26.5-7.el9 fixed in 1.26.5-8.el9_8 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-40170 | MEDIUM6.38 | samba-client-libs 4.23.5-6.el9 fixed in 4.23.5-10.el9_8 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-40170 | MEDIUM6.38 | samba-common 4.23.5-6.el9 fixed in 4.23.5-10.el9_8 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-40170 | MEDIUM6.38 | samba-common-libs 4.23.5-6.el9 fixed in 4.23.5-10.el9_8 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-61729 | MEDIUM6.38 | stdlib v1.22.10 fixed in 1.24.11, 1.25.5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25679 | MEDIUM6.38 | stdlib v1.22.10 fixed in 1.25.8, 1.26.1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-27145 | MEDIUM6.38 | stdlib v1.22.10 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-32280 | MEDIUM6.38 | stdlib v1.22.10 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-32281 | MEDIUM6.38 | stdlib v1.22.10 fixed in 1.25.9, 1.26.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-32283 | MEDIUM6.38 | stdlib v1.22.10 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-33811 | MEDIUM6.38 | stdlib v1.22.10 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-33814 | MEDIUM6.38 | stdlib v1.22.10 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-39820 | MEDIUM6.38 | stdlib v1.22.10 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-39836 | MEDIUM6.38 | stdlib v1.22.10 fixed in 1.25.10, 1.26.3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42499 | MEDIUM6.38 | stdlib v1.22.10 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-42504 | MEDIUM6.38 | stdlib v1.22.10 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-58183 | MEDIUM6.38 | stdlib v1.22.10 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-61728 | MEDIUM6.38 | stdlib v1.22.10 fixed in 1.24.12, 1.25.6 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-3833 | MEDIUM6.29 | gnutls 3.8.10-3.el9 fixed in 3.8.10-4.el9_8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42011 | MEDIUM6.29 | gnutls 3.8.10-3.el9 fixed in 3.8.10-4.el9_8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-34182 | MEDIUM6.29 | openssl-libs 1:3.5.5-1.el9 fixed in 1:3.5.5-4.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-16118 | MEDIUM6.03 | glib2 2.68.4-19.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42012 | MEDIUM6.03 | gnutls 3.8.10-3.el9 fixed in 3.8.10-4.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-54369 | MEDIUM6.03 | libacl 2.3.1-4.el9 fixed in 2.4.0-1.el9_8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66035 | MEDIUM6.03 | librados2 2:20.2.1-0.el9 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-66035 | MEDIUM6.03 | librbd1 2:20.2.1-0.el9 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4786 | MEDIUM6.03 | python3 3.9.25-5.el9 fixed in 3.9.25-7.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4786 | MEDIUM6.03 | python3-libs 3.9.25-5.el9 fixed in 3.9.25-7.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4878 | MEDIUM5.95 | libcap 2.48-10.el9 fixed in 2.48-10.el9_8.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5222 | MEDIUM5.95 | libicu 67.1-10.el9 fixed in 67.1-10.el9_6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-51767 | MEDIUM5.95 | openssh 9.9p1-7.el9 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-51767 | MEDIUM5.95 | openssh-server 9.9p1-7.el9 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-44604 | MEDIUM5.95 | python3-rpm 4.16.1.3-40.el9 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-44604 | MEDIUM5.95 | rpm-build-libs 4.16.1.3-40.el9 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-44604 | MEDIUM5.95 | rpm-libs 4.16.1.3-40.el9 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-44604 | MEDIUM5.95 | rpm-plugin-selinux 4.16.1.3-40.el9 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-44604 | MEDIUM5.95 | rpm-sign-libs 4.16.1.3-40.el9 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-47907 | MEDIUM5.95 | stdlib v1.22.10 fixed in 1.23.12, 1.24.6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-37890 | MEDIUM5.9 | librados2 2:20.2.1-0.el9 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2024-37890 | MEDIUM5.9 | librbd1 2:20.2.1-0.el9 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2025-13151 | MEDIUM5.9 | libtasn1 4.16.0-9.el9 fixed in 4.16.0-10.el9_8 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-31790 | MEDIUM5.9 | openssl-libs 1:3.5.5-1.el9 fixed in 1:3.5.5-2.el9_8 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42764 | MEDIUM5.9 | openssl-libs 1:3.5.5-1.el9 fixed in 1:3.5.5-4.el9_8 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-41996 | MEDIUM5.9 | openssl-libs 1:3.5.5-1.el9 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-56132 | MEDIUM5.87 | expat 2.5.0-6.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56403 | MEDIUM5.87 | expat 2.5.0-6.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56405 | MEDIUM5.87 | expat 2.5.0-6.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56406 | MEDIUM5.87 | expat 2.5.0-6.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3012 | MEDIUM5.78 | libldb 4.23.5-6.el9 fixed in 4.23.5-10.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-3012 | MEDIUM5.78 | libwbclient 4.23.5-6.el9 fixed in 4.23.5-10.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-22185 | MEDIUM5.78 | openldap 2.6.8-4.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3012 | MEDIUM5.78 | samba-client-libs 4.23.5-6.el9 fixed in 4.23.5-10.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-3012 | MEDIUM5.78 | samba-common 4.23.5-6.el9 fixed in 4.23.5-10.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-3012 | MEDIUM5.78 | samba-common-libs 4.23.5-6.el9 fixed in 4.23.5-10.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-4673 | MEDIUM5.78 | stdlib v1.22.10 fixed in 1.23.10, 1.24.4 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4105 | MEDIUM5.7 | systemd-libs 252-67.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4105 | MEDIUM5.7 | systemd-pam 252-67.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42014 | MEDIUM5.61 | gnutls 3.8.10-3.el9 fixed in 3.8.10-4.el9_8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-5915 | MEDIUM5.61 | libarchive 3.5.3-8.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5918 | MEDIUM5.61 | libarchive 3.5.3-8.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-68468 | MEDIUM5.52 | avahi-libs 0.8-24.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-68471 | MEDIUM5.52 | avahi-libs 0.8-24.el9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-24401 | MEDIUM5.52 | avahi-libs 0.8-24.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-14512 | MEDIUM5.52 | glib2 2.68.4-19.el9 fixed in 2.68.4-19.el9_8.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | glibc 2.34-262.el9 fixed in 2.34-270.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | glibc 2.34-262.el9 fixed in 2.34-274.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | glibc-common 2.34-262.el9 fixed in 2.34-270.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | glibc-common 2.34-262.el9 fixed in 2.34-274.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | glibc-gconv-extra 2.34-262.el9 fixed in 2.34-270.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | glibc-gconv-extra 2.34-262.el9 fixed in 2.34-274.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4426 | MEDIUM5.52 | libarchive 3.5.3-8.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-1933 | MEDIUM5.52 | libldb 4.23.5-6.el9 fixed in 4.23.5-10.el9_8 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-2340 | MEDIUM5.52 | libldb 4.23.5-6.el9 fixed in 4.23.5-10.el9_8 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-25727 | MEDIUM5.52 | libldb 4.23.5-6.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-52555 | MEDIUM5.52 | librados2 2:20.2.1-0.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-52555 | MEDIUM5.52 | librbd1 2:20.2.1-0.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-9149 | MEDIUM5.52 | libsolv 0.7.24-4.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-9150 | MEDIUM5.52 | libsolv 0.7.24-4.el9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-1933 | MEDIUM5.52 | libwbclient 4.23.5-6.el9 fixed in 4.23.5-10.el9_8 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-2340 | MEDIUM5.52 | libwbclient 4.23.5-6.el9 fixed in 4.23.5-10.el9_8 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-25727 | MEDIUM5.52 | libwbclient 4.23.5-6.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-45322 | MEDIUM5.52 | libxml2 2.9.13-14.el9 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-55653 | MEDIUM5.52 | openssh 9.9p1-7.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-59998 | MEDIUM5.52 | openssh 9.9p1-7.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-60001 | MEDIUM5.52 | openssh 9.9p1-7.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-35387 | MEDIUM5.52 | openssh 9.9p1-7.el9 fixed in 9.9p1-7.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-55653 | MEDIUM5.52 | openssh-server 9.9p1-7.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-59998 | MEDIUM5.52 | openssh-server 9.9p1-7.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-60001 | MEDIUM5.52 | openssh-server 9.9p1-7.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-35387 | MEDIUM5.52 | openssh-server 9.9p1-7.el9 fixed in 9.9p1-7.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-2673 | MEDIUM5.52 | openssl-fips-provider 1:3.5.5-1.el9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-2673 | MEDIUM5.52 | openssl-libs 1:3.5.5-1.el9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-11972 | MEDIUM5.52 | python3 3.9.25-5.el9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-11972 | MEDIUM5.52 | python3-libs 3.9.25-5.el9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-16277 | MEDIUM5.52 | rpcbind 1.2.6-7.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-16461 | MEDIUM5.52 | rpcbind 1.2.6-7.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-1933 | MEDIUM5.52 | samba-client-libs 4.23.5-6.el9 fixed in 4.23.5-10.el9_8 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-2340 | MEDIUM5.52 | samba-client-libs 4.23.5-6.el9 fixed in 4.23.5-10.el9_8 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-25727 | MEDIUM5.52 | samba-client-libs 4.23.5-6.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-1933 | MEDIUM5.52 | samba-common 4.23.5-6.el9 fixed in 4.23.5-10.el9_8 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-2340 | MEDIUM5.52 | samba-common 4.23.5-6.el9 fixed in 4.23.5-10.el9_8 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-25727 | MEDIUM5.52 | samba-common 4.23.5-6.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-1933 | MEDIUM5.52 | samba-common-libs 4.23.5-6.el9 fixed in 4.23.5-10.el9_8 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-2340 | MEDIUM5.52 | samba-common-libs 4.23.5-6.el9 fixed in 4.23.5-10.el9_8 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-25727 | MEDIUM5.52 | samba-common-libs 4.23.5-6.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-47906 | MEDIUM5.52 | stdlib v1.22.10 fixed in 1.23.12, 1.24.6 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-61727 | MEDIUM5.52 | stdlib v1.22.10 fixed in 1.24.11, 1.25.5 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-39825 | MEDIUM5.52 | stdlib v1.22.10 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-34459 | MEDIUM5.5 | libxml2 2.9.13-14.el9 fixed in 2.9.13-14.el9_8.1 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-44605 | MEDIUM5.5 | python3-rpm 4.16.1.3-40.el9 No fix yet | — | Directly Exposed |
| CVE-2026-44605 | MEDIUM5.5 | rpm-build-libs 4.16.1.3-40.el9 No fix yet | — | Directly Exposed |
| CVE-2026-44605 | MEDIUM5.5 | rpm-libs 4.16.1.3-40.el9 No fix yet | — | Directly Exposed |
| CVE-2026-44605 | MEDIUM5.5 | rpm-plugin-selinux 4.16.1.3-40.el9 No fix yet | — | Directly Exposed |
| CVE-2026-44605 | MEDIUM5.5 | rpm-sign-libs 4.16.1.3-40.el9 No fix yet | — | Directly Exposed |
| CVE-2024-6485 | MEDIUM5.44 | librados2 2:20.2.1-0.el9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-6485 | MEDIUM5.44 | librbd1 2:20.2.1-0.el9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-12610 | MEDIUM5.44 | libsss_idmap 2.9.8-1.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-12610 | MEDIUM5.44 | libsss_nss_idmap 2.9.8-1.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-12610 | MEDIUM5.44 | sssd-client 2.9.8-1.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-32282 | MEDIUM5.44 | stdlib v1.22.10 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54370 | MEDIUM5.35 | libacl 2.3.1-4.el9 fixed in 2.4.0-1.el9_8 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-54371 | MEDIUM5.35 | libattr 2.5.1-3.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34181 | MEDIUM5.35 | openssl-libs 1:3.5.5-1.el9 fixed in 1:3.5.5-4.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42768 | MEDIUM5.35 | openssl-libs 1:3.5.5-1.el9 fixed in 1:3.5.5-4.el9_8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-13465 | MEDIUM5.3 | librados2 2:20.2.1-0.el9 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2025-13465 | MEDIUM5.3 | librbd1 2:20.2.1-0.el9 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2021-33430 | MEDIUM5.3 | python3-numpy 1:1.23.5-2.el9 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-34141 | MEDIUM5.3 | python3-numpy 1:1.23.5-2.el9 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-1757 | MEDIUM5.27 | libxml2 2.9.13-14.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13757 | MEDIUM5.27 | p11-kit 0.26.2-1.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-13757 | MEDIUM5.27 | p11-kit-trust 0.26.2-1.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27970 | MEDIUM5.18 | librados2 2:20.2.1-0.el9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-27970 | MEDIUM5.18 | librbd1 2:20.2.1-0.el9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-55655 | MEDIUM5.18 | openssh 9.9p1-7.el9 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55655 | MEDIUM5.18 | openssh-server 9.9p1-7.el9 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6019 | MEDIUM5.18 | python3 3.9.25-5.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6019 | MEDIUM5.18 | python3-libs 3.9.25-5.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32289 | MEDIUM5.18 | stdlib v1.22.10 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5713 | MEDIUM5.1 | python3 3.9.25-5.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5713 | MEDIUM5.1 | python3-libs 3.9.25-5.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-62408 | MEDIUM5.02 | c-ares 1.19.1-2.el9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-50219 | MEDIUM5.02 | expat 2.5.0-6.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-56412 | MEDIUM5.02 | expat 2.5.0-6.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | glibc 2.34-262.el9 fixed in 2.34-274.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | glibc-common 2.34-262.el9 fixed in 2.34-274.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | glibc-gconv-extra 2.34-262.el9 fixed in 2.34-274.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-0990 | MEDIUM5.02 | libxml2 2.9.13-14.el9 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-42769 | MEDIUM5.02 | openssl-libs 1:3.5.5-1.el9 fixed in 1:3.5.5-4.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42770 | MEDIUM5.02 | openssl-libs 1:3.5.5-1.el9 fixed in 1:3.5.5-4.el9_8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-9076 | MEDIUM5.02 | openssl-libs 1:3.5.5-1.el9 fixed in 1:3.5.5-4.el9_8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-41066 | MEDIUM5.02 | python3-lxml 4.6.5-3.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-59884 | MEDIUM5.02 | python3-pyasn1 0.4.8-7.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-59884 | MEDIUM5.02 | python3-pyasn1-modules 0.4.8-7.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-45336 | MEDIUM5.02 | stdlib v1.22.10 fixed in 1.22.11, 1.23.5, 1.24.0-rc.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-34180 | MEDIUM5 | openssl-libs 1:3.5.5-1.el9 fixed in 1:3.5.5-4.el9_8 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2025-5916 | MEDIUM4.76 | libarchive 3.5.3-8.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1647 | MEDIUM4.76 | librados2 2:20.2.1-0.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1647 | MEDIUM4.76 | librbd1 2:20.2.1-0.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2021-45078 | MEDIUM4.68 | binutils 2.35.2-72.el9 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2021-45078 | MEDIUM4.68 | binutils-gold 2.35.2-72.el9 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2022-23222 | MEDIUM4.68 | kernel-headers 5.14.0-688.el9 No fix yet | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2022-25265 | MEDIUM4.68 | kernel-headers 5.14.0-688.el9 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2021-3927 | MEDIUM4.68 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2021-3973 | MEDIUM4.68 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2021-3974 | MEDIUM4.68 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2021-4136 | MEDIUM4.68 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2021-4173 | MEDIUM4.68 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2021-4187 | MEDIUM4.68 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2022-1616 | MEDIUM4.68 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2022-1619 | MEDIUM4.68 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 2.6% Low-Moderate Risk | Post-Exploit |
| CVE-2022-1720 | MEDIUM4.68 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 2.1% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2042 | MEDIUM4.68 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2124 | MEDIUM4.68 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2125 | MEDIUM4.68 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2126 | MEDIUM4.68 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2129 | MEDIUM4.68 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2175 | MEDIUM4.68 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2182 | MEDIUM4.68 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2183 | MEDIUM4.68 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2206 | MEDIUM4.68 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2207 | MEDIUM4.68 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2210 | MEDIUM4.68 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2257 | MEDIUM4.68 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2284 | MEDIUM4.68 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2285 | MEDIUM4.68 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2286 | MEDIUM4.68 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2304 | MEDIUM4.68 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2343 | MEDIUM4.68 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2344 | MEDIUM4.68 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2345 | MEDIUM4.68 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2025-59529 | MEDIUM4.67 | avahi-libs 0.8-24.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68276 | MEDIUM4.67 | avahi-libs 0.8-24.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34933 | MEDIUM4.67 | avahi-libs 0.8-24.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-25629 | MEDIUM4.67 | c-ares 1.19.1-2.el9 fixed in 1.19.1-2.el9_4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-16730 | MEDIUM4.67 | dbus-broker 28-7.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1371 | MEDIUM4.67 | elfutils-libelf 0.194-1.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1377 | MEDIUM4.67 | elfutils-libelf 0.194-1.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1371 | MEDIUM4.67 | elfutils-libs 0.194-1.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1377 | MEDIUM4.67 | elfutils-libs 0.194-1.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-32776 | MEDIUM4.67 | expat 2.5.0-6.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32777 | MEDIUM4.67 | expat 2.5.0-6.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32778 | MEDIUM4.67 | expat 2.5.0-6.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66382 | MEDIUM4.67 | expat 2.5.0-6.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-60753 | MEDIUM4.67 | libarchive 3.5.3-8.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5745 | MEDIUM4.67 | libarchive 3.5.3-8.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1632 | MEDIUM4.67 | libarchive 3.5.3-8.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2021-46195 | MEDIUM4.67 | libgcc 11.5.0-14.el9 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libgcc 11.5.0-14.el9 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2021-46195 | MEDIUM4.67 | libgfortran 11.5.0-14.el9 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libgfortran 11.5.0-14.el9 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2021-46195 | MEDIUM4.67 | libgomp 11.5.0-14.el9 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libgomp 11.5.0-14.el9 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2023-24056 | MEDIUM4.67 | libpkgconf 1.7.3-10.el9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2021-46195 | MEDIUM4.67 | libquadmath 11.5.0-14.el9 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libquadmath 11.5.0-14.el9 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-6245 | MEDIUM4.67 | libsss_idmap 2.9.8-1.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6245 | MEDIUM4.67 | libsss_nss_idmap 2.9.8-1.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2021-46195 | MEDIUM4.67 | libstdc++ 11.5.0-14.el9 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libstdc++ 11.5.0-14.el9 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-9714 | MEDIUM4.67 | libxml2 2.9.13-14.el9 fixed in 2.9.13-14.el9_7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-10911 | MEDIUM4.67 | libxslt 1.1.34-12.el9 fixed in 1.1.34-14.el9_8.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-7383 | MEDIUM4.67 | openssl-libs 1:3.5.5-1.el9 fixed in 1:3.5.5-4.el9_8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-13837 | MEDIUM4.67 | python3 3.9.25-5.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42308 | MEDIUM4.67 | python3 3.9.25-5.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-13837 | MEDIUM4.67 | python3-libs 3.9.25-5.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42308 | MEDIUM4.67 | python3-libs 3.9.25-5.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-25399 | MEDIUM4.67 | python3-scipy 1.9.3-2.el9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-0232 | MEDIUM4.67 | sqlite-libs 3.34.1-9.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6245 | MEDIUM4.67 | sssd-client 2.9.8-1.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27171 | MEDIUM4.67 | zlib 1.2.11-41.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32288 | MEDIUM4.67 | stdlib v1.22.10 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-45445 | MEDIUM4.64 | openssl 1:3.5.5-1.el9 fixed in 1:3.5.5-4.el9_8 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-1489 | MEDIUM4.59 | glib2 2.68.4-19.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58055 | MEDIUM4.59 | libnghttp2 1.43.0-6.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66412 | MEDIUM4.59 | librados2 2:20.2.1-0.el9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-66412 | MEDIUM4.59 | librbd1 2:20.2.1-0.el9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-59995 | MEDIUM4.59 | openssh 9.9p1-7.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-59996 | MEDIUM4.59 | openssh 9.9p1-7.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-59997 | MEDIUM4.59 | openssh 9.9p1-7.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-59995 | MEDIUM4.59 | openssh-server 9.9p1-7.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-59996 | MEDIUM4.59 | openssh-server 9.9p1-7.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-59997 | MEDIUM4.59 | openssh-server 9.9p1-7.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22871 | MEDIUM4.59 | stdlib v1.22.10 fixed in 1.23.8, 1.24.2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-27142 | MEDIUM4.59 | stdlib v1.22.10 fixed in 1.25.8, 1.26.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-39823 | MEDIUM4.59 | stdlib v1.22.10 fixed in 1.25.10, 1.26.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-39826 | MEDIUM4.59 | stdlib v1.22.10 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-2156 | MEDIUM4.5 | kernel-headers 5.14.0-688.el9 No fix yet | 6.1% Low-Moderate Risk | Post-Exploit |
| CVE-2023-0045 | MEDIUM4.5 | kernel-headers 5.14.0-688.el9 No fix yet | 2.4% Low-Moderate Risk | Post-Exploit |
| CVE-2026-28390 | MEDIUM4.5 | openssl 1:3.5.5-1.el9 fixed in 1:3.5.5-3.el9_8 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-34183 | MEDIUM4.5 | openssl 1:3.5.5-1.el9 fixed in 1:3.5.5-4.el9_8 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-28388 | MEDIUM4.5 | openssl 1:3.5.5-1.el9 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-28389 | MEDIUM4.5 | openssl 1:3.5.5-1.el9 No fix yet | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2022-1620 | MEDIUM4.5 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2022-3705 | MEDIUM4.5 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2023-5344 | MEDIUM4.5 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-65698 | MEDIUM4.5 | device-mapper-persistent-data 1.1.0-1.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-15588 | MEDIUM4.5 | glib2 2.68.4-19.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | glibc 2.34-262.el9 fixed in 2.34-270.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | glibc-common 2.34-262.el9 fixed in 2.34-270.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | glibc-gconv-extra 2.34-262.el9 fixed in 2.34-270.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42015 | MEDIUM4.5 | gnutls 3.8.10-3.el9 fixed in 3.8.10-4.el9_8 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-30571 | MEDIUM4.5 | libarchive 3.5.3-8.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libblkid 2.37.4-25.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libfdisk 2.37.4-25.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libmount 2.37.4-25.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-2950 | MEDIUM4.5 | librados2 2:20.2.1-0.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-2950 | MEDIUM4.5 | librbd1 2:20.2.1-0.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libsmartcols 2.37.4-25.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libuuid 2.37.4-25.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42766 | MEDIUM4.5 | openssl-libs 1:3.5.5-1.el9 fixed in 1:3.5.5-4.el9_8 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-42767 | MEDIUM4.5 | openssl-libs 1:3.5.5-1.el9 fixed in 1:3.5.5-4.el9_8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-4565 | MEDIUM4.5 | protobuf 3.14.0-17.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-12781 | MEDIUM4.5 | python3 3.9.25-5.el9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3276 | MEDIUM4.5 | python3 3.9.25-5.el9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-45409 | MEDIUM4.5 | python3-idna 2.10-7.el9.1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-12781 | MEDIUM4.5 | python3-libs 3.9.25-5.el9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3276 | MEDIUM4.5 | python3-libs 3.9.25-5.el9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-4565 | MEDIUM4.5 | python3-protobuf 3.14.0-17.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-47081 | MEDIUM4.5 | python3-requests 2.25.1-10.el9 fixed in 2.25.1-10.el9_6 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-44431 | MEDIUM4.5 | python3-urllib3 1.26.5-7.el9 fixed in 1.26.5-8.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-34743 | MEDIUM4.5 | xz-libs 5.2.5-8.el9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42505 | MEDIUM4.5 | stdlib v1.26.4 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-22866 | MEDIUM4.5 | stdlib v1.22.10 fixed in 1.22.12, 1.23.6, 1.24.0-rc.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-22873 | MEDIUM4.5 | stdlib v1.22.10 fixed in 1.23.9, 1.24.3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-47912 | MEDIUM4.5 | stdlib v1.22.10 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-58185 | MEDIUM4.5 | stdlib v1.22.10 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-58187 | MEDIUM4.5 | stdlib v1.22.10 fixed in 1.24.9, 1.25.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-58188 | MEDIUM4.5 | stdlib v1.22.10 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-58189 | MEDIUM4.5 | stdlib v1.22.10 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-61723 | MEDIUM4.5 | stdlib v1.22.10 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-61724 | MEDIUM4.5 | stdlib v1.22.10 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-61725 | MEDIUM4.5 | stdlib v1.22.10 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-61730 | MEDIUM4.5 | stdlib v1.22.10 fixed in 1.24.12, 1.25.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42505 | MEDIUM4.5 | stdlib v1.22.10 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42507 | MEDIUM4.5 | stdlib v1.22.10 fixed in 1.25.11, 1.26.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-58186 | MEDIUM4.5 | stdlib v1.22.10 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-23395 | MEDIUM4.49 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-47162 | MEDIUM4.49 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-7264 | MEDIUM4.48 | curl-minimal 7.76.1-41.el9 No fix yet | 17.3% High Exploitation Risk | Post-Exploit |
| CVE-2024-7264 | MEDIUM4.48 | libcurl-minimal 7.76.1-41.el9 No fix yet | 17.3% High Exploitation Risk | Post-Exploit |
| CVE-2025-4516 | MEDIUM4.33 | python3 3.9.25-5.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-4516 | MEDIUM4.33 | python3-libs 3.9.25-5.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-4204 | MEDIUM4.26 | kernel-headers 5.14.0-688.el9 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2021-4166 | MEDIUM4.26 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2287 | MEDIUM4.26 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-42250 | MEDIUM4.25 | bzip2-libs 1.0.8-11.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | glibc 2.34-262.el9 fixed in 2.34-272.el9_8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | glibc 2.34-262.el9 fixed in 2.34-274.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | glibc-common 2.34-262.el9 fixed in 2.34-272.el9_8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | glibc-common 2.34-262.el9 fixed in 2.34-274.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | glibc-gconv-extra 2.34-262.el9 fixed in 2.34-272.el9_8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | glibc-gconv-extra 2.34-262.el9 fixed in 2.34-274.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | krb5-libs 1.21.1-9.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5917 | MEDIUM4.25 | libarchive 3.5.3-8.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31788 | MEDIUM4.18 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-52859 | MEDIUM4.18 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-0620 | MEDIUM4.17 | libldb 4.23.5-6.el9 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-0620 | MEDIUM4.17 | libwbclient 4.23.5-6.el9 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-0620 | MEDIUM4.17 | samba-client-libs 4.23.5-6.el9 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-0620 | MEDIUM4.17 | samba-common 4.23.5-6.el9 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-0620 | MEDIUM4.17 | samba-common-libs 4.23.5-6.el9 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-8286 | MEDIUM4.13 | curl-minimal 7.76.1-41.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8925 | MEDIUM4.13 | curl-minimal 7.76.1-41.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | MEDIUM4.13 | curl-minimal 7.76.1-41.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-43114 | MEDIUM4.13 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8286 | MEDIUM4.13 | libcurl-minimal 7.76.1-41.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8925 | MEDIUM4.13 | libcurl-minimal 7.76.1-41.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | MEDIUM4.13 | libcurl-minimal 7.76.1-41.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-35385 | MEDIUM4.13 | openssh-clients 9.9p1-7.el9 fixed in 9.9p1-7.el9_8 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-35414 | MEDIUM4.13 | openssh-clients 9.9p1-7.el9 fixed in 9.9p1-7.el9_8 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-35386 | MEDIUM4.13 | openssh-clients 9.9p1-7.el9 fixed in 9.9p1-7.el9_8 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-28387 | MEDIUM4.13 | openssl 1:3.5.5-1.el9 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-6100 | MEDIUM4.13 | python3-devel 3.9.25-5.el9 fixed in 3.9.25-7.el9_8 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2022-50386 | MEDIUM4.08 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3534 | MEDIUM4.08 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-15282 | MEDIUM4.08 | python3 3.9.25-5.el9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-0672 | MEDIUM4.08 | python3 3.9.25-5.el9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15282 | MEDIUM4.08 | python3-libs 3.9.25-5.el9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-0672 | MEDIUM4.08 | python3-libs 3.9.25-5.el9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4480 | MEDIUM4.06 | libldb 4.23.5-6.el9 fixed in 4.23.5-10.el9_8 | 13.9% High Exploitation Risk | Post-Exploit |
| CVE-2026-4480 | MEDIUM4.06 | libwbclient 4.23.5-6.el9 fixed in 4.23.5-10.el9_8 | 13.9% High Exploitation Risk | Post-Exploit |
| CVE-2026-4480 | MEDIUM4.06 | samba-client-libs 4.23.5-6.el9 fixed in 4.23.5-10.el9_8 | 13.9% High Exploitation Risk | Post-Exploit |
| CVE-2026-4480 | MEDIUM4.06 | samba-common 4.23.5-6.el9 fixed in 4.23.5-10.el9_8 | 13.9% High Exploitation Risk | Post-Exploit |
| CVE-2026-4480 | MEDIUM4.06 | samba-common-libs 4.23.5-6.el9 fixed in 4.23.5-10.el9_8 | 13.9% High Exploitation Risk | Post-Exploit |
| CVE-2026-43133 | MEDIUM4.03 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1376 | MEDIUM4 | elfutils-libelf 0.194-1.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1376 | MEDIUM4 | elfutils-libs 0.194-1.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libblkid 2.37.4-25.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libfdisk 2.37.4-25.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libmount 2.37.4-25.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libsmartcols 2.37.4-25.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libuuid 2.37.4-25.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-13176 | MEDIUM4 | openssl-libs 1:3.5.5-1.el9 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-5206 | MEDIUM4 | scikit-learn 1.4.1.post1 fixed in 1.5.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | LOW3.98 | binutils 2.35.2-72.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW3.98 | binutils 2.35.2-72.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-7545 | LOW3.98 | binutils 2.35.2-72.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-44840 | LOW3.98 | binutils 2.35.2-72.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-11082 | LOW3.98 | binutils-gold 2.35.2-72.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW3.98 | binutils-gold 2.35.2-72.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-7545 | LOW3.98 | binutils-gold 2.35.2-72.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-44840 | LOW3.98 | binutils-gold 2.35.2-72.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-11082 | LOW3.98 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11083 | LOW3.98 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW3.98 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52922 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-53107 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53141 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-23185 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45998 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53262 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2021-34866 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2021-46999 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-47017 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47103 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2021-47561 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-0500 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-3424 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48637 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48744 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48778 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48783 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48787 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48834 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-48837 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-48848 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48913 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48943 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48950 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-48951 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48981 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48990 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48991 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49006 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49014 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49015 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49017 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49029 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49062 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49377 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49384 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49410 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49455 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49508 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49581 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49720 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49779 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49811 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49840 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49882 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49892 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49900 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49921 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50066 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50142 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50220 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50258 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50303 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50305 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50315 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50320 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50328 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50329 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50401 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50406 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50411 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50412 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50419 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50422 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50423 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50433 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50470 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50488 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50543 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50552 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50630 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-1118 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-3640 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2023-52469 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-52707 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-52752 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52835 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-52846 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52854 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52885 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52906 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52930 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-52988 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-53037 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53039 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53053 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53065 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53072 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53075 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53077 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53084 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53088 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53111 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53116 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53123 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53145 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53205 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53218 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53257 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53282 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53286 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53305 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53320 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53340 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53363 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53386 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53398 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53427 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53446 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53454 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53484 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53500 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53504 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53506 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53515 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53516 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53522 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53524 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53543 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53560 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53587 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53619 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53626 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53629 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53638 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53676 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53680 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26598 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26689 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35868 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-36921 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-39494 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-40900 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-40903 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-40935 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-40956 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-40974 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-41045 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-41069 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-41087 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42148 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-42285 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42302 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-44932 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-44964 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-44967 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-44974 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-44977 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-44985 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-44986 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-44998 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-45026 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46673 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-46725 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46736 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46738 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-46746 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46759 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-46766 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46786 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46796 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46798 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46800 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-46830 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46859 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46871 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47682 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47696 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-47701 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47718 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47748 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49880 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49882 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-49883 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-49884 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-49889 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-49930 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-49950 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-49960 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-49983 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-49991 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-50007 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-50029 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50055 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-50063 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50067 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50074 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50114 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50126 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50127 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50131 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50143 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-50151 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-50155 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50158 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50209 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50215 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-50235 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50261 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50262 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-50267 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-50274 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50282 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-53057 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-53059 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-53096 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-53103 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53166 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-53168 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-53173 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-53179 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-53239 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-56600 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56604 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56605 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56609 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56615 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-56633 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-56638 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56640 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56642 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56658 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56765 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56772 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57798 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57849 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57951 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-58093 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-58240 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21692 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-21724 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21772 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21856 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21858 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-23133 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-23142 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37798 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37839 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-37861 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-37869 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37882 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37885 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-37891 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37921 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37944 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37957 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38019 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38056 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38077 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38117 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38118 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38146 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38154 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38157 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38198 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38201 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38209 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38212 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38216 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38245 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38248 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38257 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38270 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38280 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38289 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38317 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38323 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38338 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38346 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38369 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38375 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38443 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38488 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-38494 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38512 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38552 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38574 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38584 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38593 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38618 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38676 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-38688 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38729 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39689 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39691 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39790 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39797 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39809 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39810 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39823 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39824 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39854 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39855 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39860 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39861 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39862 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39863 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39877 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39880 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39911 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39939 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39944 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39945 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39967 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40014 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40149 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-71068 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71091 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71100 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71137 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-71157 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71234 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71238 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-22980 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23013 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23025 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23078 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23208 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23223 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23262 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23319 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23343 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23359 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23412 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23413 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23415 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23447 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23448 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31399 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31452 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31455 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31485 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31493 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31500 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31527 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31530 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31583 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31686 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31729 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31731 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31759 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31776 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43049 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43059 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43120 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43150 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43328 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43440 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45837 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45891 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45996 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46004 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46045 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46047 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46069 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46084 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46121 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46162 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46180 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46234 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46294 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53004 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53089 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53109 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53116 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53117 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53118 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53120 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53129 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53156 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53195 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53286 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53294 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53296 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53366 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-46984 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-47014 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47196 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47222 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47261 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47404 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-47483 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47517 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47536 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47576 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47609 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-47613 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47616 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48657 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48658 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48662 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48694 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48702 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48712 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48732 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48801 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49888 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49907 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49917 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49975 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50071 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50252 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50432 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52452 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52455 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52464 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-52468 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-52764 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-52795 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52818 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-52851 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52987 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53082 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53142 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53153 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53179 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53215 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53307 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53492 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53578 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53604 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54207 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54285 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26742 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26883 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-36012 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-36898 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-36906 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-38588 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-38627 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-39480 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-40994 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-41000 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-41003 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-42136 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42138 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46845 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50130 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53214 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-56669 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56708 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-57917 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21869 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37928 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-37981 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38239 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38385 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38535 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38563 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-38565 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39701 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39776 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39835 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39913 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39957 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39958 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39963 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40364 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-71078 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71082 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71099 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71122 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23089 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31696 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45920 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46068 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46136 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52962 | LOW3.98 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-35535 | LOW3.98 | sudo 1.9.17p2-2.el9 fixed in 1.9.17p2-3.el9_8 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-55895 | LOW3.98 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-57456 | LOW3.98 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-39881 | LOW3.98 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-55693 | LOW3.98 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-57455 | LOW3.98 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-59856 | LOW3.98 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-59858 | LOW3.98 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2021-3928 | LOW3.98 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2022-0351 | LOW3.98 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2022-2522 | LOW3.98 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2022-2817 | LOW3.98 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-2819 | LOW3.98 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2022-2845 | LOW3.98 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-2849 | LOW3.98 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-2862 | LOW3.98 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2022-2889 | LOW3.98 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-2946 | LOW3.98 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-2982 | LOW3.98 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2022-3016 | LOW3.98 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-3037 | LOW3.98 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-3099 | LOW3.98 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-3134 | LOW3.98 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-3234 | LOW3.98 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-3235 | LOW3.98 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-3256 | LOW3.98 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-3296 | LOW3.98 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-3297 | LOW3.98 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-3324 | LOW3.98 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-3352 | LOW3.98 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-4141 | LOW3.98 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-4292 | LOW3.98 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-0049 | LOW3.98 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-0051 | LOW3.98 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-0054 | LOW3.98 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-0288 | LOW3.98 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-0433 | LOW3.98 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-0512 | LOW3.98 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-1127 | LOW3.98 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-2610 | LOW3.98 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-4734 | LOW3.98 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-4735 | LOW3.98 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-4738 | LOW3.98 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-4751 | LOW3.98 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-4781 | LOW3.98 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-5535 | LOW3.98 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2024-22667 | LOW3.98 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1215 | LOW3.98 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-0213 | LOW3.96 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2021-3826 | LOW3.9 | binutils 2.35.2-72.el9 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2021-3826 | LOW3.9 | binutils-gold 2.35.2-72.el9 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2024-9681 | LOW3.9 | curl-minimal 7.76.1-41.el9 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2020-26140 | LOW3.9 | kernel-headers 5.14.0-688.el9 No fix yet | 2.9% Low-Moderate Risk | Post-Exploit |
| CVE-2020-26144 | LOW3.9 | kernel-headers 5.14.0-688.el9 No fix yet | 4.9% Low-Moderate Risk | Post-Exploit |
| CVE-2024-47692 | LOW3.9 | kernel-headers 5.14.0-688.el9 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2024-9681 | LOW3.9 | libcurl-minimal 7.76.1-41.el9 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2025-66864 | LOW3.82 | binutils 2.35.2-72.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66866 | LOW3.82 | binutils 2.35.2-72.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69649 | LOW3.82 | binutils 2.35.2-72.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69650 | LOW3.82 | binutils 2.35.2-72.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-66864 | LOW3.82 | binutils-gold 2.35.2-72.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66866 | LOW3.82 | binutils-gold 2.35.2-72.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69649 | LOW3.82 | binutils-gold 2.35.2-72.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69650 | LOW3.82 | binutils-gold 2.35.2-72.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-11352 | LOW3.82 | curl-minimal 7.76.1-41.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-11586 | LOW3.82 | curl-minimal 7.76.1-41.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-5773 | LOW3.82 | curl-minimal 7.76.1-41.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW3.82 | curl-minimal 7.76.1-41.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66864 | LOW3.82 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66866 | LOW3.82 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69649 | LOW3.82 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69650 | LOW3.82 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-40164 | LOW3.82 | jq 1.6-19.el9 fixed in 1.6-19.el9_8.2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-32316 | LOW3.82 | jq 1.6-19.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-50865 | LOW3.82 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50083 | LOW3.82 | kernel-headers 5.14.0-688.el9 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2024-57791 | LOW3.82 | kernel-headers 5.14.0-688.el9 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-39973 | LOW3.82 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-11352 | LOW3.82 | libcurl-minimal 7.76.1-41.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-11586 | LOW3.82 | libcurl-minimal 7.76.1-41.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-5773 | LOW3.82 | libcurl-minimal 7.76.1-41.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW3.82 | libcurl-minimal 7.76.1-41.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-59999 | LOW3.82 | openssh-clients 9.9p1-7.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-60000 | LOW3.82 | openssh-clients 9.9p1-7.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-0994 | LOW3.82 | protobuf-compiler 3.14.0-17.el9 fixed in 3.14.0-17.el9_7 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-15308 | LOW3.82 | python3-devel 3.9.25-5.el9 fixed in 3.9.25-7.el9_8.2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-3644 | LOW3.82 | python3-devel 3.9.25-5.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-4224 | LOW3.82 | python3-devel 3.9.25-5.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-7210 | LOW3.82 | python3-devel 3.9.25-5.el9 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-59871 | LOW3.82 | tar 2:1.34-11.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-26269 | LOW3.82 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11468 | LOW3.82 | python3 3.9.25-5.el9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-0865 | LOW3.82 | python3 3.9.25-5.el9 fixed in 3.9.25-5.el9_8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-1502 | LOW3.82 | python3 3.9.25-5.el9 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-11468 | LOW3.82 | python3-libs 3.9.25-5.el9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-0865 | LOW3.82 | python3-libs 3.9.25-5.el9 fixed in 3.9.25-5.el9_8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-1502 | LOW3.82 | python3-libs 3.9.25-5.el9 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-9547 | LOW3.77 | curl-minimal 7.76.1-41.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-9547 | LOW3.77 | libcurl-minimal 7.76.1-41.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-34182 | LOW3.77 | openssl 1:3.5.5-1.el9 fixed in 1:3.5.5-4.el9_8 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2020-25678 | LOW3.74 | librados2 2:20.2.1-0.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2020-25678 | LOW3.74 | librbd1 2:20.2.1-0.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-29040 | LOW3.74 | tpm2-tss 3.2.3-1.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-22870 | LOW3.74 | stdlib v1.22.10 fixed in 1.23.7, 1.24.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-53705 | LOW3.72 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-43078 | LOW3.72 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43248 | LOW3.72 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-48748 | LOW3.66 | kernel-headers 5.14.0-688.el9 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2025-9640 | LOW3.65 | libldb 4.23.5-6.el9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-9640 | LOW3.65 | libwbclient 4.23.5-6.el9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-9640 | LOW3.65 | samba-client-libs 4.23.5-6.el9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-9640 | LOW3.65 | samba-common 4.23.5-6.el9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-9640 | LOW3.65 | samba-common-libs 4.23.5-6.el9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-4156 | LOW3.62 | gawk 5.1.0-6.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-46033 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2021-47097 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-48866 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49094 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49395 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49407 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49444 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49503 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49518 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49556 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49687 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49696 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49740 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49799 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49844 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49865 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49870 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49883 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49948 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50103 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50200 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50231 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50239 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50255 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50279 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50307 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50366 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50394 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50490 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50551 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-1838 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-53024 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53085 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53090 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53112 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53213 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53232 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53254 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53259 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53272 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53333 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53376 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53392 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53521 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53575 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53600 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53659 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53668 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53675 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-0775 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-36013 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2024-38606 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-39487 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42094 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-44983 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-46722 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-46723 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-46724 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46743 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-49860 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-49928 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50033 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-50035 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-50042 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50128 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50164 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50250 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50268 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-50278 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-50279 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-50301 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-53082 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53099 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53147 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53174 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56558 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-58013 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21762 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-21973 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37761 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37846 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37973 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38004 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38103 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38111 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38249 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38320 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38342 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38445 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38616 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38680 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39683 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39750 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39853 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39891 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39901 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39922 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68357 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-71093 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71112 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71231 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23076 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23099 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23102 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23187 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23315 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23318 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23327 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23363 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23388 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23397 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31395 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31430 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31568 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31614 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31778 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43040 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43052 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43281 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43427 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43449 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43450 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43453 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46094 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46120 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46130 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46191 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52968 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53255 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2021-47089 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47191 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47226 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48714 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48757 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48760 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50497 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52519 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52598 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52794 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52842 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52866 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53265 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53357 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-14040 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46774 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57838 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21719 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38502 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38521 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38636 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38728 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71133 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23244 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45851 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-46140 | LOW3.62 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-4786 | LOW3.62 | python3-devel 3.9.25-5.el9 fixed in 3.9.25-7.el9_8 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-6965 | LOW3.61 | sqlite-libs 3.34.1-9.el9 fixed in 3.34.1-9.el9_7 | 74.4% Actively Exploited | Post-Exploit |
| CVE-2005-2541 | LOW3.6 | tar 2:1.34-11.el9 No fix yet | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2025-68973 | LOW3.57 | gnupg2 2.3.3-5.el9 fixed in 2.3.3-5.el9_7 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40186 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-54518 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-31663 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45972 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-46099 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-46309 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52951 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52973 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52991 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52993 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-53000 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53002 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-53091 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53145 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53202 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53203 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53360 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53398 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-53399 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-63824 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-63829 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-63830 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-63875 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63886 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-63887 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-63888 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-63899 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63917 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63922 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-63924 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-63939 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63952 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63956 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63962 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63970 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63993 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-63994 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-64009 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64017 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64018 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64026 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64030 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64037 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-64113 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-64191 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64276 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64277 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64296 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64378 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64490 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-4202 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-1247 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-48858 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48988 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49667 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-50082 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-1077 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-52974 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-52983 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-38561 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42162 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42228 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-43882 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49855 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50036 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50106 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50275 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57876 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21761 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38051 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38102 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38107 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38108 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40199 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40216 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40259 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40328 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23050 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23454 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31539 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-31586 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43050 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43233 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-43304 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-43332 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43334 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-43339 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43493 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-45856 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45859 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-45861 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45894 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45910 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45942 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45959 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45970 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46015 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46043 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-46052 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-46076 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46114 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-46119 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-46133 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-46149 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46174 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46185 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-46266 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-46275 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-46306 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-46317 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46319 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46324 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46325 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-46330 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52912 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52917 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52918 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-52920 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-52924 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-52933 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52935 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52942 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52945 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-52947 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52953 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52956 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-52957 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-52971 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52986 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-52998 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-53005 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53009 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53011 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53031 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53036 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53049 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-53053 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53062 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53072 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53075 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-53078 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53110 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53131 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-53182 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53185 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53189 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53192 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53193 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53209 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53212 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53223 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53224 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-53228 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-53230 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53239 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53242 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53246 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-53250 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53253 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-53254 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-53256 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53264 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53268 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-53270 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53275 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53290 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53341 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53354 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53357 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-53384 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-53388 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53391 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-53392 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-53393 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53397 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-63794 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63800 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-63801 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-63802 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-63807 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-63808 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-63809 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63823 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-63826 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63885 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63898 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63901 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63910 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63913 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-63914 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63920 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63925 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-63928 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63941 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63945 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63947 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-63975 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-63978 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-63992 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-63996 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64000 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-64002 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64011 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64015 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64025 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-64029 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64035 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-64047 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-64048 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-64053 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64054 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64071 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64098 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64102 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-64109 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64111 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64114 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64115 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64117 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64136 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-64160 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-64174 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64189 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64192 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64321 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64342 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64354 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64384 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-64456 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64515 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64530 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-48689 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53622 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23054 | LOW3.57 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-51767 | LOW3.57 | openssh-clients 9.9p1-7.el9 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-44604 | LOW3.57 | rpm 4.16.1.3-40.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-46483 | LOW3.57 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-1484 | LOW3.57 | glib2 2.68.4-19.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-45341 | LOW3.57 | stdlib v1.22.10 fixed in 1.22.11, 1.23.5, 1.24.0-rc.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-1153 | LOW3.54 | binutils 2.35.2-72.el9 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1153 | LOW3.54 | binutils-gold 2.35.2-72.el9 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2024-11053 | LOW3.54 | curl-minimal 7.76.1-41.el9 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1153 | LOW3.54 | gdb-gdbserver 16.3-3.el9 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2021-3714 | LOW3.54 | kernel-headers 5.14.0-688.el9 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2024-11053 | LOW3.54 | libcurl-minimal 7.76.1-41.el9 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2026-31790 | LOW3.54 | openssl 1:3.5.5-1.el9 fixed in 1:3.5.5-2.el9_8 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-42764 | LOW3.54 | openssl 1:3.5.5-1.el9 fixed in 1:3.5.5-4.el9_8 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2024-41996 | LOW3.54 | openssl 1:3.5.5-1.el9 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-42010 | LOW3.53 | gnutls 3.8.10-3.el9 fixed in 3.8.10-4.el9_8 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-4408 | LOW3.53 | libldb 4.23.5-6.el9 fixed in 4.23.5-10.el9_8 | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-4800 | LOW3.53 | librados2 2:20.2.1-0.el9 No fix yet | 2.6% Low-Moderate Risk | Post-Exploit |
| CVE-2026-4800 | LOW3.53 | librbd1 2:20.2.1-0.el9 No fix yet | 2.6% Low-Moderate Risk | Post-Exploit |
| CVE-2026-4408 | LOW3.53 | libwbclient 4.23.5-6.el9 fixed in 4.23.5-10.el9_8 | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2023-29824 | LOW3.53 | python3-scipy 1.9.3-2.el9 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-4408 | LOW3.53 | samba-client-libs 4.23.5-6.el9 fixed in 4.23.5-10.el9_8 | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-4408 | LOW3.53 | samba-common 4.23.5-6.el9 fixed in 4.23.5-10.el9_8 | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-4408 | LOW3.53 | samba-common-libs 4.23.5-6.el9 fixed in 4.23.5-10.el9_8 | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2025-13034 | LOW3.47 | curl-minimal 7.76.1-41.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-1965 | LOW3.47 | curl-minimal 7.76.1-41.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-33656 | LOW3.47 | kernel-headers 5.14.0-688.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-40345 | LOW3.47 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53196 | LOW3.47 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-13034 | LOW3.47 | libcurl-minimal 7.76.1-41.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-1965 | LOW3.47 | libcurl-minimal 7.76.1-41.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-42739 | LOW3.42 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2021-43975 | LOW3.42 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-20153 | LOW3.42 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-49388 | LOW3.42 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-50616 | LOW3.42 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52975 | LOW3.42 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-54102 | LOW3.42 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54110 | LOW3.42 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53095 | LOW3.42 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53177 | LOW3.42 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56678 | LOW3.42 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56693 | LOW3.42 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57795 | LOW3.42 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21731 | LOW3.42 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40257 | LOW3.42 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53094 | LOW3.42 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52447 | LOW3.42 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26828 | LOW3.42 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2021-3572 | LOW3.42 | python3-pip-wheel 21.3.1-1.el9 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2024-25260 | LOW3.4 | elfutils-libelf 0.194-1.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-25260 | LOW3.4 | elfutils-libs 0.194-1.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | glibc 2.34-262.el9 fixed in 2.34-270.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | glibc-common 2.34-262.el9 fixed in 2.34-270.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | glibc-gconv-extra 2.34-262.el9 fixed in 2.34-270.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-49839 | LOW3.37 | jq 1.6-19.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50851 | LOW3.37 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-5197 | LOW3.37 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-53729 | LOW3.37 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54168 | LOW3.37 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54300 | LOW3.37 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-0607 | LOW3.37 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40018 | LOW3.37 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40261 | LOW3.37 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-31589 | LOW3.37 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-45991 | LOW3.37 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53267 | LOW3.37 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-28419 | LOW3.37 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-1170 | LOW3.37 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-1175 | LOW3.37 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-1972 | LOW3.31 | binutils 2.35.2-72.el9 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2023-1972 | LOW3.31 | binutils-gold 2.35.2-72.el9 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-11856 | LOW3.31 | curl-minimal 7.76.1-41.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-3784 | LOW3.31 | curl-minimal 7.76.1-41.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW3.31 | curl-minimal 7.76.1-41.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW3.31 | curl-minimal 7.76.1-41.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | curl-minimal 7.76.1-41.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-14524 | LOW3.31 | curl-minimal 7.76.1-41.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-4437 | LOW3.31 | glibc-devel 2.34-262.el9 fixed in 2.34-270.el9_8 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6238 | LOW3.31 | glibc-devel 2.34-262.el9 fixed in 2.34-274.el9_8 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-4437 | LOW3.31 | glibc-headers 2.34-262.el9 fixed in 2.34-270.el9_8 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6238 | LOW3.31 | glibc-headers 2.34-262.el9 fixed in 2.34-274.el9_8 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-39979 | LOW3.31 | jq 1.6-19.el9 fixed in 1.6-19.el9_8.2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-68284 | LOW3.31 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-28711 | LOW3.31 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-28712 | LOW3.31 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-28713 | LOW3.31 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-50821 | LOW3.31 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53785 | LOW3.31 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54094 | LOW3.31 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47693 | LOW3.31 | kernel-headers 5.14.0-688.el9 No fix yet | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2024-50076 | LOW3.31 | kernel-headers 5.14.0-688.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-39969 | LOW3.31 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40061 | LOW3.31 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40273 | LOW3.31 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40336 | LOW3.31 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68354 | LOW3.31 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68380 | LOW3.31 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23179 | LOW3.31 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-31470 | LOW3.31 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31588 | LOW3.31 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43239 | LOW3.31 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-43447 | LOW3.31 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53176 | LOW3.31 | kernel-headers 5.14.0-688.el9 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-64535 | LOW3.31 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-0564 | LOW3.31 | kernel-headers 5.14.0-688.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-11856 | LOW3.31 | libcurl-minimal 7.76.1-41.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-3784 | LOW3.31 | libcurl-minimal 7.76.1-41.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW3.31 | libcurl-minimal 7.76.1-41.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW3.31 | libcurl-minimal 7.76.1-41.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | libcurl-minimal 7.76.1-41.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-14524 | LOW3.31 | libcurl-minimal 7.76.1-41.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-55653 | LOW3.31 | openssh-clients 9.9p1-7.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-59998 | LOW3.31 | openssh-clients 9.9p1-7.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-60001 | LOW3.31 | openssh-clients 9.9p1-7.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-35387 | LOW3.31 | openssh-clients 9.9p1-7.el9 fixed in 9.9p1-7.el9_8 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-2673 | LOW3.31 | openssl 1:3.5.5-1.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-11972 | LOW3.31 | python3-devel 3.9.25-5.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-33056 | LOW3.31 | tar 2:1.34-11.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-15028 | LOW3.31 | libarchive 3.5.3-8.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52832 | LOW3.3 | kernel-headers 5.14.0-688.el9 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2024-38612 | LOW3.3 | kernel-headers 5.14.0-688.el9 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2025-21760 | LOW3.3 | kernel-headers 5.14.0-688.el9 No fix yet | 9.5% Low-Moderate Risk | Post-Exploit |
| CVE-2025-39946 | LOW3.3 | kernel-headers 5.14.0-688.el9 No fix yet | 8.9% Low-Moderate Risk | Post-Exploit |
| CVE-2021-47241 | LOW3.3 | kernel-headers 5.14.0-688.el9 No fix yet | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2024-38573 | LOW3.3 | kernel-headers 5.14.0-688.el9 No fix yet | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-44605 | LOW3.3 | rpm 4.16.1.3-40.el9 No fix yet | — | Post-Exploit |
| CVE-2022-0529 | LOW3.3 | unzip 6.0-59.el9 No fix yet | 2.4% Low-Moderate Risk | Post-Exploit |
| CVE-2022-0530 | LOW3.3 | unzip 6.0-59.el9 No fix yet | 2.1% Low-Moderate Risk | Post-Exploit |
| CVE-2022-1674 | LOW3.3 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2208 | LOW3.3 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2017-6519 | LOW3.28 | avahi-libs 0.8-24.el9 No fix yet | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2024-47685 | LOW3.28 | kernel-headers 5.14.0-688.el9 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2021-37159 | LOW3.26 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2021-47634 | LOW3.26 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-20154 | LOW3.26 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-49493 | LOW3.26 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49694 | LOW3.26 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50880 | LOW3.26 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54164 | LOW3.26 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54200 | LOW3.26 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-21823 | LOW3.26 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57979 | LOW3.26 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-21700 | LOW3.26 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39978 | LOW3.26 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40074 | LOW3.26 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40091 | LOW3.26 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40309 | LOW3.26 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40321 | LOW3.26 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40350 | LOW3.26 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68371 | LOW3.26 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23178 | LOW3.26 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23383 | LOW3.26 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23450 | LOW3.26 | kernel-headers 5.14.0-688.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-23456 | LOW3.26 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-31502 | LOW3.26 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31516 | LOW3.26 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31525 | LOW3.26 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43070 | LOW3.26 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45932 | LOW3.26 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52910 | LOW3.26 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53033 | LOW3.26 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53081 | LOW3.26 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53085 | LOW3.26 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53090 | LOW3.26 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53092 | LOW3.26 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52886 | LOW3.26 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-32728 | LOW3.23 | openssh 9.9p1-7.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-32728 | LOW3.23 | openssh-server 9.9p1-7.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-20197 | LOW3.21 | binutils 2.35.2-72.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-20197 | LOW3.21 | binutils-gold 2.35.2-72.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-50701 | LOW3.21 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42161 | LOW3.21 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40000 | LOW3.21 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40302 | LOW3.21 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40307 | LOW3.21 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40320 | LOW3.21 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68282 | LOW3.21 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-31504 | LOW3.21 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31631 | LOW3.21 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-41012 | LOW3.21 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-34181 | LOW3.21 | openssl 1:3.5.5-1.el9 fixed in 1:3.5.5-4.el9_8 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-42768 | LOW3.21 | openssl 1:3.5.5-1.el9 fixed in 1:3.5.5-4.el9_8 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-5958 | LOW3.21 | sed 4.8-10.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2020-26146 | LOW3.18 | kernel-headers 5.14.0-688.el9 No fix yet | 5.6% Low-Moderate Risk | Post-Exploit |
| CVE-2021-33430 | LOW3.18 | python3-numpy-f2py 1:1.23.5-2.el9 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2021-34141 | LOW3.18 | python3-numpy-f2py 1:1.23.5-2.el9 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2022-1271 | LOW3.17 | xz-libs 5.2.5-8.el9 fixed in 5.2.5-8.el9_0 | 4.3% Low-Moderate Risk | Post-Exploit |
| CVE-2024-6345 | LOW3.17 | setuptools 69.2.0 fixed in 70.0.0 | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2025-47273 | LOW3.17 | setuptools 69.2.0 fixed in 78.1.1 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2022-50764 | LOW3.16 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50817 | LOW3.16 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50829 | LOW3.16 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50838 | LOW3.16 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50873 | LOW3.16 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54039 | LOW3.16 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54081 | LOW3.16 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54311 | LOW3.16 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50251 | LOW3.16 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-40048 | LOW3.16 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40132 | LOW3.16 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40146 | LOW3.16 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40147 | LOW3.16 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-41080 | LOW3.15 | expat 2.5.0-6.el9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-3360 | LOW3.15 | glib2 2.68.4-19.el9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-7039 | LOW3.15 | glib2 2.68.4-19.el9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0988 | LOW3.15 | glib2 2.68.4-19.el9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3832 | LOW3.15 | gnutls 3.8.10-3.el9 fixed in 3.8.10-4.el9_8 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-5419 | LOW3.15 | gnutls 3.8.10-3.el9 fixed in 3.8.10-4.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0989 | LOW3.15 | libxml2 2.9.13-14.el9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-55654 | LOW3.15 | openssh 9.9p1-7.el9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-55654 | LOW3.15 | openssh-server 9.9p1-7.el9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-45446 | LOW3.15 | openssl-libs 1:3.5.5-1.el9 fixed in 1:3.5.5-4.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-56391 | LOW3.11 | coreutils-single 8.32-40.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-39956 | LOW3.11 | jq 1.6-19.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53788 | LOW3.11 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53802 | LOW3.11 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53808 | LOW3.11 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53840 | LOW3.11 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53850 | LOW3.11 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42224 | LOW3.11 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40019 | LOW3.11 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-40038 | LOW3.11 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40071 | LOW3.11 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40080 | LOW3.11 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40190 | LOW3.11 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40355 | LOW3.11 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68245 | LOW3.11 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68342 | LOW3.11 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68343 | LOW3.11 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68736 | LOW3.11 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68764 | LOW3.11 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68770 | LOW3.11 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68815 | LOW3.11 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-31449 | LOW3.11 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31464 | LOW3.11 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-31505 | LOW3.11 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31511 | LOW3.11 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31513 | LOW3.11 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-31570 | LOW3.11 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-31700 | LOW3.11 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31708 | LOW3.11 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-43134 | LOW3.11 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-43321 | LOW3.11 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2021-47313 | LOW3.11 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-57874 | LOW3.11 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57878 | LOW3.11 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-55655 | LOW3.11 | openssh-clients 9.9p1-7.el9 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6019 | LOW3.11 | python3-devel 3.9.25-5.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-50181 | LOW3.11 | python3-pip-wheel 21.3.1-1.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-50182 | LOW3.11 | python3-pip-wheel 21.3.1-1.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-57451 | LOW3.11 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-59890 | LOW3.11 | setuptools 69.2.0 fixed in 83.0.0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-9232 | LOW3.1 | openssl-libs 1:3.5.5-1.el9 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2021-47308 | LOW3.06 | kernel-headers 5.14.0-688.el9 No fix yet | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2022-49053 | LOW3.06 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49385 | LOW3.06 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-50621 | LOW3.06 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40359 | LOW3.06 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-31649 | LOW3.06 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-52481 | LOW3.06 | kernel-headers 5.14.0-688.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-5713 | LOW3.06 | python3-devel 3.9.25-5.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-5435 | LOW3.01 | glibc-devel 2.34-262.el9 fixed in 2.34-274.el9_8 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-5435 | LOW3.01 | glibc-headers 2.34-262.el9 fixed in 2.34-274.el9_8 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50666 | LOW3.01 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50756 | LOW3.01 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50849 | LOW3.01 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53764 | LOW3.01 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54269 | LOW3.01 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-2312 | LOW3.01 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40083 | LOW3.01 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40242 | LOW3.01 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40324 | LOW3.01 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-42769 | LOW3.01 | openssl 1:3.5.5-1.el9 fixed in 1:3.5.5-4.el9_8 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42770 | LOW3.01 | openssl 1:3.5.5-1.el9 fixed in 1:3.5.5-4.el9_8 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-9076 | LOW3.01 | openssl 1:3.5.5-1.el9 fixed in 1:3.5.5-4.el9_8 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-32284 | LOW3.01 | python3-pip-wheel 21.3.1-1.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-14087 | LOW3 | glib2 2.68.4-19.el9 fixed in 2.68.4-19.el9_8.1 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-23112 | LOW3 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-31789 | LOW3 | openssl 1:3.5.5-1.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-31789 | LOW3 | openssl-libs 1:3.5.5-1.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-34180 | LOW3 | openssl 1:3.5.5-1.el9 fixed in 1:3.5.5-4.el9_8 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2022-49479 | LOW2.96 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-50636 | LOW2.96 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50710 | LOW2.96 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53717 | LOW2.96 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53789 | LOW2.96 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54045 | LOW2.96 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54107 | LOW2.96 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54176 | LOW2.96 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54236 | LOW2.96 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54258 | LOW2.96 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54262 | LOW2.96 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54276 | LOW2.96 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39998 | LOW2.96 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40111 | LOW2.96 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40167 | LOW2.96 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40194 | LOW2.96 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40201 | LOW2.96 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40237 | LOW2.96 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40272 | LOW2.96 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40323 | LOW2.96 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40329 | LOW2.96 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40340 | LOW2.96 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68742 | LOW2.96 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23239 | LOW2.96 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23240 | LOW2.96 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-23271 | LOW2.96 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23317 | LOW2.96 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31392 | LOW2.96 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31414 | LOW2.96 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-31426 | LOW2.96 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46065 | LOW2.96 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52908 | LOW2.96 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52923 | LOW2.96 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-1380 | LOW2.94 | kernel-headers 5.14.0-688.el9 No fix yet | 16.6% High Exploitation Risk | Post-Exploit |
| CVE-2026-45447 | LOW2.92 | openssl 1:3.5.5-1.el9 fixed in 1:3.5.5-4.el9_8 | 5.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-3783 | LOW2.91 | curl-minimal 7.76.1-41.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49138 | LOW2.91 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-50651 | LOW2.91 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54015 | LOW2.91 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54275 | LOW2.91 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53240 | LOW2.91 | kernel-headers 5.14.0-688.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-40319 | LOW2.91 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-46024 | LOW2.91 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-3783 | LOW2.91 | libcurl-minimal 7.76.1-41.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-3968 | LOW2.88 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 2.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-60002 | LOW2.87 | openssh-clients 9.9p1-7.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-15003 | LOW2.86 | binutils 2.35.2-72.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-15003 | LOW2.86 | binutils-gold 2.35.2-72.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-15003 | LOW2.86 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53828 | LOW2.86 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54193 | LOW2.86 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68801 | LOW2.86 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68816 | LOW2.86 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48754 | LOW2.86 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11081 | LOW2.8 | binutils 2.35.2-72.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6844 | LOW2.8 | binutils 2.35.2-72.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-38533 | LOW2.8 | binutils 2.35.2-72.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-47007 | LOW2.8 | binutils 2.35.2-72.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-47008 | LOW2.8 | binutils 2.35.2-72.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-47010 | LOW2.8 | binutils 2.35.2-72.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-47011 | LOW2.8 | binutils 2.35.2-72.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-11412 | LOW2.8 | binutils 2.35.2-72.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11413 | LOW2.8 | binutils 2.35.2-72.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11414 | LOW2.8 | binutils 2.35.2-72.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11494 | LOW2.8 | binutils 2.35.2-72.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11495 | LOW2.8 | binutils 2.35.2-72.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11839 | LOW2.8 | binutils 2.35.2-72.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11840 | LOW2.8 | binutils 2.35.2-72.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-3198 | LOW2.8 | binutils 2.35.2-72.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | binutils 2.35.2-72.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11081 | LOW2.8 | binutils-gold 2.35.2-72.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6844 | LOW2.8 | binutils-gold 2.35.2-72.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-38533 | LOW2.8 | binutils-gold 2.35.2-72.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-47007 | LOW2.8 | binutils-gold 2.35.2-72.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-47008 | LOW2.8 | binutils-gold 2.35.2-72.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-47010 | LOW2.8 | binutils-gold 2.35.2-72.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-47011 | LOW2.8 | binutils-gold 2.35.2-72.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-11412 | LOW2.8 | binutils-gold 2.35.2-72.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11413 | LOW2.8 | binutils-gold 2.35.2-72.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11414 | LOW2.8 | binutils-gold 2.35.2-72.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11494 | LOW2.8 | binutils-gold 2.35.2-72.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11495 | LOW2.8 | binutils-gold 2.35.2-72.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11839 | LOW2.8 | binutils-gold 2.35.2-72.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11840 | LOW2.8 | binutils-gold 2.35.2-72.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-3198 | LOW2.8 | binutils-gold 2.35.2-72.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | binutils-gold 2.35.2-72.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-46195 | LOW2.8 | cpp 11.5.0-14.el9 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW2.8 | cpp 11.5.0-14.el9 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2025-1371 | LOW2.8 | elfutils-debuginfod-client 0.194-1.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1377 | LOW2.8 | elfutils-debuginfod-client 0.194-1.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-46195 | LOW2.8 | gcc 11.5.0-14.el9 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW2.8 | gcc 11.5.0-14.el9 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2025-11081 | LOW2.8 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6844 | LOW2.8 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-47007 | LOW2.8 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-47010 | LOW2.8 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-47011 | LOW2.8 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-11412 | LOW2.8 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11413 | LOW2.8 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11414 | LOW2.8 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11494 | LOW2.8 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11495 | LOW2.8 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11839 | LOW2.8 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11840 | LOW2.8 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-3198 | LOW2.8 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-24883 | LOW2.8 | gnupg2 2.3.3-5.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-33947 | LOW2.8 | jq 1.6-19.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-40612 | LOW2.8 | jq 1.6-19.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-41256 | LOW2.8 | jq 1.6-19.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-41257 | LOW2.8 | jq 1.6-19.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43894 | LOW2.8 | jq 1.6-19.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-43896 | LOW2.8 | jq 1.6-19.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-44777 | LOW2.8 | jq 1.6-19.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-47770 | LOW2.8 | jq 1.6-19.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-54679 | LOW2.8 | jq 1.6-19.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-9403 | LOW2.8 | jq 1.6-19.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38001 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-38509 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40348 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68182 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68192 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68215 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68291 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68297 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68307 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-52972 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2020-13844 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2021-34693 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2021-4135 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-46931 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47041 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47092 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-47214 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47223 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47227 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47230 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47275 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47316 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47343 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-47365 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47444 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47465 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47515 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47559 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47620 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47632 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47648 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47650 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47659 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-0171 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-26878 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-26966 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-2785 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-4543 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2022-48638 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48644 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48652 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48696 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48719 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-48773 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-48780 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48781 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48785 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48793 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48797 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48799 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48802 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-48810 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48811 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-48819 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48831 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-48832 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48835 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48836 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48839 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-48840 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48844 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48849 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48850 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48853 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-48861 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48862 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48863 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48864 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48865 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-48875 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48876 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48879 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48886 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48889 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48914 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48915 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48938 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48946 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-48953 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48961 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48969 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-48971 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48972 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-48975 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48982 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48983 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-48984 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48986 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48987 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48994 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49011 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49012 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49013 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49021 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49028 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49048 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49052 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49061 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49074 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49076 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49077 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49082 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49092 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49096 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49100 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49110 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49118 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49132 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49134 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49148 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49154 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49159 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49171 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49174 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49176 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49182 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49187 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49190 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49198 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49208 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49216 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49219 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49220 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49231 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49237 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49256 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49262 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49266 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49273 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49279 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49296 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49307 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49314 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49316 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49321 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49339 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49341 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49370 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49390 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49400 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49403 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49406 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49419 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49420 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49441 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49446 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49450 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49456 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49468 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49472 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49474 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49475 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49481 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49486 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49497 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49521 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49523 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49526 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49535 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49542 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49567 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49611 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49613 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49616 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49617 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49620 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49624 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49656 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49658 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49662 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49679 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49699 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49715 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49716 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49728 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49743 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49748 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49750 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-49759 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-49764 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49773 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-49774 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-49776 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49780 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49783 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-49786 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-49791 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-49795 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-49797 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49801 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49802 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49803 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49810 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-49812 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49819 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-49821 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49822 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49823 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49824 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49825 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49827 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49829 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-49832 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49836 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49837 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49838 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49839 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49847 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-49855 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49858 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-49863 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49864 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49866 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49867 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49871 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49873 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49875 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49876 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-49877 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49878 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49879 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49881 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49885 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49893 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-49894 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-49895 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-49901 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-49905 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49918 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49928 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49929 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-49931 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49932 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49963 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49972 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49987 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49989 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50004 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50008 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50043 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50059 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50060 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50065 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50091 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50098 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50118 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50127 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50130 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50144 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50167 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50174 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50186 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50222 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50233 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50246 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50266 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50267 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50272 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50280 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50282 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50295 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50297 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50314 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50321 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50323 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50327 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50334 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50341 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50356 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50361 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50369 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50370 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50375 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50380 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50382 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50390 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50409 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50414 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50426 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50428 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50430 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50435 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50438 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50440 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50461 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50464 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50475 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50476 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50493 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50494 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50498 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50540 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50553 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50582 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50627 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50709 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50731 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50740 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50746 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50772 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50822 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50832 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50871 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50885 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-2162 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-28327 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-3006 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-31082 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-31085 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-4459 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-45862 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-5090 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52450 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-52486 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52487 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-52518 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52582 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52583 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52619 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52646 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52702 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-52739 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-52787 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52803 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52869 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52901 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52908 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52910 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52912 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52920 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52931 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52977 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-52991 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52992 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52997 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53006 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53008 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53010 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53026 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53032 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53036 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53038 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53041 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53042 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53044 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53050 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53051 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53056 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53058 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53060 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53062 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53070 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53071 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53073 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53078 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53079 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53080 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53086 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53087 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53089 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53095 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53096 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53100 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53101 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53102 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53103 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53105 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53108 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53109 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53110 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53113 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53114 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53118 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53120 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53121 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53124 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53126 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53132 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53133 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53144 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53147 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53168 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53171 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53185 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53189 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53198 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53199 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53200 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53201 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53224 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53225 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53226 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53229 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53240 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53241 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53251 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53277 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53292 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53295 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53296 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53299 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53302 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53315 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53326 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53327 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53347 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53360 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53366 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53382 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53430 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53433 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53437 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53438 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53450 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53453 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53457 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53461 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53463 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53464 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53466 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53475 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53477 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53480 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53481 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53488 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53491 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53499 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53509 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53512 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53514 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53517 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53526 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53528 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53529 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53532 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53535 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53540 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53549 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53561 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53566 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53567 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53574 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53576 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53582 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53589 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53591 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53598 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53601 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53609 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53620 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53624 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53625 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53627 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53635 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53639 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53641 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53643 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53667 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53669 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53678 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53679 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53682 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53684 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53698 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53721 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53753 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53756 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53780 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53783 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53800 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53803 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53822 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53987 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54004 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54012 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54013 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54036 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54037 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54040 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54053 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54055 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54085 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54129 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54131 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54150 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54191 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54238 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54259 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54265 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54273 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54280 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54317 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-7324 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-0443 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-1151 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-26637 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26666 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26682 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26683 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26708 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26771 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26772 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-26779 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26785 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26816 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-26851 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26889 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-26902 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26918 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26991 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26999 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-27031 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-27039 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-27056 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-27077 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-27413 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35803 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35878 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2024-35933 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35978 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-35980 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35999 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-36011 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-36021 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-36286 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-36884 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-36966 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-36970 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36975 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-38598 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-39490 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-39493 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-40937 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-40965 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-40977 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-40980 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-40990 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-41023 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-41031 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-41035 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-41037 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-41060 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-41064 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-41097 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42069 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42070 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-42076 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42083 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42106 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-42135 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42139 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42145 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42232 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42238 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42239 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42240 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42241 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42259 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-42278 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42281 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42286 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42288 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42289 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42290 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42316 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42317 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-43816 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-43821 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-43829 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-43834 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-43835 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-43853 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-43861 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-43871 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-43874 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-43880 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-43889 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-43896 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-43906 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-43908 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-43912 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-43914 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-44931 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-44935 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-44944 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-44957 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-44958 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-44960 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-44961 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-44965 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-44984 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-44989 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-44990 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-44994 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-44996 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-45000 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-45001 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-45006 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-45008 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-45009 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-45010 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-45013 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-45025 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46678 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46715 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46717 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46719 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46737 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-46739 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-46748 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46750 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46755 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-46760 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46761 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-46762 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46767 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46770 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46771 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-46777 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46783 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46791 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46793 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46805 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-46807 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46819 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46822 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46826 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46834 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46835 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46842 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46855 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46857 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46863 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47408 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47673 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47678 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47684 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-47687 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47700 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47703 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47705 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47706 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47707 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47710 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47713 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-47737 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-47739 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47749 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-48873 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-48876 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49568 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49571 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49851 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49856 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49870 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49878 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-49881 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-49886 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49888 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49891 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49925 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-49927 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49929 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49935 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49937 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49938 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-49939 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49940 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49944 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-49948 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-49951 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49952 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-49953 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-49954 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49955 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-49959 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-49962 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-49968 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49971 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49973 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-49974 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-49975 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-49976 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49978 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49994 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50000 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50002 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50008 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50009 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50012 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50014 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50020 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50021 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50024 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-50027 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50028 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50039 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50040 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-50041 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50045 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-50048 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50058 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50075 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50077 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50078 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50081 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50095 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-50109 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50117 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50136 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50139 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50141 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50145 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50146 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50147 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50153 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-50157 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50160 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50162 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50165 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50167 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-50169 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50172 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50179 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50182 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50185 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50189 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50191 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50197 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50207 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50208 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50223 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50236 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-50237 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-50255 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50256 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50258 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50259 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50271 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50272 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50299 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-50303 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50304 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53042 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-53044 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53045 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53048 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53050 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53055 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-53060 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-53066 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-53070 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53073 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53074 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53079 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53091 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53093 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53109 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53110 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53114 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53117 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53118 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53121 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53123 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53134 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53138 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53140 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53144 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-53146 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53167 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-53185 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53194 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53195 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53196 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53207 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53209 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53219 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53236 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-54460 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-54683 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-55642 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56369 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56535 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-56569 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56589 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56636 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-56647 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56648 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56654 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56667 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56677 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-56679 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56688 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56690 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56703 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56716 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56718 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56725 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56726 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56727 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56751 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56757 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56760 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56763 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56770 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-56779 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56783 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57793 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57875 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57882 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57890 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57924 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57932 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57938 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57946 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57948 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57977 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57985 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57996 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-58017 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-58053 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-58061 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-58071 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-58092 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-58096 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-58097 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-58098 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-58100 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-58237 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-58238 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-58241 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21649 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21653 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21659 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21664 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21670 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21673 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21681 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21682 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21683 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21706 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21707 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21709 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21725 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21763 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21767 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21768 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21808 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21809 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21814 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21816 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21817 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21836 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21838 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21852 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21854 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21857 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21862 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21870 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21874 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21885 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21891 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21899 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21900 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21908 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21913 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21936 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21939 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21948 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21951 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21959 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21971 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21974 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21975 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21980 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-22005 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-22013 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-22015 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-22016 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-22017 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-22021 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-22024 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-22025 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-22044 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-22053 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22057 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-22062 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-22063 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-22065 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-22075 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-22077 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22090 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-22106 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-22108 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-22124 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-22125 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-23131 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-23132 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-23134 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-23136 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-23137 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-23138 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-23141 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-23143 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-23145 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-23161 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-23163 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37745 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37747 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37757 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37773 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37791 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37800 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37807 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37808 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37809 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37811 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37813 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37820 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37824 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37829 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37830 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37834 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37836 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-37842 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37843 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37844 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37848 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37857 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-37859 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-37860 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37862 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-37873 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37875 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37876 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37877 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37878 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37883 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37884 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37888 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37889 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37912 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37918 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37919 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37922 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37933 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37940 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37948 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37949 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37954 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37959 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37960 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37961 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37963 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37967 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37974 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37978 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37986 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37989 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37990 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37992 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37995 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37997 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37998 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38003 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38014 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38017 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38018 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38023 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38029 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38031 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38035 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38036 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38038 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38040 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38044 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38047 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38055 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38057 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38058 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38060 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38061 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38062 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38063 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38064 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38066 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38067 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-38071 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38072 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38095 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38099 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38100 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38105 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38113 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38115 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38120 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38122 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38125 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38126 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38128 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38134 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38140 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38147 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38149 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38161 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38162 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38169 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38177 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38181 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38184 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38186 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38190 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38192 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38197 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38199 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38208 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38210 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38214 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38215 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38222 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38231 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38238 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38244 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38246 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38251 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38253 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38255 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38258 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38265 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38282 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38284 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38285 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38287 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38290 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38291 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38293 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38294 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38302 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38303 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38304 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38305 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38307 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38310 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38311 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38312 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38315 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38318 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38321 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38324 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38334 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38335 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38337 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38344 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38353 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38355 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38356 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38359 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38363 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38364 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38372 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38386 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38387 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38391 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38399 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38408 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38412 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38414 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38424 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38427 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38430 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38431 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38436 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38439 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38444 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38450 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38455 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38457 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38458 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38465 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38466 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38468 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38473 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38474 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38475 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38478 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38491 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38495 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38496 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38510 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38511 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38514 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38526 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38537 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38539 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38540 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38541 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38543 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38544 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38557 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38559 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38560 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38569 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38587 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38588 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38601 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38602 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38605 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38606 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38609 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38622 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38629 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38641 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38642 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38644 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38645 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38646 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38659 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38660 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38664 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38665 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38668 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38669 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38673 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38674 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38678 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38683 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38691 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38692 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38694 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38695 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38700 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38701 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38706 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38709 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38710 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38725 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38732 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38735 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39677 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39678 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39688 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39703 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39732 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39742 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39746 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39756 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39763 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39764 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39765 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39773 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39775 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39782 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39791 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39792 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39794 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39798 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39808 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39830 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39832 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39834 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39838 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39847 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39850 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39851 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39857 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39858 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39875 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39889 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39890 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39894 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39902 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39910 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39926 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39931 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39932 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39940 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39947 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39949 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39953 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39965 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39989 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40020 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40030 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40037 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40040 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-40044 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40051 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40053 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40070 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40075 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40078 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40102 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40104 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40109 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40115 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40140 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40153 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40155 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40160 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40171 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40181 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40195 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40211 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40231 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40239 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40255 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40264 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40280 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40283 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40284 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40287 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40292 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40293 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40297 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40362 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-40363 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68185 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68188 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68208 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68209 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68211 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68223 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68226 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68228 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68229 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68231 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68259 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68261 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68262 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68265 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68283 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68292 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68299 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68304 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68309 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68310 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68313 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68331 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68337 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68340 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68353 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68368 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68372 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68379 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68752 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68756 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68776 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68784 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68803 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68814 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-71064 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-71077 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71083 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71087 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71088 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71094 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71097 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71098 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71104 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71126 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71127 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71128 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71131 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71132 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71135 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71147 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71160 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-71202 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71229 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71236 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71273 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71286 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71295 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71296 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71297 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71298 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71301 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-22976 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-22977 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-22981 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-22985 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-22989 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-22991 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-22992 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-22993 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-22996 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23000 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23003 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-23011 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23017 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23021 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23023 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23031 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23038 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23047 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23057 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23058 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23059 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23061 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23066 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23067 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23069 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23070 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23084 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23086 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23103 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23104 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23107 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23108 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23113 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23116 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23117 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23120 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23122 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23125 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23128 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23129 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23130 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23133 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23135 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23138 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23140 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23142 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23148 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-23151 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23164 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23166 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23173 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23186 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23196 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23199 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23200 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23202 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23230 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23241 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23242 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-23248 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23249 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23250 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23251 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23255 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23272 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23274 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23276 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23278 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23282 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23286 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23292 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23293 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23296 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23299 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23300 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23304 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23307 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23316 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23329 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23332 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23335 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23336 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23340 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23346 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23351 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23365 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23368 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23369 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23370 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23377 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23381 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23382 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23386 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23391 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23398 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23414 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23437 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23439 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23442 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23444 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23445 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23449 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23461 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23462 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-23466 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23467 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23472 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31394 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31400 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31403 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31404 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31407 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-31415 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31416 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31421 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31422 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31423 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31424 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31427 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31435 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-31436 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-31438 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31440 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31441 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31442 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31443 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31446 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31447 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31448 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-31450 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-31451 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31453 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31454 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31458 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31468 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31469 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31473 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31479 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31480 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31482 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31483 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31487 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31492 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31495 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31496 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31498 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31499 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31503 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31507 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31510 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31512 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31515 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31518 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31519 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31521 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31526 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31528 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31531 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-31533 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-31542 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31543 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31546 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31548 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31551 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31554 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-31555 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31557 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-31565 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31574 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31575 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31579 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31590 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31591 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31592 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31593 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31600 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-31604 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31609 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-31619 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31624 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31625 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31628 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31630 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31632 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31633 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-31634 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31637 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-31638 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-31642 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31647 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31648 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31661 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31662 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-31665 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31666 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31667 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31672 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31673 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31674 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31675 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31676 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-31678 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31679 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31680 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31681 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31682 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-31691 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31692 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31693 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31698 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31699 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31701 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31719 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-31738 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31739 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-31742 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31752 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31758 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31767 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31771 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-31773 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-31774 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31775 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31777 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31779 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-31781 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43009 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43012 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43013 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43016 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43017 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43018 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-43019 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43021 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43022 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43024 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43025 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43026 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43028 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43033 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43034 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43035 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43042 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43043 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43048 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-43054 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43055 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-43060 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43061 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43062 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-43063 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43064 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43065 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43067 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-43071 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-43079 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43080 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43084 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43085 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43088 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43089 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43091 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43093 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43094 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43095 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43099 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-43107 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43109 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43111 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43119 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43124 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43129 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43132 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43136 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43137 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43139 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-43140 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43143 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43144 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43152 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43153 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43156 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43157 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43161 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43169 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43170 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43171 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43172 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-43176 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-43180 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43187 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-43199 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-43201 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43204 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43213 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-43214 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43215 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-43216 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43234 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43238 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43240 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43251 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43261 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43266 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43267 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43273 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43277 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43278 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43280 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43287 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43288 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43292 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43296 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-43315 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43323 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43325 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43333 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43346 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43350 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-43351 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43362 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-43363 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43365 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-43366 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43374 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43394 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43395 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43396 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43401 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43402 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-43405 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-43406 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-43407 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-43408 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43409 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43411 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43413 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43416 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43429 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43436 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43437 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43441 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-43443 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43445 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43452 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-43456 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-43459 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43463 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43466 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-43468 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43469 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-43472 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43473 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43475 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43491 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45834 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45835 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45836 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45838 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45840 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45841 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45842 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45843 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-45844 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45845 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45846 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45855 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45857 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45862 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45886 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45892 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45899 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45912 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45944 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45945 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45973 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45981 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45983 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45985 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45988 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-46000 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-46012 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46021 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46023 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46027 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-46028 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46032 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46037 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-46050 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46051 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46066 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46070 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46078 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46079 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46082 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46095 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46102 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-46107 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46111 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46115 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-46132 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46137 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-46138 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-46139 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46146 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46151 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46158 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46168 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46170 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46172 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46182 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46188 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46193 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46207 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46214 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46252 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46253 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46273 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-46280 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46291 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46304 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-46315 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46320 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-46322 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52909 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52915 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52925 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52927 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52929 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-52930 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52937 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52946 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-52954 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-52958 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-52961 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52963 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52964 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52966 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52967 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-52970 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52975 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52977 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52981 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-52982 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-52988 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52990 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52994 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52999 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-53003 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-53012 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53014 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53021 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53022 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53032 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53034 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53035 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53047 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53061 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53069 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-53070 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-53073 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53074 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53076 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53084 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53086 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-53096 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53101 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53103 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53105 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53114 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53134 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53151 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-53163 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53164 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53167 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53168 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53181 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53183 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-53184 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-53187 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53188 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53191 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53199 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-53205 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53206 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53208 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53218 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53219 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53220 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53221 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-53225 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-53227 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53229 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-53232 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-53236 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53238 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53241 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53245 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53249 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53257 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53263 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53265 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53269 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53281 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53283 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53287 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53306 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53317 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53318 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53321 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53349 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53358 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53365 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53372 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53394 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-53400 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53402 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-63803 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-63822 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63832 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63838 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63858 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-63860 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-63863 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-63868 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63870 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-63897 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63900 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63902 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63903 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63926 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63937 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63942 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63968 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-63976 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-63977 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-63980 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-63983 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63985 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-63986 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63995 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64004 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64005 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64006 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64012 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64036 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64038 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64046 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-64052 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64073 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64076 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64079 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64103 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64106 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64112 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64118 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64121 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64123 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64125 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-64126 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64127 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64128 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64133 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64170 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64178 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64185 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64190 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64205 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64206 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-64290 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64293 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64309 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64325 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64346 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64351 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64362 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64363 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64373 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64424 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64433 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64452 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64477 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64479 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2020-36782 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-20320 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-4454 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-45402 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2021-46904 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-46909 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-46910 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-46917 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-46918 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-46920 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-46923 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47020 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47033 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47079 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47182 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47190 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47197 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47199 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47202 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47210 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47215 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47217 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47237 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47250 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47266 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47272 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47325 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47349 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47360 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-47373 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-47380 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47398 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47420 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47422 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47426 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47438 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47455 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47481 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47490 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47499 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47504 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47516 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47527 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-47537 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47538 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47539 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47550 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47558 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47578 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47582 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47601 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47607 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47617 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47622 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47623 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-2905 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3344 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-3606 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-48628 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48635 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48639 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48640 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48641 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48643 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48660 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48673 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48675 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48690 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48691 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48697 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48704 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48705 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48706 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48707 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48709 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48710 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-48713 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48720 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48721 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48724 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48725 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48727 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48728 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48729 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48731 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48741 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48746 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48752 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48763 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48764 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48767 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48768 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48769 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48770 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48800 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48806 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-48809 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-48812 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-48813 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-48814 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-48815 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-48817 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-48818 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-48823 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-48825 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-48887 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48890 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48896 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48944 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48963 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48979 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49005 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49027 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49046 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49064 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49065 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49103 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49127 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49139 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49155 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49157 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49177 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49178 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49206 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49209 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49225 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49257 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49287 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49352 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49402 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49422 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49436 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49447 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49466 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49476 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49498 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49516 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49532 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49653 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49731 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49746 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49749 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49752 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49760 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-49766 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-49769 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49772 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49782 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49784 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-49800 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49807 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-49813 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49817 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49830 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49835 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49841 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49874 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49880 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49889 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49891 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49896 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-49906 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49915 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49938 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-49955 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50012 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50025 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50042 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50045 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50076 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50104 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50107 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50108 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50110 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50134 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50135 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50176 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50191 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50197 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50201 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50218 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50230 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50232 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50244 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50247 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50249 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50250 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50253 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50269 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50275 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50276 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50278 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50287 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50304 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50311 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50317 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50322 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50331 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50332 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50337 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50342 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50349 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50351 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50352 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50353 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50354 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50357 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50365 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50372 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50387 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50389 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50391 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50395 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50416 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50424 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50429 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50434 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50444 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50458 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50460 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50466 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50472 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50473 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50477 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50479 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50481 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50482 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50489 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50500 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50505 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50510 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50515 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50520 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50521 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50527 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50528 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50532 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50535 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50537 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50544 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50550 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50556 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50561 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50562 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50566 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50577 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50578 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50617 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50618 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50619 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50626 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50632 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50633 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50639 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50643 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50645 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50646 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50648 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50650 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50654 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50655 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50658 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50667 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50669 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50675 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50699 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50704 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50705 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50718 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50719 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-50724 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50728 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50733 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50742 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50749 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50751 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50760 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-50771 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50781 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50809 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50862 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50868 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50884 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-37454 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-52462 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52465 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-52467 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-52470 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-52473 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-52516 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52623 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-52653 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-52675 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-52700 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52704 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52706 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52732 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52736 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52743 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52744 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52747 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52750 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52778 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52781 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52782 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52792 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52806 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-52808 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52811 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-52815 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52819 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52828 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52845 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-52849 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52877 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52882 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-52883 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-52887 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52928 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52936 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52937 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52938 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52942 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52981 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52982 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52986 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-52993 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52994 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53002 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53005 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53007 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53009 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53011 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53012 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53013 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53014 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53015 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53028 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53031 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53048 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53049 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53055 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53069 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53074 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53091 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53093 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53115 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53127 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53128 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53131 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53165 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53167 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53174 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53190 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53197 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53211 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53233 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53234 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53242 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53245 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53250 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53268 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53271 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53279 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53291 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53313 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53319 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53332 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53334 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53341 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53344 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53359 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53369 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53375 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53378 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53387 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53390 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53391 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53400 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53408 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53409 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53410 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53411 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53419 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53422 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53431 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53443 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53449 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53456 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53460 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53467 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53474 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53482 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53489 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53498 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53511 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53518 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53523 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53548 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53557 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53571 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53588 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53593 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53594 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53602 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53603 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53605 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53607 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53610 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53631 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53648 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53656 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53670 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53671 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53685 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53712 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53716 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53728 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53746 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53754 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53760 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53767 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53790 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53792 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53793 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53798 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53814 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53818 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53826 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53830 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53836 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53852 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53866 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53867 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54011 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54024 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54041 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54043 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54046 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54051 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54056 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54057 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54087 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54088 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54097 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54098 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54099 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54123 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54134 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54174 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54189 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54190 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54195 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54223 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54234 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54245 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54288 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54305 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54306 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54321 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-7042 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-14027 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-25740 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26595 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26605 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26647 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26659 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26687 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26691 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26695 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26714 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26715 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-26721 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26751 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26760 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26775 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26776 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26786 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26818 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26820 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26844 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26845 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26891 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26900 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-26926 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-26945 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26950 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-27059 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-27073 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-27393 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-35790 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35834 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35836 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35859 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35860 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35865 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35879 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35901 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35903 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35917 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35922 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35945 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35973 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-35974 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35981 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-36004 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-36007 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-36008 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-36489 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-36893 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-36909 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-36911 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-36918 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-36919 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-36932 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-36937 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-36938 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-36954 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-36955 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-36962 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-38566 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-38594 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-38600 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-38607 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-39468 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-39473 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-39483 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-39509 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-40908 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-40964 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-40992 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-40997 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-40999 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-41004 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-41047 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-41063 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-41066 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-41068 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-41072 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-41084 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-41098 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-42063 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42067 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42068 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42071 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42073 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42080 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42085 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42097 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42098 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42109 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42126 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42129 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42151 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42237 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42243 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42244 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-43098 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-43817 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-43840 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-43863 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-43890 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-43893 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-43894 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-44947 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2024-45012 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-45017 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-45019 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-45027 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-45029 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46672 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46681 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46692 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46698 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46706 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46707 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46709 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46720 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46765 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46784 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46788 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46797 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46823 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46825 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46860 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46861 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46862 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47143 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47671 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47674 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47702 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47728 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47734 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47794 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47809 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49875 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50001 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-50093 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50101 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50107 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50138 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50163 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50194 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50201 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50252 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53047 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53051 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53064 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53072 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53094 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53097 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53125 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53151 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-53157 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53161 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53172 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53175 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53180 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53189 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53198 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53202 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53210 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53215 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53217 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53225 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53230 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53231 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53238 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53685 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-55881 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56372 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56531 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56532 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56533 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56545 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56549 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56583 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56584 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56587 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-56588 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56592 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56593 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56594 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56613 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56617 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56624 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56625 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56629 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56632 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56641 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56657 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56659 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56668 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56681 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56696 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56698 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56701 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56702 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56707 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56710 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56712 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56714 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56715 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-56720 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56728 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56742 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56745 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56747 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56748 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56752 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56756 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56773 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56782 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56787 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57804 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57807 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57883 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57914 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57933 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57936 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57952 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57973 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57994 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57999 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-58070 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-58074 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-58078 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-58079 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-58084 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-58090 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21632 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21634 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21636 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21637 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21638 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21639 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21640 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21644 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21645 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21690 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21705 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21708 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21712 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21713 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21716 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21723 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21744 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21750 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21766 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21770 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21776 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21779 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21783 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21807 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21810 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21827 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21830 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21831 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21832 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21833 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21866 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21872 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21875 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21876 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21877 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21880 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21881 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21884 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21886 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21889 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21890 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21898 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21901 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21906 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21907 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21909 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21910 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21916 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21918 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21921 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21922 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21924 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21930 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21937 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21953 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21970 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21976 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21978 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21981 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21986 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21992 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21995 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21996 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-22008 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-22009 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-22031 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-22045 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-22117 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-22128 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-23144 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-23147 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-23149 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-23154 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-23162 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37743 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37744 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37756 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-37788 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37792 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37793 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37794 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37801 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37805 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37837 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37867 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37895 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37907 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37911 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37932 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37936 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37938 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37945 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37984 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38009 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38010 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38016 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38020 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38037 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38039 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38045 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38049 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38096 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38148 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38168 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38170 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38193 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38202 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38262 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38268 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38278 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38345 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38402 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38460 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38489 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38505 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38528 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38546 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38576 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38581 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38586 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38591 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38608 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38621 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38623 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38624 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38640 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38643 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38671 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38721 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38733 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39676 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39681 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39721 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39724 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39736 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39737 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39745 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39748 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39752 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39753 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39772 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39784 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39795 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39801 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39811 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39829 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39865 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39886 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39887 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39916 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39929 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39937 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39956 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39959 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39974 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39990 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40010 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40042 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40049 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40057 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40086 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40099 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40103 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40105 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40125 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40159 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40164 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40169 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40219 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40253 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40267 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40325 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40346 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40360 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68170 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68171 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68173 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68178 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68193 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68198 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68200 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68204 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68206 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68207 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68218 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68219 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68227 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68233 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68244 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68281 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68288 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68295 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68298 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68300 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68306 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68308 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68317 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68321 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68326 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68334 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68336 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68345 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68348 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68363 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68378 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68725 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68732 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68758 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68783 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68785 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68794 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68795 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68798 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68802 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68807 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68813 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68818 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68820 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68822 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-71076 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71096 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71108 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71117 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71118 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71119 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71125 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71142 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71154 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71161 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-71182 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-71227 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71232 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71235 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71285 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71305 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-71315 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-22994 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-22997 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-23002 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23005 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23007 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23008 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23009 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23039 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23085 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23119 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23141 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23149 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23154 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23155 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23160 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23190 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23247 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23252 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23259 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23260 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23261 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23290 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23297 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23303 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23310 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23312 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23313 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23352 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23357 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23366 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23367 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23374 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23376 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23379 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23389 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23399 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23417 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23418 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23421 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23430 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23434 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23436 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23475 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31390 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31428 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31486 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31491 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31497 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31520 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31522 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31524 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31556 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31571 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31639 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31655 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31664 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31670 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31671 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31784 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43010 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43030 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43036 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43041 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43066 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43068 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43073 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43092 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43123 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43130 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43148 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43167 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43194 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-43211 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43253 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-43259 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43262 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43265 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43289 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43309 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43311 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43313 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43314 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43344 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43419 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43425 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43428 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43432 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43451 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43477 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43478 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43483 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43484 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43487 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43488 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43496 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45847 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45870 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45872 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45873 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45877 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45880 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45888 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45904 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45913 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45915 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45917 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45919 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45922 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45923 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45925 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45933 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45948 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45953 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45955 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45961 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45963 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45964 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45968 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45982 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45987 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45997 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46003 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46005 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46014 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46018 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-46026 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46038 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46040 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46046 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46049 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46059 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46060 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46063 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46071 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46083 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46088 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46089 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46092 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46101 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46126 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46131 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46144 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46153 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46161 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46167 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46178 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46184 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46196 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46201 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46216 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46224 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46248 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46249 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46262 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46271 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46292 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46302 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46327 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52921 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52936 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52941 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52948 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52949 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52960 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-52965 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52974 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-52984 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52985 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53001 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53007 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53013 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53028 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53037 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53048 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53051 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53060 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53063 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53064 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53080 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53083 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53088 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-53093 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53100 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53102 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53104 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53106 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53111 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53113 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53121 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53123 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53125 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53126 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53142 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53154 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53177 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53190 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53207 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53251 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53252 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53258 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53261 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53274 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53278 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53289 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53291 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53295 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53297 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53304 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53314 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53324 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53327 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53337 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53347 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53348 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53350 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53353 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53364 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53369 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53378 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53385 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53403 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63810 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63869 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63871 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63872 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-63964 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63973 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63974 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-63989 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63997 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63998 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63999 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64003 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-64021 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64028 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64060 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64070 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64105 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64110 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64131 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64134 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64144 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64146 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64155 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64162 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-64171 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64175 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-64176 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64179 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64182 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64183 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64184 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64186 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64187 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64485 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64512 | LOW2.8 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-7383 | LOW2.8 | openssl 1:3.5.5-1.el9 fixed in 1:3.5.5-4.el9_8 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-24056 | LOW2.8 | pkgconf 1.7.3-10.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-24056 | LOW2.8 | pkgconf-pkg-config 1.7.3-10.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-13837 | LOW2.8 | python3-devel 3.9.25-5.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-42308 | LOW2.8 | python3-devel 3.9.25-5.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-25645 | LOW2.8 | python3-pip-wheel 21.3.1-1.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53655 | LOW2.8 | tar 2:1.34-11.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-5704 | LOW2.8 | tar 2:1.34-11.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-28418 | LOW2.8 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45130 | LOW2.8 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-55892 | LOW2.8 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-59857 | LOW2.8 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-1725 | LOW2.8 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-2874 | LOW2.8 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-2923 | LOW2.8 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-2980 | LOW2.8 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2022-3153 | LOW2.8 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-3278 | LOW2.8 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2022-4293 | LOW2.8 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-1264 | LOW2.8 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-2609 | LOW2.8 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-46246 | LOW2.8 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-5441 | LOW2.8 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-45306 | LOW2.8 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-22134 | LOW2.8 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-24014 | LOW2.8 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-41990 | LOW2.8 | libgcrypt 1.10.0-11.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4519 | LOW2.8 | python3 3.9.25-5.el9 fixed in 3.9.25-7.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-13462 | LOW2.8 | python3 3.9.25-5.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-2297 | LOW2.8 | python3 3.9.25-5.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3479 | LOW2.8 | python3 3.9.25-5.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4519 | LOW2.8 | python3-libs 3.9.25-5.el9 fixed in 3.9.25-7.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-13462 | LOW2.8 | python3-libs 3.9.25-5.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-2297 | LOW2.8 | python3-libs 3.9.25-5.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3479 | LOW2.8 | python3-libs 3.9.25-5.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-70873 | LOW2.8 | sqlite-libs 3.34.1-9.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-59995 | LOW2.75 | openssh-clients 9.9p1-7.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-59996 | LOW2.75 | openssh-clients 9.9p1-7.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-59997 | LOW2.75 | openssh-clients 9.9p1-7.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-4873 | LOW2.7 | curl-minimal 7.76.1-41.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW2.7 | curl-minimal 7.76.1-41.el9 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-7168 | LOW2.7 | curl-minimal 7.76.1-41.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-4046 | LOW2.7 | glibc-devel 2.34-262.el9 fixed in 2.34-270.el9_8 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-4046 | LOW2.7 | glibc-headers 2.34-262.el9 fixed in 2.34-270.el9_8 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-33948 | LOW2.7 | jq 1.6-19.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-47238 | LOW2.7 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50700 | LOW2.7 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50774 | LOW2.7 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50784 | LOW2.7 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54092 | LOW2.7 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54216 | LOW2.7 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54243 | LOW2.7 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39968 | LOW2.7 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39972 | LOW2.7 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40204 | LOW2.7 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40353 | LOW2.7 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-71225 | LOW2.7 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23053 | LOW2.7 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23457 | LOW2.7 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-53194 | LOW2.7 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50755 | LOW2.7 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54181 | LOW2.7 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-4873 | LOW2.7 | libcurl-minimal 7.76.1-41.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW2.7 | libcurl-minimal 7.76.1-41.el9 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-7168 | LOW2.7 | libcurl-minimal 7.76.1-41.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-42766 | LOW2.7 | openssl 1:3.5.5-1.el9 fixed in 1:3.5.5-4.el9_8 | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2026-42767 | LOW2.7 | openssl 1:3.5.5-1.el9 fixed in 1:3.5.5-4.el9_8 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-4565 | LOW2.7 | protobuf-compiler 3.14.0-17.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-12781 | LOW2.7 | python3-devel 3.9.25-5.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-3276 | LOW2.7 | python3-devel 3.9.25-5.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-45409 | LOW2.7 | python3-pip-wheel 21.3.1-1.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-59875 | LOW2.7 | tar 2:1.34-11.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | util-linux 2.37.4-25.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | util-linux-core 2.37.4-25.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-44656 | LOW2.7 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2024-41957 | LOW2.7 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-53841 | LOW2.65 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39970 | LOW2.65 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40217 | LOW2.65 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40330 | LOW2.65 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40338 | LOW2.65 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40343 | LOW2.65 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40344 | LOW2.65 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-38541 | LOW2.64 | kernel-headers 5.14.0-688.el9 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2023-52735 | LOW2.64 | kernel-headers 5.14.0-688.el9 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2023-52798 | LOW2.64 | kernel-headers 5.14.0-688.el9 No fix yet | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2024-38605 | LOW2.64 | kernel-headers 5.14.0-688.el9 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2025-58160 | LOW2.63 | libldb 4.23.5-6.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-58160 | LOW2.63 | libwbclient 4.23.5-6.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11731 | LOW2.63 | libxslt 1.1.34-12.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1795 | LOW2.63 | python3 3.9.25-5.el9 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1795 | LOW2.63 | python3-libs 3.9.25-5.el9 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-58160 | LOW2.63 | samba-client-libs 4.23.5-6.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-58160 | LOW2.63 | samba-common 4.23.5-6.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-58160 | LOW2.63 | samba-common-libs 4.23.5-6.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2020-36558 | LOW2.6 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-50721 | LOW2.6 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50735 | LOW2.6 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50852 | LOW2.6 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54226 | LOW2.6 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40178 | LOW2.6 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23035 | LOW2.6 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47327 | LOW2.6 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-54222 | LOW2.6 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-4516 | LOW2.6 | python3-devel 3.9.25-5.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6845 | LOW2.55 | binutils 2.35.2-72.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57360 | LOW2.55 | binutils 2.35.2-72.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6845 | LOW2.55 | binutils-gold 2.35.2-72.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57360 | LOW2.55 | binutils-gold 2.35.2-72.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6845 | LOW2.55 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57360 | LOW2.55 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-5450 | LOW2.55 | glibc-devel 2.34-262.el9 fixed in 2.34-272.el9_8 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-5928 | LOW2.55 | glibc-devel 2.34-262.el9 fixed in 2.34-274.el9_8 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-5450 | LOW2.55 | glibc-headers 2.34-262.el9 fixed in 2.34-272.el9_8 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-5928 | LOW2.55 | glibc-headers 2.34-262.el9 fixed in 2.34-274.el9_8 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-40121 | LOW2.55 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68197 | LOW2.55 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50819 | LOW2.5 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-16517 | LOW2.46 | libarchive 3.5.3-8.el9 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0992 | LOW2.46 | libxml2 2.9.13-14.el9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-14017 | LOW2.45 | curl-minimal 7.76.1-41.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-8926 | LOW2.45 | curl-minimal 7.76.1-41.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-3056 | LOW2.45 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2021-47441 | LOW2.45 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.45 | libcurl-minimal 7.76.1-41.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-8926 | LOW2.45 | libcurl-minimal 7.76.1-41.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15282 | LOW2.45 | python3-devel 3.9.25-5.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-0672 | LOW2.45 | python3-devel 3.9.25-5.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | curl-minimal 7.76.1-41.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-1376 | LOW2.4 | elfutils-debuginfod-client 0.194-1.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gnupg2 2.3.3-5.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gnupg2 2.3.3-5.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-41991 | LOW2.4 | gzip 1.12-1.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-27672 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-48751 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48784 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48816 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-48899 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48931 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48985 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48989 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-48997 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49089 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49149 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49286 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49344 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49414 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49597 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49607 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49771 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-49781 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50373 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50671 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-50677 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52568 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52786 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52898 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52909 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53186 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53188 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53345 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53368 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53452 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53520 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53623 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53703 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53710 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53755 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53759 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53777 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53794 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53799 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53815 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53816 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53824 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53832 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53853 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54071 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54206 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54287 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26698 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42107 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-44954 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-45003 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46679 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46787 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47660 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47668 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50006 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50010 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50135 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50183 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50277 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53088 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53100 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53124 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53136 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53169 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53178 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56637 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56729 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57974 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21732 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21892 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21938 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22050 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37985 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38008 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38048 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38078 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38083 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38112 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38232 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38440 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38462 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38477 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38524 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38617 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-38632 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38681 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39673 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39713 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39726 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39754 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39927 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39961 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39977 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39980 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39992 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40011 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40016 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40056 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40085 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40110 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40120 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40129 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40139 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40179 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40187 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40197 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40215 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40220 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40238 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40250 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40252 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40254 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40331 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40342 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68239 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68241 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68296 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68312 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68745 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23004 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23071 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23126 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23207 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23212 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23348 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23440 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23441 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23452 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31389 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31393 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-31456 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31523 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31535 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31572 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31697 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43047 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43053 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43383 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-43420 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43448 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45949 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46017 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52955 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-53008 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53108 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-48745 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49554 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49571 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49633 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50259 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50697 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50847 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52478 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53786 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54007 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54042 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54128 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54202 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54308 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54309 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-23196 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-24855 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26859 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26862 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26915 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-36949 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42253 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42287 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46710 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49866 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50082 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56568 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21651 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21701 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21825 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21895 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-23151 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37920 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39813 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39991 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40357 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68181 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68214 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68264 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68373 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68374 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-71111 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23101 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23118 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23275 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23302 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31466 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43439 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45905 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46298 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53352 | LOW2.4 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | libcurl-minimal 7.76.1-41.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-13176 | LOW2.4 | openssl 1:3.5.5-1.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-64118 | LOW2.4 | tar 2:1.34-11.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | util-linux 2.37.4-25.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | util-linux-core 2.37.4-25.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-57452 | LOW2.4 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-48706 | LOW2.4 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-43374 | LOW2.4 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-47814 | LOW2.4 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-1485 | LOW2.38 | glib2 2.68.4-19.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-49934 | LOW2.35 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-31620 | LOW2.35 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-3903 | LOW2.35 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-50842 | LOW2.29 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54239 | LOW2.29 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40166 | LOW2.29 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40308 | LOW2.29 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68242 | LOW2.29 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68360 | LOW2.29 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53831 | LOW2.29 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11468 | LOW2.29 | python3-devel 3.9.25-5.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-0865 | LOW2.29 | python3-devel 3.9.25-5.el9 fixed in 3.9.25-5.el9_8 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-1502 | LOW2.29 | python3-devel 3.9.25-5.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2024-43802 | LOW2.29 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-5278 | LOW2.24 | coreutils-single 8.32-40.el9 fixed in 8.32-41.el9_8 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-56392 | LOW2.24 | coreutils-single 8.32-40.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43895 | LOW2.24 | jq 1.6-19.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47449 | LOW2.24 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49196 | LOW2.24 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-50579 | LOW2.24 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-2019 | LOW2.24 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-52508 | LOW2.24 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53733 | LOW2.24 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-7192 | LOW2.24 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-26810 | LOW2.24 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-38559 | LOW2.24 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-42114 | LOW2.24 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42123 | LOW2.24 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40081 | LOW2.24 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40206 | LOW2.24 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40281 | LOW2.24 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68768 | LOW2.24 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2020-14304 | LOW2.24 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-48761 | LOW2.24 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-2269 | LOW2.24 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52738 | LOW2.24 | kernel-headers 5.14.0-688.el9 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2023-52800 | LOW2.24 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52801 | LOW2.24 | kernel-headers 5.14.0-688.el9 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2023-52884 | LOW2.24 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53718 | LOW2.24 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54086 | LOW2.24 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54209 | LOW2.24 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54210 | LOW2.24 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54247 | LOW2.24 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26648 | LOW2.24 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26661 | LOW2.24 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26662 | LOW2.24 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26672 | LOW2.24 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26712 | LOW2.24 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26758 | LOW2.24 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26769 | LOW2.24 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26854 | LOW2.24 | kernel-headers 5.14.0-688.el9 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2024-26857 | LOW2.24 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-26890 | LOW2.24 | kernel-headers 5.14.0-688.el9 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2024-36030 | LOW2.24 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-36031 | LOW2.24 | kernel-headers 5.14.0-688.el9 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2024-36910 | LOW2.24 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-38384 | LOW2.24 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-38388 | LOW2.24 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42230 | LOW2.24 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40021 | LOW2.24 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40123 | LOW2.24 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40157 | LOW2.24 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40183 | LOW2.24 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40198 | LOW2.24 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40200 | LOW2.24 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23032 | LOW2.24 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23458 | LOW2.24 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31401 | LOW2.24 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-29768 | LOW2.24 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-28420 | LOW2.24 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-42307 | LOW2.24 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2023-54213 | LOW2.19 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-39920 | LOW2.19 | kernel-headers 5.14.0-688.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2022-50878 | LOW2.19 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-47233 | LOW2.19 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-54270 | LOW2.19 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40275 | LOW2.19 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-48231 | LOW2.19 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-48232 | LOW2.19 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-48233 | LOW2.19 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-48234 | LOW2.19 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-48235 | LOW2.19 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-48236 | LOW2.19 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-48237 | LOW2.19 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2022-50358 | LOW2.14 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-45803 | LOW2.14 | python3-pip-wheel 21.3.1-1.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2024-41965 | LOW2.14 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-26603 | LOW2.14 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-24515 | LOW2.12 | expat 2.5.0-6.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6170 | LOW2.12 | libxml2 2.9.13-14.el9 fixed in 2.9.13-14.el9_8.2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-35388 | LOW2.12 | openssh 9.9p1-7.el9 fixed in 9.9p1-7.el9_8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-35388 | LOW2.12 | openssh-server 9.9p1-7.el9 fixed in 9.9p1-7.el9_8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27139 | LOW2.12 | stdlib v1.22.10 fixed in 1.25.8, 1.26.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-1974 | LOW2.09 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50558 | LOW2.09 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52872 | LOW2.09 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53720 | LOW2.09 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54295 | LOW2.09 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42229 | LOW2.09 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40173 | LOW2.09 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40218 | LOW2.09 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2019-16089 | LOW2.09 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-25260 | LOW2.04 | elfutils-debuginfod-client 0.194-1.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-4438 | LOW2.04 | glibc-devel 2.34-262.el9 fixed in 2.34-270.el9_8 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-4438 | LOW2.04 | glibc-headers 2.34-262.el9 fixed in 2.34-270.el9_8 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-50853 | LOW2.04 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53695 | LOW2.04 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53994 | LOW2.04 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40162 | LOW2.04 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53715 | LOW1.99 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-32728 | LOW1.94 | openssh-clients 9.9p1-7.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils 2.35.2-72.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils-gold 2.35.2-72.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-55654 | LOW1.89 | openssh-clients 9.9p1-7.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-45446 | LOW1.89 | openssl 1:3.5.5-1.el9 fixed in 1:3.5.5-4.el9_8 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-9232 | LOW1.86 | openssl 1:3.5.5-1.el9 No fix yet | 2.3% Low-Moderate Risk | Post-Exploit |
| CVE-2023-54074 | LOW1.84 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2020-35501 | LOW1.73 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68740 | LOW1.73 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66861 | LOW1.68 | binutils 2.35.2-72.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66862 | LOW1.68 | binutils 2.35.2-72.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66863 | LOW1.68 | binutils 2.35.2-72.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.68 | binutils 2.35.2-72.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.68 | binutils 2.35.2-72.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.68 | binutils 2.35.2-72.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils 2.35.2-72.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66861 | LOW1.68 | binutils-gold 2.35.2-72.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66862 | LOW1.68 | binutils-gold 2.35.2-72.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66863 | LOW1.68 | binutils-gold 2.35.2-72.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.68 | binutils-gold 2.35.2-72.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.68 | binutils-gold 2.35.2-72.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.68 | binutils-gold 2.35.2-72.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils-gold 2.35.2-72.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66861 | LOW1.68 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66862 | LOW1.68 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66863 | LOW1.68 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.68 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.68 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.68 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gnupg2 2.3.3-5.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-68191 | LOW1.68 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50628 | LOW1.68 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54034 | LOW1.68 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-41007 | LOW1.68 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47738 | LOW1.68 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50057 | LOW1.68 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39964 | LOW1.68 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23045 | LOW1.68 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-46934 | LOW1.68 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47430 | LOW1.68 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-3629 | LOW1.68 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3633 | LOW1.68 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-48939 | LOW1.68 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50575 | LOW1.68 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50706 | LOW1.68 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50712 | LOW1.68 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50750 | LOW1.68 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50820 | LOW1.68 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50823 | LOW1.68 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50824 | LOW1.68 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50825 | LOW1.68 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50827 | LOW1.68 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50850 | LOW1.68 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50856 | LOW1.68 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50859 | LOW1.68 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50882 | LOW1.68 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50883 | LOW1.68 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50887 | LOW1.68 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-1513 | LOW1.68 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52926 | LOW1.68 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53998 | LOW1.68 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54058 | LOW1.68 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54116 | LOW1.68 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54144 | LOW1.68 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54171 | LOW1.68 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54177 | LOW1.68 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54211 | LOW1.68 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54218 | LOW1.68 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54220 | LOW1.68 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54233 | LOW1.68 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54252 | LOW1.68 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54294 | LOW1.68 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54315 | LOW1.68 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54320 | LOW1.68 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26612 | LOW1.68 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46794 | LOW1.68 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50044 | LOW1.68 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50211 | LOW1.68 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50280 | LOW1.68 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-40035 | LOW1.68 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40268 | LOW1.68 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40341 | LOW1.68 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68744 | LOW1.68 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68746 | LOW1.68 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68751 | LOW1.68 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68775 | LOW1.68 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68782 | LOW1.68 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-71148 | LOW1.68 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71224 | LOW1.68 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-31668 | LOW1.68 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-4519 | LOW1.68 | python3-devel 3.9.25-5.el9 fixed in 3.9.25-7.el9_8 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-13462 | LOW1.68 | python3-devel 3.9.25-5.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-2297 | LOW1.68 | python3-devel 3.9.25-5.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3479 | LOW1.68 | python3-devel 3.9.25-5.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-39804 | LOW1.68 | tar 2:1.34-11.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-4217 | LOW1.68 | unzip 6.0-59.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1150 | LOW1.58 | binutils 2.35.2-72.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1151 | LOW1.58 | binutils 2.35.2-72.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1150 | LOW1.58 | binutils-gold 2.35.2-72.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1151 | LOW1.58 | binutils-gold 2.35.2-72.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1150 | LOW1.58 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1151 | LOW1.58 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1795 | LOW1.58 | python3-devel 3.9.25-5.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW1.48 | gnupg2 2.3.3-5.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69644 | LOW1.43 | binutils 2.35.2-72.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.43 | binutils 2.35.2-72.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.43 | binutils 2.35.2-72.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69644 | LOW1.43 | binutils-gold 2.35.2-72.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.43 | binutils-gold 2.35.2-72.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.43 | binutils-gold 2.35.2-72.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69644 | LOW1.43 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.43 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.43 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50665 | LOW1.27 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50844 | LOW1.27 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50870 | LOW1.27 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54108 | LOW1.27 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68788 | LOW1.27 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-35388 | LOW1.27 | openssh-clients 9.9p1-7.el9 fixed in 9.9p1-7.el9_8 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-28422 | LOW1.12 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-9323 | NONE0 | python3-urwid 2.1.2-4.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-29111 | NONE0 | systemd 252-67.el9 fixed in 252-67.el9_8.2 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-29111 | NONE0 | systemd-rpm-macros 252-67.el9 fixed in 252-67.el9_8.2 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-29111 | NONE0 | systemd-udev 252-67.el9 fixed in 252-67.el9_8.2 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-41409 | NONE0 | pcre2-syntax 10.40-6.el9 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-54369 | NONE0 | acl 2.3.1-4.el9 fixed in 2.4.0-1.el9_8 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-4105 | NONE0 | systemd 252-67.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-4105 | NONE0 | systemd-rpm-macros 252-67.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-4105 | NONE0 | systemd-udev 252-67.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-4437 | NONE0 | glibc-minimal-langpack 2.34-262.el9 fixed in 2.34-270.el9_8 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-6238 | NONE0 | glibc-minimal-langpack 2.34-262.el9 fixed in 2.34-274.el9_8 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | ncurses-base 6.2-12.20210508.el9 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | ncurses-libs 6.2-12.20210508.el9 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2026-12610 | NONE0 | pam 1.5.1-28.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-54370 | NONE0 | acl 2.3.1-4.el9 fixed in 2.4.0-1.el9_8 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-54371 | NONE0 | attr 2.5.1-3.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-5435 | NONE0 | glibc-minimal-langpack 2.34-262.el9 fixed in 2.34-274.el9_8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-1371 | NONE0 | elfutils-default-yama-scope 0.194-1.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-1377 | NONE0 | elfutils-default-yama-scope 0.194-1.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-24056 | NONE0 | pkgconf-m4 1.7.3-10.el9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-4046 | NONE0 | glibc-minimal-langpack 2.34-262.el9 fixed in 2.34-270.el9_8 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-5450 | NONE0 | glibc-minimal-langpack 2.34-262.el9 fixed in 2.34-272.el9_8 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-5928 | NONE0 | glibc-minimal-langpack 2.34-262.el9 fixed in 2.34-274.el9_8 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | pam 1.5.1-28.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-1376 | NONE0 | elfutils-default-yama-scope 0.194-1.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-25260 | NONE0 | elfutils-default-yama-scope 0.194-1.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-4438 | NONE0 | glibc-minimal-langpack 2.34-262.el9 fixed in 2.34-270.el9_8 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63930 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| GO-2026-5932 | NONE0 | golang.org/x/crypto v0.52.0 No fix yet | — | Not Applicable |
| CVE-2026-46600 | NONE0 | golang.org/x/net v0.55.0 fixed in 0.56.0 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-56852 | NONE0 | golang.org/x/text v0.37.0 fixed in 0.39.0 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-39824 | NONE0 | golang.org/x/sys v0.20.0 fixed in 0.44.0 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-0913 | NONE0 | stdlib v1.22.10 fixed in 1.23.10, 1.24.4 | 0.2% Theoretical Threat | Not Applicable |
Which CVEs are actually reachable — is the vulnerable code even linked and callable.
Live-container probes: default user, writable paths, capabilities, exposed ports.
A step-by-step hardened build plan, with parity tests proving nothing breaks.
Want to check another image? Run a full scan with the Docker Security Scanner.