Tracker / CVE-2022-0435
CVE-2022-0435
High 8.8
A stack overflow flaw was found in the Linux kernel's TIPC protocol functionality in the way a user sends a packet with malicious content where the number of domain member nodes is higher than the 64 allowed. This flaw allows a remote user to crash the system or possibly escalate their privileges if they have access to the TIPC network.
Affected products and versions
| fedoraproject | fedora |
|---|---|
| linux | linux_kernel |
| linux | linux_kernel · 4.10 → 4.14.266 |
| linux | linux_kernel · 4.15 → 4.19.229 |
| linux | linux_kernel · 4.20 → 5.4.179 |
| linux | linux_kernel · 4.8 → 4.9.301 |
| linux | linux_kernel · 5.11 → 5.15.23 |
| linux | linux_kernel · 5.16 → 5.16.9 |
| linux | linux_kernel · 5.5 → 5.10.100 |
| netapp | h300e_firmware |
| netapp | h300s_firmware |
| netapp | h410s_firmware |
| netapp | h500e_firmware |
| netapp | h500s_firmware |
| netapp | h700e_firmware |
| netapp | h700s_firmware |
| ovirt | node |
| redhat | codeready_linux_builder |
| redhat | codeready_linux_builder_eus |
| redhat | codeready_linux_builder_eus_for_power_little_endian |
| redhat | codeready_linux_builder_for_power_little_endian_eus |
| redhat | enterprise_linux |
| redhat | enterprise_linux_eus |
| redhat | enterprise_linux_for_ibm_z_systems |
| redhat | enterprise_linux_for_ibm_z_systems_eus |
| redhat | enterprise_linux_for_power_little_endian |
| redhat | enterprise_linux_for_power_little_endian_eus |
| redhat | enterprise_linux_for_real_time |
| redhat | enterprise_linux_for_real_time_for_nfv |
| redhat | enterprise_linux_for_real_time_for_nfv_tus |
| redhat | enterprise_linux_for_real_time_tus |
| redhat | enterprise_linux_server_aus |
| redhat | enterprise_linux_server_for_power_little_endian_update_services_for_sap_solutions |
| redhat | enterprise_linux_server_tus |
| redhat | enterprise_linux_server_update_services_for_sap_solutions |
| redhat | virtualization |
| redhat | virtualization_host |
Analysis
This page is not indexable yet.Until it carries original analysis — what it actually exposes, how to check in two minutes whether a system was touched, what to do if it was — the page stays noindex. The database decides that, not the template.