This image carries significant risk; production deployment is highly discouraged without strict compensating controls. The most severe threats are remote code execution via CVE-2026-45447 in OpenSSL and denial of service or information disclosure via CVE-2026-33845 in GnuTLS, both exploitable over the network. While the image is trusted and pinned by digest, the high volume of critical vulnerabilities in core libraries like openssl-libs and gnutls requires immediate remediation or strict network segmentation (e.g., egress filtering, reduced attack surface) before any production use.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-45447 | HIGH8.1 | openssl-libs 1:3.5.5-1.el9 fixed in 1:3.5.5-4.el9_8 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-33845 | HIGH7.73 | gnutls 3.8.10-3.el9 fixed in 3.8.10-4.el9_8 | 0.6% 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.3% 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-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-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-2025-27113 | HIGH7.5 | libxml2 2.9.13-14.el9 No fix yet | 1.0% 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.1% 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-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-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-28387 | MEDIUM6.88 | openssl-libs 1:3.5.5-1.el9 No fix yet | 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.5% 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-48864 | MEDIUM6.63 | libsolv 0.7.24-4.el9 No fix yet | 0.2% 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-29111 | MEDIUM6.63 | systemd-rpm-macros 252-67.el9 fixed in 252-67.el9_8.2 | 0.1% 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.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-33846 | MEDIUM6.38 | gnutls 3.8.10-3.el9 fixed in 3.8.10-4.el9_8 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-42009 | MEDIUM6.38 | gnutls 3.8.10-3.el9 fixed in 3.8.10-4.el9_8 | 0.8% 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-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.6% Theoretical Threat | Directly Exposed |
| CVE-2026-28390 | MEDIUM6.38 | libldb 4.23.5-6.el9 No fix yet | 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.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40170 | MEDIUM6.38 | libwbclient 4.23.5-6.el9 fixed in 4.23.5-10.el9_8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-28390 | MEDIUM6.38 | libwbclient 4.23.5-6.el9 No fix yet | 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-28390 | MEDIUM6.38 | openssl-libs 1:3.5.5-1.el9 fixed in 1:3.5.5-3.el9_8 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-34183 | MEDIUM6.38 | 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-28388 | MEDIUM6.38 | openssl-libs 1:3.5.5-1.el9 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-28389 | MEDIUM6.38 | openssl-libs 1:3.5.5-1.el9 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-41409 | MEDIUM6.38 | pcre2 10.40-6.el9 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2022-41409 | MEDIUM6.38 | pcre2-syntax 10.40-6.el9 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-0994 | MEDIUM6.38 | protobuf 3.14.0-17.el9 fixed in 3.14.0-17.el9_7 | 0.4% 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-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.4% 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.5% 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.5% 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.6% Theoretical Threat | Directly Exposed |
| CVE-2026-28390 | MEDIUM6.38 | samba-client-libs 4.23.5-6.el9 No fix yet | 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.6% Theoretical Threat | Directly Exposed |
| CVE-2026-28390 | MEDIUM6.38 | samba-common 4.23.5-6.el9 No fix yet | 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.6% Theoretical Threat | Directly Exposed |
| CVE-2026-28390 | MEDIUM6.38 | samba-common-libs 4.23.5-6.el9 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-61726 | MEDIUM6.38 | stdlib v1.22.10 fixed in 1.24.12, 1.25.6 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-61729 | MEDIUM6.38 | stdlib v1.22.10 fixed in 1.24.11, 1.25.5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-25679 | MEDIUM6.38 | stdlib v1.22.10 fixed in 1.25.8, 1.26.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-32280 | MEDIUM6.38 | stdlib v1.22.10 fixed in 1.25.9, 1.26.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-32281 | MEDIUM6.38 | stdlib v1.22.10 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-32283 | MEDIUM6.38 | stdlib v1.22.10 fixed in 1.25.9, 1.26.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-33811 | MEDIUM6.38 | stdlib v1.22.10 fixed in 1.25.10, 1.26.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-33814 | MEDIUM6.38 | stdlib v1.22.10 fixed in 1.25.10, 1.26.3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-39820 | MEDIUM6.38 | stdlib v1.22.10 fixed in 1.25.10, 1.26.3 | 0.4% 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-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.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42011 | MEDIUM6.29 | gnutls 3.8.10-3.el9 fixed in 3.8.10-4.el9_8 | 0.3% 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.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42012 | MEDIUM6.03 | gnutls 3.8.10-3.el9 fixed in 3.8.10-4.el9_8 | 0.3% 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-libs 3.9.25-5.el9 fixed in 3.9.25-7.el9_8 | 0.2% 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-2026-44604 | MEDIUM5.95 | python3-rpm 4.16.1.3-40.el9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-44604 | MEDIUM5.95 | rpm-libs 4.16.1.3-40.el9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-44604 | MEDIUM5.95 | rpm-sign-libs 4.16.1.3-40.el9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-47907 | MEDIUM5.95 | stdlib v1.22.10 fixed in 1.23.12, 1.24.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-37890 | MEDIUM5.9 | librados2 2:20.2.1-0.el9 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-37890 | MEDIUM5.9 | librbd1 2:20.2.1-0.el9 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-13151 | MEDIUM5.9 | libtasn1 4.16.0-9.el9 No fix yet | 1.1% 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-3012 | MEDIUM5.78 | libldb 4.23.5-6.el9 fixed in 4.23.5-10.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3012 | MEDIUM5.78 | libwbclient 4.23.5-6.el9 fixed in 4.23.5-10.el9_8 | 0.2% 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.2% 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.2% 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.2% 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-4105 | MEDIUM5.7 | systemd-rpm-macros 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.2% 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 No fix yet | 0.3% 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 No fix yet | 0.3% 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 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | glibc-minimal-langpack 2.34-262.el9 fixed in 2.34-270.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | glibc-minimal-langpack 2.34-262.el9 No fix yet | 0.3% 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.5% Theoretical Threat | Directly Exposed |
| CVE-2026-2340 | MEDIUM5.52 | libldb 4.23.5-6.el9 fixed in 4.23.5-10.el9_8 | 0.5% 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.5% Theoretical Threat | Directly Exposed |
| CVE-2026-2340 | MEDIUM5.52 | libwbclient 4.23.5-6.el9 fixed in 4.23.5-10.el9_8 | 0.5% 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-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-1933 | MEDIUM5.52 | samba-client-libs 4.23.5-6.el9 fixed in 4.23.5-10.el9_8 | 0.5% 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.5% 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.5% 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.5% 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.5% 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.5% 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-2024-34459 | MEDIUM5.5 | libxml2 2.9.13-14.el9 No fix yet | 2.3% Low-Moderate Risk | 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-32282 | MEDIUM5.44 | stdlib v1.22.10 fixed in 1.25.9, 1.26.2 | 0.3% 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.4% Theoretical Threat | 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-27970 | MEDIUM5.18 | librados2 2:20.2.1-0.el9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-27970 | MEDIUM5.18 | librbd1 2:20.2.1-0.el9 No fix yet | 0.4% 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-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.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | glibc 2.34-262.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | glibc-common 2.34-262.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | glibc-gconv-extra 2.34-262.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | glibc-minimal-langpack 2.34-262.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM5.02 | krb5-libs 1.21.1-9.el9 fixed in 1.21.1-10.el9_8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM5.02 | krb5-libs 1.21.1-9.el9 fixed in 1.21.1-10.el9_8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-0990 | MEDIUM5.02 | libxml2 2.9.13-14.el9 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-31790 | MEDIUM5.02 | openssl-fips-provider 1:3.5.5-1.el9 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-31790 | MEDIUM5.02 | openssl-libs 1:3.5.5-1.el9 fixed in 1:3.5.5-2.el9_8 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-42764 | MEDIUM5.02 | openssl-libs 1:3.5.5-1.el9 fixed in 1:3.5.5-4.el9_8 | 0.7% 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.3% 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.2% 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.3% 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-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-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-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.6% Low-Moderate Risk | Post-Exploit |
| CVE-2022-1619 | MEDIUM4.68 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 2.5% 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.3% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2175 | MEDIUM4.68 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2182 | MEDIUM4.68 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2183 | MEDIUM4.68 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2206 | MEDIUM4.68 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2207 | MEDIUM4.68 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2210 | MEDIUM4.68 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2257 | MEDIUM4.68 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2284 | MEDIUM4.68 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2285 | MEDIUM4.68 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2286 | MEDIUM4.68 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2304 | MEDIUM4.68 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2343 | MEDIUM4.68 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2344 | MEDIUM4.68 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 1.0% 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.4% Theoretical Threat | Directly Exposed |
| CVE-2025-1371 | MEDIUM4.67 | elfutils-debuginfod-client 0.194-1.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1377 | MEDIUM4.67 | elfutils-debuginfod-client 0.194-1.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1371 | MEDIUM4.67 | elfutils-default-yama-scope 0.194-1.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1377 | MEDIUM4.67 | elfutils-default-yama-scope 0.194-1.el9 No fix yet | 0.3% 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.1% 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.1% 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.1% 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 No fix yet | 0.1% 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.3% 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.3% 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-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-2025-22871 | MEDIUM4.59 | stdlib v1.22.10 fixed in 1.23.8, 1.24.2 | 0.7% 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-39826 | MEDIUM4.59 | stdlib v1.22.10 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-6965 | MEDIUM4.58 | sqlite-libs 3.34.1-9.el9 fixed in 3.34.1-9.el9_7 | 64.9% Actively Exploited | Post-Exploit |
| CVE-2022-1620 | MEDIUM4.5 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 1.5% 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-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-4046 | MEDIUM4.5 | glibc-minimal-langpack 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-2025-13465 | MEDIUM4.5 | librados2 2:20.2.1-0.el9 No fix yet | 0.3% 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-2025-13465 | MEDIUM4.5 | librbd1 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-42766 | 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-2026-42767 | MEDIUM4.5 | openssl-libs 1:3.5.5-1.el9 fixed in 1:3.5.5-4.el9_8 | 0.3% 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-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.4% 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-34743 | MEDIUM4.5 | xz-libs 5.2.5-8.el9 No fix yet | 0.4% 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.3% 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-2025-58186 | MEDIUM4.5 | stdlib v1.22.10 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-7264 | MEDIUM4.48 | curl-minimal 7.76.1-41.el9 No fix yet | 16.2% High Exploitation Risk | Post-Exploit |
| CVE-2024-7264 | MEDIUM4.48 | libcurl-minimal 7.76.1-41.el9 No fix yet | 16.2% High Exploitation Risk | Post-Exploit |
| CVE-2025-4516 | MEDIUM4.33 | python3-libs 3.9.25-5.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| 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.1% 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 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | glibc 2.34-262.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | glibc-common 2.34-262.el9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | glibc-common 2.34-262.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | glibc-gconv-extra 2.34-262.el9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | glibc-gconv-extra 2.34-262.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | glibc-minimal-langpack 2.34-262.el9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | glibc-minimal-langpack 2.34-262.el9 No fix yet | 0.3% 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-34180 | MEDIUM4.25 | 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-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 | 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-2025-15079 | MEDIUM4.13 | curl-minimal 7.76.1-41.el9 No fix yet | 0.5% 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 9.9p1-7.el9 fixed in 9.9p1-7.el9_8 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-35414 | MEDIUM4.13 | openssh 9.9p1-7.el9 fixed in 9.9p1-7.el9_8 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-35386 | MEDIUM4.13 | openssh 9.9p1-7.el9 fixed in 9.9p1-7.el9_8 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-35385 | MEDIUM4.13 | openssh-clients 9.9p1-7.el9 fixed in 9.9p1-7.el9_8 | 0.3% 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.2% Theoretical Threat | Post-Exploit |
| CVE-2026-35385 | MEDIUM4.13 | openssh-server 9.9p1-7.el9 fixed in 9.9p1-7.el9_8 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-35414 | MEDIUM4.13 | openssh-server 9.9p1-7.el9 fixed in 9.9p1-7.el9_8 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-35386 | MEDIUM4.13 | openssh-server 9.9p1-7.el9 fixed in 9.9p1-7.el9_8 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-28387 | MEDIUM4.13 | openssl 1:3.5.5-1.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-6100 | MEDIUM4.13 | python3 3.9.25-5.el9 fixed in 3.9.25-7.el9_8 | 0.5% Theoretical Threat | Post-Exploit |
| 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-2025-1376 | MEDIUM4 | elfutils-debuginfod-client 0.194-1.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1376 | MEDIUM4 | elfutils-default-yama-scope 0.194-1.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| 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-2026-6846 | LOW3.98 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.2% 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-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-39881 | LOW3.98 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.6% 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-2345 | LOW3.98 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2022-2522 | LOW3.98 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.5% 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.5% 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-2024-9681 | LOW3.9 | curl-minimal 7.76.1-41.el9 No fix yet | 2.0% 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-2026-5773 | LOW3.82 | curl-minimal 7.76.1-41.el9 No fix yet | 0.4% 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.2% Theoretical Threat | Post-Exploit |
| CVE-2026-32316 | LOW3.82 | jq 1.6-19.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.4% 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-28390 | LOW3.82 | openssl 1:3.5.5-1.el9 fixed in 1:3.5.5-3.el9_8 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-34183 | LOW3.82 | openssl 1:3.5.5-1.el9 fixed in 1:3.5.5-4.el9_8 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-28388 | LOW3.82 | openssl 1:3.5.5-1.el9 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-28389 | LOW3.82 | openssl 1:3.5.5-1.el9 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-3644 | LOW3.82 | python3 3.9.25-5.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-4224 | LOW3.82 | python3 3.9.25-5.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-7210 | LOW3.82 | python3 3.9.25-5.el9 No fix yet | 0.8% 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-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.5% Theoretical Threat | Directly Exposed |
| CVE-2026-34182 | LOW3.77 | openssl 1:3.5.5-1.el9 fixed in 1:3.5.5-4.el9_8 | 0.2% 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-2026-41411 | LOW3.72 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| 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-2026-4786 | LOW3.62 | python3 3.9.25-5.el9 fixed in 3.9.25-7.el9_8 | 0.2% Theoretical Threat | 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-2023-51767 | LOW3.57 | openssh 9.9p1-7.el9 No fix yet | 0.7% 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-2023-51767 | LOW3.57 | openssh-server 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.5% 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.4% 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-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-2024-11053 | LOW3.54 | libcurl-minimal 7.76.1-41.el9 No fix yet | 1.4% 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-4408 | LOW3.53 | libldb 4.23.5-6.el9 fixed in 4.23.5-10.el9_8 | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2026-4480 | LOW3.53 | libldb 4.23.5-6.el9 fixed in 4.23.5-10.el9_8 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-4800 | LOW3.53 | librados2 2:20.2.1-0.el9 No fix yet | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-4800 | LOW3.53 | librbd1 2:20.2.1-0.el9 No fix yet | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-4408 | LOW3.53 | libwbclient 4.23.5-6.el9 fixed in 4.23.5-10.el9_8 | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2026-4480 | LOW3.53 | libwbclient 4.23.5-6.el9 fixed in 4.23.5-10.el9_8 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2023-29824 | LOW3.53 | python3-scipy 1.9.3-2.el9 No fix yet | 1.1% 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 | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2026-4480 | LOW3.53 | samba-client-libs 4.23.5-6.el9 fixed in 4.23.5-10.el9_8 | 1.2% 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 | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2026-4480 | LOW3.53 | samba-common 4.23.5-6.el9 fixed in 4.23.5-10.el9_8 | 1.2% 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 | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2026-4480 | LOW3.53 | samba-common-libs 4.23.5-6.el9 fixed in 4.23.5-10.el9_8 | 1.2% 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-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-2024-25260 | LOW3.4 | elfutils-debuginfod-client 0.194-1.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-25260 | LOW3.4 | elfutils-default-yama-scope 0.194-1.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| 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.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | glibc-common 2.34-262.el9 fixed in 2.34-270.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | glibc-gconv-extra 2.34-262.el9 fixed in 2.34-270.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | glibc-minimal-langpack 2.34-262.el9 fixed in 2.34-270.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| 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-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.4% 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-39979 | LOW3.31 | jq 1.6-19.el9 fixed in 1.6-19.el9_8.2 | 0.3% 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.4% 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-35387 | LOW3.31 | openssh 9.9p1-7.el9 fixed in 9.9p1-7.el9_8 | 0.2% 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-35387 | LOW3.31 | openssh-server 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-33056 | LOW3.31 | tar 2:1.34-11.el9 No fix yet | 0.4% Theoretical Threat | 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.1% 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-2021-20197 | LOW3.21 | binutils 2.35.2-72.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-3805 | LOW3.21 | curl-minimal 7.76.1-41.el9 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-3805 | LOW3.21 | libcurl-minimal 7.76.1-41.el9 No fix yet | 0.7% 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.4% Theoretical Threat | 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.8% Low-Moderate Risk | Post-Exploit |
| CVE-2025-47273 | LOW3.17 | setuptools 69.2.0 fixed in 78.1.1 | 1.4% Low-Moderate Risk | 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.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5419 | LOW3.15 | gnutls 3.8.10-3.el9 fixed in 3.8.10-4.el9_8 | 0.5% 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-45446 | LOW3.15 | 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-4647 | LOW3.11 | binutils 2.35.2-72.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-4647 | LOW3.11 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-39956 | LOW3.11 | jq 1.6-19.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6019 | LOW3.11 | python3 3.9.25-5.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-9232 | LOW3.1 | openssl-libs 1:3.5.5-1.el9 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-5713 | LOW3.06 | python3 3.9.25-5.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31790 | LOW3.01 | openssl 1:3.5.5-1.el9 fixed in 1:3.5.5-2.el9_8 | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2026-42764 | LOW3.01 | openssl 1:3.5.5-1.el9 fixed in 1:3.5.5-4.el9_8 | 0.7% 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.3% 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.2% 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.3% 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-42010 | LOW3 | gnutls 3.8.10-3.el9 fixed in 3.8.10-4.el9_8 | 0.8% 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-45447 | LOW2.92 | openssl 1:3.5.5-1.el9 fixed in 1:3.5.5-4.el9_8 | 1.4% 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-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-2021-3927 | LOW2.81 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2021-3973 | LOW2.81 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2021-3974 | LOW2.81 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2021-4136 | LOW2.81 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 1.8% Low-Moderate Risk | 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.2% 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-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.2% 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-2025-9403 | LOW2.8 | jq 1.6-19.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.3% Theoretical Threat | Post-Exploit |
| CVE-2025-13837 | LOW2.8 | python3 3.9.25-5.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-42308 | LOW2.8 | python3 3.9.25-5.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-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.4% Theoretical Threat | Post-Exploit |
| CVE-2022-3278 | LOW2.8 | vim-minimal 2:8.2.2637-27.el9 No fix yet | 0.8% 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-libs 3.9.25-5.el9 fixed in 3.9.25-7.el9_8 | 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-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.5% Theoretical Threat | Post-Exploit |
| CVE-2026-7168 | LOW2.7 | curl-minimal 7.76.1-41.el9 No fix yet | 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-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.5% Theoretical Threat | Post-Exploit |
| CVE-2026-7168 | LOW2.7 | libcurl-minimal 7.76.1-41.el9 No fix yet | 0.4% 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 | 0.6% 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.3% Theoretical Threat | Post-Exploit |
| CVE-2025-12781 | LOW2.7 | python3 3.9.25-5.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-3276 | LOW2.7 | python3 3.9.25-5.el9 No fix yet | 0.4% 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-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-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-2025-4516 | LOW2.6 | python3 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 | 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-34180 | LOW2.55 | openssl 1:3.5.5-1.el9 fixed in 1:3.5.5-4.el9_8 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-0992 | LOW2.46 | libxml2 2.9.13-14.el9 No fix yet | 0.3% 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-2025-14017 | LOW2.45 | libcurl-minimal 7.76.1-41.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-15282 | LOW2.45 | python3 3.9.25-5.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-0672 | LOW2.45 | python3 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-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-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-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-2025-11468 | LOW2.29 | python3 3.9.25-5.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-0865 | LOW2.29 | python3 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 3.9.25-5.el9 No fix yet | 0.5% 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 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-43895 | LOW2.24 | jq 1.6-19.el9 No fix yet | 0.2% 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-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-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 No fix yet | 0.2% 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-2025-32728 | LOW1.94 | openssh 9.9p1-7.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-32728 | LOW1.94 | openssh-clients 9.9p1-7.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-32728 | LOW1.94 | openssh-server 9.9p1-7.el9 No fix yet | 0.1% 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 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.6% 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.2% Theoretical Threat | Post-Exploit |
| CVE-2025-9232 | LOW1.86 | openssl 1:3.5.5-1.el9 No fix yet | 2.0% Low-Moderate Risk | 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 | 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-2026-4519 | LOW1.68 | python3 3.9.25-5.el9 fixed in 3.9.25-7.el9_8 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-2297 | LOW1.68 | python3 3.9.25-5.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3479 | LOW1.68 | python3 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 | 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 3.9.25-5.el9 No fix yet | 0.6% 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 | 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-2026-35388 | LOW1.27 | openssh 9.9p1-7.el9 fixed in 9.9p1-7.el9_8 | 0.1% 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-35388 | LOW1.27 | openssh-server 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-23112 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-47685 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2026-23395 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-10263 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31788 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6100 | NONE0 | python3-devel 3.9.25-5.el9 fixed in 3.9.25-7.el9_8 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-50386 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-3534 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-45078 | NONE0 | binutils-gold 2.35.2-72.el9 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2025-11082 | NONE0 | binutils-gold 2.35.2-72.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-5245 | NONE0 | binutils-gold 2.35.2-72.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-7545 | NONE0 | binutils-gold 2.35.2-72.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-44840 | NONE0 | binutils-gold 2.35.2-72.el9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-52922 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53141 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-23185 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31474 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31488 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45998 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46189 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46323 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46331 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2021-34866 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2021-46999 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47017 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47103 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-47561 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-0500 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-23222 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2022-25265 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2022-3424 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48637 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48744 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48778 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48783 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48787 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48834 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-48837 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-48848 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48913 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48943 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48950 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-48951 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48981 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48990 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48991 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49006 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49014 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49015 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49017 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49029 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49062 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49377 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49384 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49410 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49455 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49471 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49508 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49548 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49581 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49720 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49779 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49840 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49892 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49900 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49921 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50142 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50220 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50305 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50315 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50320 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50328 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50401 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50411 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50419 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50422 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50433 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50552 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50630 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-1118 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52469 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52752 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52835 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52846 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52854 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52885 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52906 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52930 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53037 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53075 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53111 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53123 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53145 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53257 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53282 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53286 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53305 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53340 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53386 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53427 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53446 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53454 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53484 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53500 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53504 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53506 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53515 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53516 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53522 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53543 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53560 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53587 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53619 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53629 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53638 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53676 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53680 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-26598 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26689 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35868 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36921 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39494 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40900 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40903 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40935 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40956 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40974 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41045 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41069 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41087 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42148 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42285 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42302 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44932 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44964 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44967 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44974 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-44977 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-44985 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-44986 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44998 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-45026 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46673 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46725 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46736 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46738 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46744 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46746 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46759 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46766 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46786 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46796 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46798 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46800 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46830 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46859 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46871 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47682 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47696 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-47701 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47718 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47748 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49880 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49882 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49883 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49884 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49889 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49930 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49950 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49960 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49983 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49991 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50007 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50029 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50055 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50063 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50067 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50074 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50114 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50126 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50127 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50131 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50143 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50151 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50155 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50158 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50209 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50215 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50235 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50261 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50262 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50267 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50274 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50282 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53057 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53059 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53096 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53103 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53166 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53168 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53170 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53173 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53179 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53239 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-56600 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56604 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56605 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56609 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56615 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-56633 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-56638 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56640 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56642 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56658 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56675 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56765 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56772 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57798 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57849 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57951 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57980 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57995 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58069 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58072 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58093 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58240 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21631 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21671 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21692 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-21724 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21772 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21855 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21856 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21858 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21966 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21969 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21979 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23133 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23142 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37798 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37839 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37861 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37869 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37882 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37885 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37891 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37921 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37944 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37957 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38019 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38056 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38077 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38117 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38118 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38146 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38154 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38157 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38198 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38201 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38209 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38212 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38216 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38245 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38248 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38257 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38270 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38280 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38289 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38317 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38323 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38338 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38346 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38369 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38375 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38443 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38488 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-38494 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38512 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38552 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38574 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38584 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38593 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38618 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38676 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-38688 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38729 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39689 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39691 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39790 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39797 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39809 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39810 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39823 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39824 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39854 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39855 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39860 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39861 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39862 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39863 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39877 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39880 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39911 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39939 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39944 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39945 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39967 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40014 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40149 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71068 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71091 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71100 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71137 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71157 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71234 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71238 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-22980 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23013 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23025 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23078 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23208 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23223 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23319 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23343 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23359 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23412 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23413 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23415 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23447 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23448 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31399 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31452 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31455 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31485 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31493 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31500 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31527 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31530 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31583 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31686 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31688 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31729 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31731 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31759 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31776 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31787 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43049 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43120 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43150 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43260 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43276 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43328 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43440 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45996 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46004 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46045 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46047 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46162 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46180 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46234 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2021-46984 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47014 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47196 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47222 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47261 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47404 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47483 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47517 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47536 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47576 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47609 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47613 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47616 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48657 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48658 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48662 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48694 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48702 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48712 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48732 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48801 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49888 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49907 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49917 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49975 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50071 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50252 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50432 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-52452 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52455 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52464 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52468 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52764 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52795 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52818 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52851 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52987 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53082 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53142 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53153 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53179 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53215 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53307 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53426 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53604 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-54207 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-54285 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26742 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26883 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-36012 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36898 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36906 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38588 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38627 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-39480 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40994 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41000 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41003 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42136 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42138 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46845 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50130 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53214 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-56669 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56708 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57917 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21869 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37928 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-37981 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38239 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38385 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38535 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38563 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-38565 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39701 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39776 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39835 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39913 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39957 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39958 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39963 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40364 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71078 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71082 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71099 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71122 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23089 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31696 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% 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-udev 252-67.el9 fixed in 252-67.el9_8.2 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-66864 | NONE0 | binutils-gold 2.35.2-72.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-66866 | NONE0 | binutils-gold 2.35.2-72.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69649 | NONE0 | binutils-gold 2.35.2-72.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69650 | NONE0 | binutils-gold 2.35.2-72.el9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-50083 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2024-57791 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-31669 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-0045 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2026-0994 | NONE0 | protobuf-compiler 3.14.0-17.el9 fixed in 3.14.0-17.el9_7 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-3644 | NONE0 | python3-devel 3.9.25-5.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-4224 | NONE0 | python3-devel 3.9.25-5.el9 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-7210 | NONE0 | python3-devel 3.9.25-5.el9 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-43038 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46244 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-53781 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43074 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43078 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43248 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-4156 | NONE0 | gawk 5.1.0-6.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46033 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-4204 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2021-47097 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-48866 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49094 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49218 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49395 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49407 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49416 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49444 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49503 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49518 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49556 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49696 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49740 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49799 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49844 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49865 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49870 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49883 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49948 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50103 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50231 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50255 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50307 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50366 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50394 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50490 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50551 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-1380 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 16.8% High Exploitation Risk | Not Applicable |
| CVE-2023-1838 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-53259 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53272 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53600 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53659 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53668 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-0775 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36013 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-38606 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39487 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42094 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44983 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46722 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46723 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46724 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46743 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49860 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49928 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50033 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50035 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50042 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50128 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50164 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50250 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50268 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50278 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50279 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50301 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-52332 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53082 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53099 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53147 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53174 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56558 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57982 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58013 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58014 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58015 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21762 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21905 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21920 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21973 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21993 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37761 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37785 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37846 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37973 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38004 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38103 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38111 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38249 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38320 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38342 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38445 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38616 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38680 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39683 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39750 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39853 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39891 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39901 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39922 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68357 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71093 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71112 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71231 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23076 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23099 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23102 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23187 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23315 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23318 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23327 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23363 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23388 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23397 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31395 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31430 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31568 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31614 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31778 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43040 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43052 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43281 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43414 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43427 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43449 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43450 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43453 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46056 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46120 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46135 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46150 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46155 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46191 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46209 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46259 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2021-47089 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47191 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47226 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48714 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48757 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48760 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49623 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-50497 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-52519 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52598 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52794 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52842 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52866 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53265 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53357 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46774 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57838 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21719 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38502 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38521 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38636 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38728 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71133 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23244 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-4786 | NONE0 | python3-devel 3.9.25-5.el9 fixed in 3.9.25-7.el9_8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40186 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68287 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31663 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43198 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43329 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43503 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45898 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-45972 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-45984 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46054 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46090 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46099 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46116 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46117 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46125 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46145 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46152 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46166 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46176 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46227 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46309 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46316 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46319 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46330 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2021-4202 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-1247 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-48858 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48988 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49667 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-50082 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-1077 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52935 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52974 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52983 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38561 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42162 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42228 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43882 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49855 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50036 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50106 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50275 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56672 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-21761 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21764 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22004 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38051 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38102 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38107 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38108 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40199 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40216 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40259 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40328 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23050 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23454 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31539 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31586 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31694 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31772 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43050 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43233 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43304 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43332 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43334 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43339 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43491 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43493 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-45840 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45856 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45859 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-45861 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45886 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45892 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45894 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45899 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45910 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45912 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45942 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45959 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45970 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46015 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46043 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46052 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46069 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46076 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46084 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46114 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46119 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46121 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46132 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46133 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-46139 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46149 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46173 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46174 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46185 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46215 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46242 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46266 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46275 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46294 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46306 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46317 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46324 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46325 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-48689 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53622 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23054 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-44604 | NONE0 | rpm-build-libs 4.16.1.3-40.el9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-44604 | NONE0 | rpm-plugin-selinux 4.16.1.3-40.el9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-33656 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-40345 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45837 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-42739 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-43975 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-20153 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-49275 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49388 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49426 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-50616 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52975 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54102 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54110 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53095 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53177 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56678 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56693 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57795 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21714 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21731 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21739 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22097 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40257 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52447 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26828 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% 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-udev 252-67.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50851 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-5197 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-53729 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54168 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-0607 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40018 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40261 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31589 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-45991 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-3826 | NONE0 | binutils-gold 2.35.2-72.el9 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2023-1972 | NONE0 | binutils-gold 2.35.2-72.el9 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-4437 | NONE0 | glibc-devel 2.34-262.el9 fixed in 2.34-270.el9_8 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-6238 | NONE0 | glibc-devel 2.34-262.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-4437 | NONE0 | glibc-headers 2.34-262.el9 fixed in 2.34-270.el9_8 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-6238 | NONE0 | glibc-headers 2.34-262.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-68284 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2020-26140 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 2.9% Low-Moderate Risk | Not Applicable |
| CVE-2020-26144 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 4.9% Low-Moderate Risk | Not Applicable |
| CVE-2021-28711 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-28712 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-28713 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-50821 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53785 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54094 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47692 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2024-47693 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2024-50076 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-53135 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39969 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40061 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40273 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40336 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68354 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68380 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23179 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31470 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31588 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43239 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43447 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-0564 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.6% 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-45932 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2021-37159 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-47634 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-20154 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-49493 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49694 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50880 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54164 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-21823 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57979 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21700 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39978 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40074 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40091 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40309 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40321 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40350 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68371 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23178 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23383 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23450 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-23456 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31502 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31516 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31525 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43070 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-52886 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-20197 | NONE0 | binutils-gold 2.35.2-72.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42161 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40000 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40302 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40307 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40320 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68282 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31504 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31631 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-41012 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-5958 | NONE0 | sed 4.8-10.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50764 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50838 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50873 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54039 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54081 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54311 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50251 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-40048 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40132 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40146 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40147 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71066 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-4647 | NONE0 | binutils-gold 2.35.2-72.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50717 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68342 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68343 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49078 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53788 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53802 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53808 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53840 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53850 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42224 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40019 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40038 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40071 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40080 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40190 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40355 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68245 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68736 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68764 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68770 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68815 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31449 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31464 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31505 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31511 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31513 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31570 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31700 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31708 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43134 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43321 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2021-47313 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-48748 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2024-57874 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57878 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6019 | NONE0 | python3-devel 3.9.25-5.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-50181 | NONE0 | python3-pip-wheel 21.3.1-1.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-50182 | NONE0 | python3-pip-wheel 21.3.1-1.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47308 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2021-47378 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2022-49053 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49129 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49385 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49465 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-50621 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49570 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56662 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-40359 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31649 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-52481 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-5713 | NONE0 | python3-devel 3.9.25-5.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1153 | NONE0 | binutils-gold 2.35.2-72.el9 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2026-5435 | NONE0 | glibc-devel 2.34-262.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-5435 | NONE0 | glibc-headers 2.34-262.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-3714 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2022-50666 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50849 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-2312 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40083 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40242 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40324 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-32284 | NONE0 | python3-pip-wheel 21.3.1-1.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-49479 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53717 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54045 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54107 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54236 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54258 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39998 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40111 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40167 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40194 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40201 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40237 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40272 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40323 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40329 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40340 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68742 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23239 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23240 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-23271 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23317 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31392 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31414 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31426 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43279 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46065 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46113 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-49138 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-50651 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53240 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-40319 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46024 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-3572 | NONE0 | python3-pip-wheel 21.3.1-1.el9 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2023-53828 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54193 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68801 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68816 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48754 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11081 | NONE0 | binutils-gold 2.35.2-72.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6844 | NONE0 | binutils-gold 2.35.2-72.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-38533 | NONE0 | binutils-gold 2.35.2-72.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-47007 | NONE0 | binutils-gold 2.35.2-72.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-47008 | NONE0 | binutils-gold 2.35.2-72.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-47010 | NONE0 | binutils-gold 2.35.2-72.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-47011 | NONE0 | binutils-gold 2.35.2-72.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-11412 | NONE0 | binutils-gold 2.35.2-72.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11413 | NONE0 | binutils-gold 2.35.2-72.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11414 | NONE0 | binutils-gold 2.35.2-72.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11494 | NONE0 | binutils-gold 2.35.2-72.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11495 | NONE0 | binutils-gold 2.35.2-72.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11839 | NONE0 | binutils-gold 2.35.2-72.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-11840 | NONE0 | binutils-gold 2.35.2-72.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-3198 | NONE0 | binutils-gold 2.35.2-72.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69651 | NONE0 | binutils-gold 2.35.2-72.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-46195 | NONE0 | cpp 11.5.0-14.el9 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2022-27943 | NONE0 | cpp 11.5.0-14.el9 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2025-38001 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-38509 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40348 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68182 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68192 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68215 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68291 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68297 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68307 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2020-13844 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-34693 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-4135 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-46931 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47041 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47092 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47214 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47223 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47227 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47230 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47275 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47316 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47343 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47365 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47444 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47465 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47559 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47620 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47632 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47646 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47648 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47650 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47659 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-0171 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-26878 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-26966 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-2785 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-4543 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2022-48638 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48644 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48652 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48696 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48719 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-48773 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48780 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48781 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48785 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48793 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48797 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48799 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48802 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-48810 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48811 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-48819 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48831 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-48832 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48835 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48836 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48839 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-48840 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48844 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48849 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48850 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48853 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-48861 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48862 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48863 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48864 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48865 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-48875 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48876 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48879 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48886 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48889 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48914 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48915 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48938 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48946 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-48953 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48961 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48969 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-48971 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48972 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-48975 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48982 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48983 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-48984 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48986 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48987 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48994 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49011 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49012 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49013 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49021 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49048 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49052 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49060 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49061 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49074 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49076 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49077 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49082 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49087 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49092 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49096 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49100 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49110 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49118 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49123 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49130 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49132 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49134 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49148 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49154 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49159 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49171 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49174 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49176 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49179 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49182 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49187 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49190 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49198 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49208 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49216 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49219 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49231 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49236 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49237 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49262 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49266 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49269 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49279 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49294 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49296 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49307 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49314 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49316 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49321 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49323 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49329 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49332 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49341 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49349 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49357 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49370 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49371 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49389 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49390 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49400 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49403 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49404 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49406 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49408 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49412 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49419 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49420 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49437 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49441 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49446 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49450 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49456 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49468 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49472 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49474 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49475 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49481 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49486 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49492 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49497 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49521 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49523 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49526 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49534 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49535 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49536 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49542 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49567 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49583 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49611 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49613 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49615 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49616 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49617 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49620 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49624 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49626 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49627 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49643 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49644 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49647 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49651 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49656 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49657 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49658 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49662 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49664 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49670 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49671 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49672 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49679 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49700 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49715 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49716 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49728 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49743 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49750 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-49753 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49759 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-49764 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49776 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49780 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49783 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-49786 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-49791 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-49797 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49801 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49802 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49803 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49810 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-49812 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49819 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-49821 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49822 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49823 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49824 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49825 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49829 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-49832 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49836 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49837 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49838 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49845 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49847 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-49853 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49858 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-49860 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49863 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49866 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49867 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49871 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49876 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-49877 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49879 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49881 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49885 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49893 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-49894 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-49895 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-49901 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-49905 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49908 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49918 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49928 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-49929 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-49931 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-49932 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49963 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49972 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49987 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49989 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50008 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50043 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50059 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50060 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50065 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50098 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50118 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50130 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50144 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50167 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50174 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50186 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50222 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50233 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50266 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50267 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50280 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50282 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50314 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50321 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50323 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50334 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50370 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50375 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50380 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50382 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50409 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50414 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50428 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50430 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50435 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50438 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50461 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50476 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50493 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50498 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50553 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50582 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50642 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50709 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50731 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50746 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50871 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-2162 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-28327 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-3006 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31082 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-31085 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-4459 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-45862 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-5090 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52450 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52486 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52487 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52518 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52582 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52583 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52619 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52646 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52702 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52739 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52787 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52803 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52832 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2023-52869 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52901 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52908 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52910 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52912 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52920 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52931 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52932 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52973 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52992 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53008 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53016 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53026 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53032 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53041 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53062 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53080 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53101 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53109 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53118 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53133 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53144 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53147 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53189 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53199 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53200 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53201 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53225 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53226 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53240 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53251 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53277 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53295 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53302 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53315 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53326 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53327 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53347 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53360 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53382 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53438 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53450 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53457 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53463 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53475 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53480 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53481 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53488 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53491 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53509 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53514 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53526 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53528 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53529 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53535 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53540 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53567 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53574 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53589 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53601 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53627 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53639 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53667 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53682 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53684 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53698 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53721 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53765 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53783 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53800 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53806 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53822 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53987 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54012 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54013 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54016 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54040 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54052 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54150 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54280 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-7324 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-0443 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-0639 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-1151 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26637 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26666 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26682 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26683 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26708 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26771 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26772 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26779 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26785 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26816 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26851 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26889 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26902 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26918 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26991 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26999 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27031 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27039 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27056 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27077 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27413 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35803 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35878 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-35933 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35978 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-35980 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35999 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36011 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36021 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36286 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-36884 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36966 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36970 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-36975 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38598 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38612 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2024-39490 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39493 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-40937 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40965 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-40977 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-40980 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-40990 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41023 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41031 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41035 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41037 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41060 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41064 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41097 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42069 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42070 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42076 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42083 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42106 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42135 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42139 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42145 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42232 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42238 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42239 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42240 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42241 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42259 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42278 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42281 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42286 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42288 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42289 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42290 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42316 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42317 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43816 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43821 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43829 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43834 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43835 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-43853 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43861 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43871 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43874 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43880 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43889 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43896 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43906 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43908 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43912 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43914 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44931 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-44935 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44944 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44957 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44958 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44960 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44961 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44965 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44984 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44989 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44990 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44994 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44996 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-45000 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-45001 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-45006 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-45008 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-45009 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-45010 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-45013 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-45025 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46678 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46689 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46715 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46717 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46719 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46737 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46739 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46748 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46750 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46755 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46760 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46761 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46762 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46767 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46770 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46771 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46777 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46783 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46791 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46793 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46805 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46807 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46819 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46822 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46826 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46834 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46835 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46842 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46855 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46857 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46863 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47408 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47673 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47678 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47684 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-47687 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47700 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47703 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47705 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47706 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47707 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47710 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47713 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-47737 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-47739 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47749 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-48873 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-48876 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-49568 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49571 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49851 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49856 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49870 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49878 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49881 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49886 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49888 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49891 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49925 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49927 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49929 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49935 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49937 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49938 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49939 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49940 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49944 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49948 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49951 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49952 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49953 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49954 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49955 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49959 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49962 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49968 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49971 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49973 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49974 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49975 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49976 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49978 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49994 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50000 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50002 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50008 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50009 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50012 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50014 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50020 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50021 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50024 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50027 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50028 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50039 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50040 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50041 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50045 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50048 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50058 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50075 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50077 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50078 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50081 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50095 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50109 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50117 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50136 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50139 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50141 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50145 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50146 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50147 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50153 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50157 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50160 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50162 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50165 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50167 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50169 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50172 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50179 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50182 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50185 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50189 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50191 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50195 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50197 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50207 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-50208 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50223 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50236 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50237 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50255 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50256 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50258 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50259 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50271 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50272 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50299 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50303 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50304 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53042 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53044 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53045 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53048 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53050 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53055 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53060 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53066 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53070 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53073 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53074 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53079 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53090 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53091 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53093 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53109 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53110 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53114 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53117 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53118 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53119 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53121 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53123 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53134 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53138 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53140 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53144 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53146 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53167 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53185 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53194 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53195 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53196 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53207 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53209 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53219 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53236 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-54460 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-54683 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-55642 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56369 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56535 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56569 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56589 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56636 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-56647 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56648 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56654 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56667 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56677 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-56679 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56688 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56690 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56703 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56716 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56718 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56725 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56726 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56727 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56739 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56751 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56757 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56760 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56763 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56770 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-56779 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56783 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57793 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57875 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57882 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57890 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57924 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57932 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57938 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57946 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57948 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57977 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57981 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57985 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57986 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57988 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57989 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57996 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58005 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58017 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58053 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58057 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58061 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58062 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58064 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58071 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-58075 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58083 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58088 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58092 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58096 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58097 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58098 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-58100 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-58237 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-58238 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-58241 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21649 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21653 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21659 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21664 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21670 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21672 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21673 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21681 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21682 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21683 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21689 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21693 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21696 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21706 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21707 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21709 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21725 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21728 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21729 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21738 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21745 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21760 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 6.9% Low-Moderate Risk | Not Applicable |
| CVE-2025-21763 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21765 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21767 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21768 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21787 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21790 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21796 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21808 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21809 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21814 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21816 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21817 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21826 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21828 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21836 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21838 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21844 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21846 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21848 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21852 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21853 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21854 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21857 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21861 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21862 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21864 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21870 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21874 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21885 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21899 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21900 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21908 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21913 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21936 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21939 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21948 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21951 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21959 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21971 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21974 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21975 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21980 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21997 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22005 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22013 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22015 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22016 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22017 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22021 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22024 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22025 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22044 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22053 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-22057 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22062 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22063 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22065 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22075 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22077 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-22090 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22106 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22108 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-22124 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22125 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23131 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-23132 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-23134 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-23136 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23137 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23138 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23141 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23143 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23145 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23161 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-23163 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37745 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37747 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37757 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37773 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37791 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37800 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37807 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37808 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37809 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37811 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37813 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37820 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37824 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37829 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37830 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37834 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37836 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37842 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37843 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37844 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37848 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37857 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37859 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37860 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37862 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37873 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37875 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37876 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37877 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37878 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37883 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37884 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37888 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37889 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37912 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37918 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37919 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37922 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37933 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37940 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37948 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37949 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37954 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37959 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37960 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37961 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37963 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37967 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37974 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37978 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37986 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37989 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37990 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37992 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37995 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37997 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37998 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38003 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38014 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38017 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38018 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38023 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38029 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38031 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38035 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38036 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38038 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38040 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38044 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38047 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38055 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38057 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38058 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38060 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38061 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38062 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38063 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38064 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38066 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38067 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-38071 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38072 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38095 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38099 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38100 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38105 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38113 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38115 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38120 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38122 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38125 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38126 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38127 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38128 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38134 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38140 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38147 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38149 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38161 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38162 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38169 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38177 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38181 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38184 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38186 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38190 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38192 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38197 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38199 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38208 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38210 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38214 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38215 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38222 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38231 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38238 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38244 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38246 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38251 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38253 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38255 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38258 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38265 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38282 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38284 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38285 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38287 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38290 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38291 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38293 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38294 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38302 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38303 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38304 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38305 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38307 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38310 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38311 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38312 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38315 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38318 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38321 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38322 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38324 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38334 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38335 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38337 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38344 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38353 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38355 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38356 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38359 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38363 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38364 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38372 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38386 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38387 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38391 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38399 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38408 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38412 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38414 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38424 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38427 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38430 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38431 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38436 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38439 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38444 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38450 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38455 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38457 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38458 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38465 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38466 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38468 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38473 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38474 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38475 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38478 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38491 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38495 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38496 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38510 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38511 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38514 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38526 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38537 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38539 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38540 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38541 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38543 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38544 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38553 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38557 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38559 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38560 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38569 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38587 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38588 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38601 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38602 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38605 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38606 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38609 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38622 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38629 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38641 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38642 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38644 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38645 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38646 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38659 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38660 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38664 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38665 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38668 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38669 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38673 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38674 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38678 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38683 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38691 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38692 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38694 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38695 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38700 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38701 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38706 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38709 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38710 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38725 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38732 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38735 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39677 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39678 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39688 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39703 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39732 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39742 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39746 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39756 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39763 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39764 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39765 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39773 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39775 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39782 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39791 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39792 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39794 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39798 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39808 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39830 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39832 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39834 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39838 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39847 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39850 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39851 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39857 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39858 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39875 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39889 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39890 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39894 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39902 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39910 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39926 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39931 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39932 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39940 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39946 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 9.1% Low-Moderate Risk | Not Applicable |
| CVE-2025-39947 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39949 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39953 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39965 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39989 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40020 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40026 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40030 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40037 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40040 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40044 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40051 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40053 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40070 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40075 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40078 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40102 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40104 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40109 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40115 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40140 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40153 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40155 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40160 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40171 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40181 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40195 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40211 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40231 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40239 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40255 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40264 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40280 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40283 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40284 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40287 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40292 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40293 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40297 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40362 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40363 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68185 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68188 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68208 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68209 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68211 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68223 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68226 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68228 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68229 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68231 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68259 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68261 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68262 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68265 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68283 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68292 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68299 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68304 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68309 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68310 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68313 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68331 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68337 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68340 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68353 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68368 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68372 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68379 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68752 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68756 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68776 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68784 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68803 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68814 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71064 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71077 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71083 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71087 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71088 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71094 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71097 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71098 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71104 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71117 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71126 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71127 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71128 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71131 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71132 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71135 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71147 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71160 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71202 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71229 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71236 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71273 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71286 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71295 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71296 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71297 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71298 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71301 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71305 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-22976 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22977 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22981 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22985 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22989 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22991 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-22992 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-22993 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22996 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23000 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23003 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-23011 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23017 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23021 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23023 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23031 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23038 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23047 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23057 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23058 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23059 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23061 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23066 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23067 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23069 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23070 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23084 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23086 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23103 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23104 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23107 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23108 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23113 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23116 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23117 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23120 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23122 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23125 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23128 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23129 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23130 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23133 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23135 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23138 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23140 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23142 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23148 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-23151 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23164 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23166 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23173 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23186 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23196 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23200 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23202 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23230 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23241 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23242 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-23248 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23249 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23250 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23251 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23255 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23262 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23272 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23274 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23276 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23278 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23282 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23286 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23292 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23293 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23296 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23299 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23300 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23304 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23307 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23316 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23329 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23332 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23335 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23336 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23340 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23346 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23351 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23365 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23368 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23369 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23370 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23377 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23381 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23382 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23386 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23391 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23398 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23414 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23437 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23439 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23442 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23444 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23445 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23449 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23461 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23462 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-23466 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23467 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23472 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31394 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31400 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31403 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31404 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31407 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31411 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31415 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31416 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31421 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31422 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31423 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31424 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31427 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31435 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31436 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31438 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31440 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31441 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31442 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31443 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31446 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31447 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31448 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31450 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31451 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31453 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31454 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31458 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31468 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31469 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31473 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31479 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31480 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31482 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31483 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31487 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31492 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31495 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31496 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31498 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31499 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31503 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31507 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31510 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31512 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31515 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31518 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31519 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31521 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31526 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31528 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31531 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31533 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31542 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31543 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31546 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31548 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31551 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31554 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31555 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31557 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31565 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31574 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31575 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31579 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31590 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31591 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31592 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31593 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31600 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31604 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31609 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31619 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31624 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31625 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31628 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31630 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31632 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31633 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31634 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31637 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31638 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31642 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31647 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31648 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31661 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31662 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31665 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31666 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31667 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31672 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31673 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31674 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31675 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31676 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31678 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31679 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31680 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31681 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31682 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31691 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31692 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31693 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31698 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31699 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31701 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31719 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31738 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31739 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31742 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31752 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31758 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31767 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31771 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31773 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31774 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31775 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31777 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31779 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31781 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43009 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43012 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43013 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43016 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43017 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43018 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43019 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43021 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43022 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43024 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43025 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43026 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43028 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43033 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43034 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43035 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43042 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43043 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43048 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43054 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43055 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43059 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43060 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43061 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43062 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43063 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43064 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43065 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43067 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43071 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43079 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43080 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43084 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43085 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43088 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43089 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43091 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43093 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43094 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43095 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43099 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43107 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43109 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43111 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43112 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43114 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43119 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43124 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43129 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43132 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43133 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43136 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43137 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43139 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43140 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43143 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43144 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43152 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43153 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43156 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43157 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43161 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43169 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43170 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43171 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43172 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43176 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43180 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43187 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43199 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43201 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43204 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43213 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43214 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43215 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43216 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43234 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43238 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43240 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43251 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43261 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43266 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43267 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43273 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43277 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43278 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43280 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43287 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43288 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43292 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43296 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43315 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43323 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43325 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43333 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43346 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43350 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43351 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43362 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43363 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43365 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43366 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43374 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43394 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43395 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43396 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43401 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43402 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43405 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43406 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43407 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43408 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43409 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43411 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43413 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43416 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43420 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43429 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43436 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43437 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43441 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43443 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43445 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43452 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43456 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43459 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43463 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43466 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43468 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43469 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43472 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43473 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43475 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45834 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45835 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45836 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45838 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45841 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45842 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45843 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-45844 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45845 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45846 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45855 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45857 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45862 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45891 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45944 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45945 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45973 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45981 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45983 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45985 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45988 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46000 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46012 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46021 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46023 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46027 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46028 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46032 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46037 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46050 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46051 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46066 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46070 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46078 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46079 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46082 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46086 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46094 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46095 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46102 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46107 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46111 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46115 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46130 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46137 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46138 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46146 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46151 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46158 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46168 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46170 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46172 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46182 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46188 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46193 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46207 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46214 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46252 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46253 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46273 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46280 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46291 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46304 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46315 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46320 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46322 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2020-36782 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-20320 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-4454 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-45402 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-46904 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-46909 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-46910 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-46917 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-46918 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-46920 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-46923 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-46937 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47020 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47033 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47079 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47182 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47190 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47197 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47199 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47202 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47210 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47215 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47217 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47237 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47241 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2021-47250 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47266 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47272 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47325 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47349 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47360 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47373 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47380 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47398 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47420 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47422 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47426 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47438 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47455 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47481 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47490 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47499 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47504 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47516 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47527 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47537 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47538 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47539 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47550 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47558 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47578 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47582 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47601 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47607 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47617 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47622 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47623 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47639 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47657 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47671 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-2905 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-3344 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-3606 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-48628 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48635 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48639 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48640 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48641 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48643 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48660 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48673 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48675 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48690 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48691 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48697 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48704 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48705 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48706 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48707 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48709 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48710 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-48713 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48720 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48721 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48724 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48725 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48727 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48728 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48729 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48731 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48741 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48746 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48752 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48763 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48764 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48767 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48768 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48769 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48770 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48800 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48806 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-48809 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-48812 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-48813 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-48814 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-48815 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-48817 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-48818 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-48823 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-48825 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-48887 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48890 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48896 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48944 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48963 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48979 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49005 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49027 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49046 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49064 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49065 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49070 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49103 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49107 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49127 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49139 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49155 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49157 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49177 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49178 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49206 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49207 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49209 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49223 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49225 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49235 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49287 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49319 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49322 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49334 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49352 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49353 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49374 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49402 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49413 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49422 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49432 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49436 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49447 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49466 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49476 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49498 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49516 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49531 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49532 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49538 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49549 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49648 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49653 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49746 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49749 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49752 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49766 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-49769 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49772 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49782 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49784 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-49800 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49807 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-49813 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49817 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49830 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49835 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49841 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49848 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-49874 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49880 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49889 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49891 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49896 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-49906 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49915 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49949 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49955 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50012 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50025 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50045 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50104 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50108 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50134 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50170 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50176 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50197 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50218 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50230 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50232 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50244 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50249 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50250 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50253 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50278 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50304 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50311 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50331 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50332 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50337 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50349 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50351 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50352 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50365 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50387 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50395 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50424 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50434 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50466 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50481 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50500 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50521 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50537 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50561 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50562 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50566 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50577 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50618 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50646 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50648 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50650 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50654 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50655 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50658 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50667 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50669 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50679 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50719 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-50742 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50749 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50751 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50868 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50884 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-37454 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-52462 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52465 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52467 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52470 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52473 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52516 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52623 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52653 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52675 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52700 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52704 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52706 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52732 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52736 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52743 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52744 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52747 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52750 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52778 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52781 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52782 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52792 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52806 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52808 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52811 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52815 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52819 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52828 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52845 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52849 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52877 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52882 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52883 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-52887 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52936 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52937 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52938 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52941 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52942 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52982 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52993 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52994 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53002 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53005 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53007 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53011 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53013 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53015 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53017 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53018 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53048 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53049 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53055 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53069 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53074 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53091 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53093 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53115 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53127 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53128 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53131 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53165 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53167 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53174 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53190 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53234 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53242 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53250 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53271 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53279 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53290 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53313 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53332 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53341 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53344 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53369 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53375 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53378 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53411 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53419 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53449 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53456 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53460 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53467 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53474 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53482 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53498 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53518 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53523 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53548 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53557 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53571 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53588 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53593 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53603 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53610 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53631 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53648 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53685 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53712 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53728 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53754 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53790 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53793 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53798 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53818 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53823 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53826 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53830 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53836 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53847 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53852 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53858 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53859 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53866 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54046 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54051 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54056 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54087 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54099 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54134 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54189 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54190 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54223 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54288 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54305 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-7042 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-14027 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-25740 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26595 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26605 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26647 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26659 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26687 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26691 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26695 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26714 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26715 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26721 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26751 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26760 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26775 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26776 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26786 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26818 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26820 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26844 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26845 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26891 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26900 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26926 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-26945 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26950 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27059 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27073 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27393 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-35790 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35834 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35836 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35859 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35860 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35865 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35879 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35901 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35903 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35917 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35922 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35945 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35973 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-35974 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35981 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36004 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36007 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36008 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36489 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-36893 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36909 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36911 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36918 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36919 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36932 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36937 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36938 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36954 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36955 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36962 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38566 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38573 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2024-38594 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38600 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38607 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39468 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39473 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39483 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39509 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40908 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40964 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40992 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40997 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40999 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41004 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41047 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41063 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41066 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41068 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41072 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41084 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41098 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42063 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42067 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42068 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42071 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42073 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42080 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42085 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42097 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42098 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42109 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42126 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42129 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42151 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42237 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42243 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42244 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43098 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43817 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43840 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43863 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43890 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-43893 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-43894 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44947 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2024-45012 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-45017 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-45019 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-45027 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-45029 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46672 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46681 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46692 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46698 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46706 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46707 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46709 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46720 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46765 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46784 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46788 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46797 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46823 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46825 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46860 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46861 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46862 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47143 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47671 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47674 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47702 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47728 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47734 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47794 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47809 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49875 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50001 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50093 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50101 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50107 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50138 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50163 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50194 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50201 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50252 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53047 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53051 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53064 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53072 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53094 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53097 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53125 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53151 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53157 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53161 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53172 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53175 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53180 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53189 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53198 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53202 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53210 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53215 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53217 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53225 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53230 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53231 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53238 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53685 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-55881 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56372 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56531 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56532 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56533 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56545 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56549 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56583 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56584 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56587 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56588 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56592 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56593 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56594 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56613 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56617 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56624 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56625 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56629 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56632 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56641 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56657 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56659 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56668 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56681 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56696 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56698 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56701 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56702 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56707 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56710 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56712 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56714 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56715 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56720 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56728 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56742 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56745 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56747 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56748 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56752 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56756 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56773 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56782 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56787 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57804 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57807 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57883 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57914 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57933 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57936 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57952 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57973 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57993 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57994 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-57999 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58012 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58068 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58070 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-58074 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-58077 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58078 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58079 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58084 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58090 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21632 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21634 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21636 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21637 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21638 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21639 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21640 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21644 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21645 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21690 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21694 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21705 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21708 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21712 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21713 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21716 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21723 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21744 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21750 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21766 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21770 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21776 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21779 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21783 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21806 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21807 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21810 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21827 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21829 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21830 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21831 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21832 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21833 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21847 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21866 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21872 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21875 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21876 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21877 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21880 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21881 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21884 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21886 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21889 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21890 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21891 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21898 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21901 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21906 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21907 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21909 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21910 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21916 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21918 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21921 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21922 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21924 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21930 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21937 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21953 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21970 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21976 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21978 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21981 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21986 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21992 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21995 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21996 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22008 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22009 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22031 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22045 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22117 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22128 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23144 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23147 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23149 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23154 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23162 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37743 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37744 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37756 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37788 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37792 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37793 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37794 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37801 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37805 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37837 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37867 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37895 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37907 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37911 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37932 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37936 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37938 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37945 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37984 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38009 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38010 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38016 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38020 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38037 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38039 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38045 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38049 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38096 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38148 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38168 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38170 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38193 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38202 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38262 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38268 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38278 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38345 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38402 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38460 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38489 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38505 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38528 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38546 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38576 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38581 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38586 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38591 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38608 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38621 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38623 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38624 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38640 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38643 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38671 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38721 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38733 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39676 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39681 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39721 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39724 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39736 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39737 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39745 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39748 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39752 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39753 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39772 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39784 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39795 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39801 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39811 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39829 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39865 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39886 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39887 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39916 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39929 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39937 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39956 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39959 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39974 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39990 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40010 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40042 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40049 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40057 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40086 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40099 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40103 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40105 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40125 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40159 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40164 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40169 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40219 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40253 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40267 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40325 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40346 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40360 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68170 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68171 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68173 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68178 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68193 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68198 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68200 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68204 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68206 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68207 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68218 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68219 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68227 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68233 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68244 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68281 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68288 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68295 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68298 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68300 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68306 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68308 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68317 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68321 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68326 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68334 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68336 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68345 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68348 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68363 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68378 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68725 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68732 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68758 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68783 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68785 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68794 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68795 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68798 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68802 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68807 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68813 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68818 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68820 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68822 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71076 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71096 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71108 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71113 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71118 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71119 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71125 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71142 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71154 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71161 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71182 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71227 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71232 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71235 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71285 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71315 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-22979 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22994 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22997 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-23002 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23005 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23007 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23008 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23009 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23039 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23085 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23119 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23141 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23149 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23154 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23155 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23160 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23190 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23247 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23252 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23259 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23260 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23290 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23297 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23303 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23310 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23312 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23313 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23352 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23357 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23366 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23367 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23374 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23376 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23379 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23389 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23399 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23417 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23418 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23421 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23430 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23434 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23436 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23475 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31390 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31428 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31486 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31491 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31497 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31520 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31522 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31524 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31556 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31571 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31639 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31655 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31664 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31670 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31671 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31784 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43010 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43030 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43036 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43041 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43066 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43068 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43073 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43092 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43123 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43130 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43148 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43167 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43194 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43211 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43253 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43259 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43262 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43265 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43289 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43309 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43311 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43313 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43314 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43344 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43419 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43425 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43428 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43432 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43451 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43477 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43478 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43483 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43484 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43487 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43488 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43496 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45847 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45851 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45870 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45872 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45873 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45877 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45880 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45888 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45904 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45905 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45913 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45915 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45917 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45919 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45920 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45922 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45923 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45925 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45933 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45948 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45953 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45955 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45961 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45963 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45964 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45968 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45982 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45987 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45997 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46003 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46005 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46014 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46018 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46026 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46038 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46040 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46046 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46049 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46059 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46060 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46063 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46068 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46071 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46083 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46088 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46089 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46092 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46101 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46126 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46131 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46136 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46140 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46144 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46153 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46161 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46167 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46178 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46184 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46196 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46201 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46216 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46224 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46248 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46249 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46262 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46271 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46292 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46298 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46302 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46327 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-24056 | NONE0 | pkgconf 1.7.3-10.el9 No fix yet | 0.5% 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-2023-24056 | NONE0 | pkgconf-pkg-config 1.7.3-10.el9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-13837 | NONE0 | python3-devel 3.9.25-5.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-42308 | NONE0 | python3-devel 3.9.25-5.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-25645 | NONE0 | python3-pip-wheel 21.3.1-1.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2020-10135 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2026-4046 | NONE0 | glibc-devel 2.34-262.el9 fixed in 2.34-270.el9_8 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-4046 | NONE0 | glibc-headers 2.34-262.el9 fixed in 2.34-270.el9_8 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40204 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47238 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50774 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53713 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53726 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54243 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39968 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39972 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40353 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71225 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23053 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23457 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2020-26146 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 5.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-50755 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54181 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-4565 | NONE0 | protobuf-compiler 3.14.0-17.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-12781 | NONE0 | python3-devel 3.9.25-5.el9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-3276 | NONE0 | python3-devel 3.9.25-5.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-33430 | NONE0 | python3-numpy-f2py 1:1.23.5-2.el9 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2021-34141 | NONE0 | python3-numpy-f2py 1:1.23.5-2.el9 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2023-53841 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39970 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40217 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40330 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40338 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40343 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40344 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2020-36558 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-50852 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53843 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54226 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40178 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23035 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47327 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-54222 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-4516 | NONE0 | python3-devel 3.9.25-5.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6845 | NONE0 | binutils-gold 2.35.2-72.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-57360 | NONE0 | binutils-gold 2.35.2-72.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-5450 | NONE0 | glibc-devel 2.34-262.el9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-5928 | NONE0 | glibc-devel 2.34-262.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-5450 | NONE0 | glibc-headers 2.34-262.el9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-5928 | NONE0 | glibc-headers 2.34-262.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40121 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68197 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-3056 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-47441 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% 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-15282 | NONE0 | python3-devel 3.9.25-5.el9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-0672 | NONE0 | python3-devel 3.9.25-5.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-27672 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-48751 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48784 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48816 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-48830 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48899 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48931 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48985 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48989 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-49089 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49149 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49286 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49344 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49414 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49571 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49578 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49597 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49607 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49638 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49771 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-49781 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50373 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-52568 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52786 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52898 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52909 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53186 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53345 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53368 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53452 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53520 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53697 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53703 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53759 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53777 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53794 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53799 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53815 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53824 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53832 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53853 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54287 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26698 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42107 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44954 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-45003 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46679 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46787 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47660 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47668 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47679 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49864 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50006 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50010 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50135 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50183 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50277 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50294 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53088 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53100 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53124 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53136 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53169 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53178 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56637 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56729 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57974 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21732 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21892 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21938 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-22050 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37985 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38008 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38048 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38078 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38083 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38112 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38232 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38234 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38440 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38462 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38477 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38524 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38617 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-38632 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38681 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39673 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39713 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39726 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39754 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39927 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39961 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39977 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39980 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39992 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40011 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40016 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40056 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40085 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40110 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40120 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40129 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40139 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40179 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40187 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40197 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40215 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40220 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40238 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40250 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40252 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40254 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40331 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40342 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68239 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68241 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68296 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68312 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68745 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23004 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23071 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23126 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23207 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23212 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23348 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23440 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23441 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23452 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31389 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31393 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31456 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31523 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31535 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31572 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31697 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43047 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43053 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43383 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43448 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45949 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46017 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48745 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49152 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49443 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49554 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49587 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49633 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50259 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50697 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52478 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53020 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-54007 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54042 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54128 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-23196 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-24855 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26631 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26859 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26862 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26915 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36949 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42253 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42287 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46710 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49866 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50082 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56568 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21651 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21701 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21825 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21895 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-23151 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37920 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39813 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39991 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40357 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68181 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68214 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68264 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68373 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68374 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71111 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23101 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23110 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23118 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23275 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23302 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31466 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43439 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2024-49934 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31620 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-3903 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-40166 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40308 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68242 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68360 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53831 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11468 | NONE0 | python3-devel 3.9.25-5.el9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-0865 | NONE0 | python3-devel 3.9.25-5.el9 fixed in 3.9.25-5.el9_8 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-1502 | NONE0 | python3-devel 3.9.25-5.el9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-47449 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49196 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49288 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-50579 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-2019 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52508 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53733 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53811 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-7192 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26810 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38541 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2024-38559 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42114 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42123 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53052 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40081 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40206 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40281 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68768 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2020-14304 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-48761 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52735 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2023-52738 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2023-52798 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-52800 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52801 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-52884 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53718 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54086 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54209 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54210 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54247 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26648 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26661 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26662 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26672 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26712 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26758 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26769 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26854 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-26857 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26890 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-36030 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36031 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-36910 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38384 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38388 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38605 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2024-42230 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40021 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40123 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40157 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40183 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40198 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40200 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23032 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23458 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31401 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-54213 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39920 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-47233 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40275 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50358 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-45803 | NONE0 | python3-pip-wheel 21.3.1-1.el9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-1974 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50558 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52872 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53720 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54295 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42229 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40173 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40218 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2019-16089 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-4438 | NONE0 | glibc-devel 2.34-262.el9 fixed in 2.34-270.el9_8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-4438 | NONE0 | glibc-headers 2.34-262.el9 fixed in 2.34-270.el9_8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50853 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53695 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53708 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53994 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40162 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53715 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-1152 | NONE0 | binutils-gold 2.35.2-72.el9 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2020-35501 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68740 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-66861 | NONE0 | binutils-gold 2.35.2-72.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-66862 | NONE0 | binutils-gold 2.35.2-72.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-66863 | NONE0 | binutils-gold 2.35.2-72.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-66865 | NONE0 | binutils-gold 2.35.2-72.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69647 | NONE0 | binutils-gold 2.35.2-72.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69648 | NONE0 | binutils-gold 2.35.2-72.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69652 | NONE0 | binutils-gold 2.35.2-72.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68191 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41007 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47738 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50057 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39964 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23045 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-46934 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47430 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-3629 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-3633 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-48939 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50575 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50706 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50827 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50850 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50859 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50887 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-1513 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52926 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53998 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54058 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54116 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54171 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54177 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54211 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54218 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54220 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54252 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54315 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26612 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46794 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50044 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50211 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50280 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21851 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40035 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40268 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40341 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68744 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68746 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68751 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68775 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68782 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71148 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71224 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23261 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31668 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-4519 | NONE0 | python3-devel 3.9.25-5.el9 fixed in 3.9.25-7.el9_8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-2297 | NONE0 | python3-devel 3.9.25-5.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-3479 | NONE0 | python3-devel 3.9.25-5.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-1150 | NONE0 | binutils-gold 2.35.2-72.el9 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1151 | NONE0 | binutils-gold 2.35.2-72.el9 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1795 | NONE0 | python3-devel 3.9.25-5.el9 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-69644 | NONE0 | binutils-gold 2.35.2-72.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69645 | NONE0 | binutils-gold 2.35.2-72.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69646 | NONE0 | binutils-gold 2.35.2-72.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50665 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50870 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68788 | NONE0 | kernel-headers 5.14.0-688.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-42504 | NONE0 | stdlib v1.26.3 fixed in 1.25.11, 1.26.4 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-27145 | NONE0 | stdlib v1.26.3 fixed in 1.25.11, 1.26.4 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-42507 | NONE0 | stdlib v1.26.3 fixed in 1.25.11, 1.26.4 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39823 | NONE0 | stdlib v1.22.10 fixed in 1.25.10, 1.26.3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39825 | NONE0 | stdlib v1.22.10 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-42499 | NONE0 | stdlib v1.22.10 fixed in 1.25.10, 1.26.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-42504 | NONE0 | stdlib v1.22.10 fixed in 1.25.11, 1.26.4 | 0.4% 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 |
| CVE-2026-27145 | NONE0 | stdlib v1.22.10 fixed in 1.25.11, 1.26.4 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-42507 | NONE0 | stdlib v1.22.10 fixed in 1.25.11, 1.26.4 | 0.3% Theoretical Threat | Not Applicable |