RHSA-2022:1619: Important: kpatch-patch security update
Published Apr 27, 2022
·Updated
This is a kernel live patch module which is automatically loaded by the RPM post-install script to modify the code of a running kernel.<br>Security Fix(es):<br><li> kernel: remote stack overflow via kernel panic on systems using TIPC may lead to DoS (CVE-2022-0435)</li> For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
Affected Software
70 affected componentsFixes available
redhat/kpatch-patch<4_18_0-147_48_1-1-8.el8_1
4_18_0-147_48_1-1-8.el8_1
redhat/kpatch-patch<4_18_0-147_51_1-1-7.el8_1
4_18_0-147_51_1-1-7.el8_1
redhat/kpatch-patch<4_18_0-147_51_2-1-6.el8_1
4_18_0-147_51_2-1-6.el8_1
redhat/kpatch-patch<4_18_0-147_52_1-1-5.el8_1
4_18_0-147_52_1-1-5.el8_1
redhat/kpatch-patch<4_18_0-147_54_2-1-4.el8_1
4_18_0-147_54_2-1-4.el8_1
redhat/kpatch-patch<4_18_0-147_56_1-1-4.el8_1
4_18_0-147_56_1-1-4.el8_1
redhat/kpatch-patch<4_18_0-147_57_1-1-3.el8_1
4_18_0-147_57_1-1-3.el8_1
redhat/kpatch-patch<4_18_0-147_58_1-1-2.el8_1
4_18_0-147_58_1-1-2.el8_1
redhat/kpatch-patch<4_18_0-147_59_1-1-2.el8_1
4_18_0-147_59_1-1-2.el8_1
redhat/kpatch-patch<4_18_0-147_64_1-1-1.el8_1
4_18_0-147_64_1-1-1.el8_1
redhat/kpatch-patch<4_18_0-147_48_1-1-8.el8_1
4_18_0-147_48_1-1-8.el8_1
redhat/kpatch-patch<4_18_0-147_48_1-debuginfo-1-8.el8_1
4_18_0-147_48_1-debuginfo-1-8.el8_1
redhat/kpatch-patch<4_18_0-147_48_1-debugsource-1-8.el8_1
4_18_0-147_48_1-debugsource-1-8.el8_1
redhat/kpatch-patch<4_18_0-147_51_1-1-7.el8_1
4_18_0-147_51_1-1-7.el8_1
redhat/kpatch-patch<4_18_0-147_51_1-debuginfo-1-7.el8_1
4_18_0-147_51_1-debuginfo-1-7.el8_1
redhat/kpatch-patch<4_18_0-147_51_1-debugsource-1-7.el8_1
4_18_0-147_51_1-debugsource-1-7.el8_1
redhat/kpatch-patch<4_18_0-147_51_2-1-6.el8_1
4_18_0-147_51_2-1-6.el8_1
redhat/kpatch-patch<4_18_0-147_51_2-debuginfo-1-6.el8_1
4_18_0-147_51_2-debuginfo-1-6.el8_1
redhat/kpatch-patch<4_18_0-147_51_2-debugsource-1-6.el8_1
4_18_0-147_51_2-debugsource-1-6.el8_1
redhat/kpatch-patch<4_18_0-147_52_1-1-5.el8_1
4_18_0-147_52_1-1-5.el8_1
redhat/kpatch-patch<4_18_0-147_52_1-debuginfo-1-5.el8_1
4_18_0-147_52_1-debuginfo-1-5.el8_1
redhat/kpatch-patch<4_18_0-147_52_1-debugsource-1-5.el8_1
4_18_0-147_52_1-debugsource-1-5.el8_1
redhat/kpatch-patch<4_18_0-147_54_2-1-4.el8_1
4_18_0-147_54_2-1-4.el8_1
redhat/kpatch-patch<4_18_0-147_54_2-debuginfo-1-4.el8_1
4_18_0-147_54_2-debuginfo-1-4.el8_1
redhat/kpatch-patch<4_18_0-147_54_2-debugsource-1-4.el8_1
4_18_0-147_54_2-debugsource-1-4.el8_1
redhat/kpatch-patch<4_18_0-147_56_1-1-4.el8_1
4_18_0-147_56_1-1-4.el8_1
redhat/kpatch-patch<4_18_0-147_56_1-debuginfo-1-4.el8_1
4_18_0-147_56_1-debuginfo-1-4.el8_1
redhat/kpatch-patch<4_18_0-147_56_1-debugsource-1-4.el8_1
4_18_0-147_56_1-debugsource-1-4.el8_1
redhat/kpatch-patch<4_18_0-147_57_1-1-3.el8_1
4_18_0-147_57_1-1-3.el8_1
redhat/kpatch-patch<4_18_0-147_57_1-debuginfo-1-3.el8_1
4_18_0-147_57_1-debuginfo-1-3.el8_1
redhat/kpatch-patch<4_18_0-147_57_1-debugsource-1-3.el8_1
4_18_0-147_57_1-debugsource-1-3.el8_1
redhat/kpatch-patch<4_18_0-147_58_1-1-2.el8_1
4_18_0-147_58_1-1-2.el8_1
redhat/kpatch-patch<4_18_0-147_58_1-debuginfo-1-2.el8_1
4_18_0-147_58_1-debuginfo-1-2.el8_1
redhat/kpatch-patch<4_18_0-147_58_1-debugsource-1-2.el8_1
4_18_0-147_58_1-debugsource-1-2.el8_1
redhat/kpatch-patch<4_18_0-147_59_1-1-2.el8_1
4_18_0-147_59_1-1-2.el8_1
redhat/kpatch-patch<4_18_0-147_59_1-debuginfo-1-2.el8_1
4_18_0-147_59_1-debuginfo-1-2.el8_1
redhat/kpatch-patch<4_18_0-147_59_1-debugsource-1-2.el8_1
4_18_0-147_59_1-debugsource-1-2.el8_1
redhat/kpatch-patch<4_18_0-147_64_1-1-1.el8_1
4_18_0-147_64_1-1-1.el8_1
redhat/kpatch-patch<4_18_0-147_64_1-debuginfo-1-1.el8_1
4_18_0-147_64_1-debuginfo-1-1.el8_1
redhat/kpatch-patch<4_18_0-147_64_1-debugsource-1-1.el8_1
4_18_0-147_64_1-debugsource-1-1.el8_1
redhat/kpatch-patch<4_18_0-147_48_1-1-8.el8_1
4_18_0-147_48_1-1-8.el8_1
redhat/kpatch-patch<4_18_0-147_48_1-debuginfo-1-8.el8_1
4_18_0-147_48_1-debuginfo-1-8.el8_1
redhat/kpatch-patch<4_18_0-147_48_1-debugsource-1-8.el8_1
4_18_0-147_48_1-debugsource-1-8.el8_1
redhat/kpatch-patch<4_18_0-147_51_1-1-7.el8_1
4_18_0-147_51_1-1-7.el8_1
redhat/kpatch-patch<4_18_0-147_51_1-debuginfo-1-7.el8_1
4_18_0-147_51_1-debuginfo-1-7.el8_1
redhat/kpatch-patch<4_18_0-147_51_1-debugsource-1-7.el8_1
4_18_0-147_51_1-debugsource-1-7.el8_1
redhat/kpatch-patch<4_18_0-147_51_2-1-6.el8_1
4_18_0-147_51_2-1-6.el8_1
redhat/kpatch-patch<4_18_0-147_51_2-debuginfo-1-6.el8_1
4_18_0-147_51_2-debuginfo-1-6.el8_1
redhat/kpatch-patch<4_18_0-147_51_2-debugsource-1-6.el8_1
4_18_0-147_51_2-debugsource-1-6.el8_1
redhat/kpatch-patch<4_18_0-147_52_1-1-5.el8_1
4_18_0-147_52_1-1-5.el8_1
redhat/kpatch-patch<4_18_0-147_52_1-debuginfo-1-5.el8_1
4_18_0-147_52_1-debuginfo-1-5.el8_1
redhat/kpatch-patch<4_18_0-147_52_1-debugsource-1-5.el8_1
4_18_0-147_52_1-debugsource-1-5.el8_1
redhat/kpatch-patch<4_18_0-147_54_2-1-4.el8_1
4_18_0-147_54_2-1-4.el8_1
redhat/kpatch-patch<4_18_0-147_54_2-debuginfo-1-4.el8_1
4_18_0-147_54_2-debuginfo-1-4.el8_1
redhat/kpatch-patch<4_18_0-147_54_2-debugsource-1-4.el8_1
4_18_0-147_54_2-debugsource-1-4.el8_1
redhat/kpatch-patch<4_18_0-147_56_1-1-4.el8_1
4_18_0-147_56_1-1-4.el8_1
redhat/kpatch-patch<4_18_0-147_56_1-debuginfo-1-4.el8_1
4_18_0-147_56_1-debuginfo-1-4.el8_1
redhat/kpatch-patch<4_18_0-147_56_1-debugsource-1-4.el8_1
4_18_0-147_56_1-debugsource-1-4.el8_1
redhat/kpatch-patch<4_18_0-147_57_1-1-3.el8_1
4_18_0-147_57_1-1-3.el8_1
redhat/kpatch-patch<4_18_0-147_57_1-debuginfo-1-3.el8_1
4_18_0-147_57_1-debuginfo-1-3.el8_1
redhat/kpatch-patch<4_18_0-147_57_1-debugsource-1-3.el8_1
4_18_0-147_57_1-debugsource-1-3.el8_1
redhat/kpatch-patch<4_18_0-147_58_1-1-2.el8_1
4_18_0-147_58_1-1-2.el8_1
redhat/kpatch-patch<4_18_0-147_58_1-debuginfo-1-2.el8_1
4_18_0-147_58_1-debuginfo-1-2.el8_1
redhat/kpatch-patch<4_18_0-147_58_1-debugsource-1-2.el8_1
4_18_0-147_58_1-debugsource-1-2.el8_1
redhat/kpatch-patch<4_18_0-147_59_1-1-2.el8_1
4_18_0-147_59_1-1-2.el8_1
redhat/kpatch-patch<4_18_0-147_59_1-debuginfo-1-2.el8_1
4_18_0-147_59_1-debuginfo-1-2.el8_1
redhat/kpatch-patch<4_18_0-147_59_1-debugsource-1-2.el8_1
4_18_0-147_59_1-debugsource-1-2.el8_1
redhat/kpatch-patch<4_18_0-147_64_1-1-1.el8_1
4_18_0-147_64_1-1-1.el8_1
redhat/kpatch-patch<4_18_0-147_64_1-debuginfo-1-1.el8_1
4_18_0-147_64_1-debuginfo-1-1.el8_1
redhat/kpatch-patch<4_18_0-147_64_1-debugsource-1-1.el8_1
4_18_0-147_64_1-debugsource-1-1.el8_1
Remediation
Event History
May 19, 2024
Advisory Published
via Red Hat·11:07 AM
Frequently Asked Questions
1
What is the severity of RHSA-2022:1619?
The severity of RHSA-2022:1619 is categorized as important due to the potential for remote stack overflow leading to Denial of Service (DoS).
2
How do I fix RHSA-2022:1619?
To fix RHSA-2022:1619, you should update the kpatch-patch package to the latest recommended version available for your system.
3
What systems are affected by RHSA-2022:1619?
RHSA-2022:1619 affects systems running specific versions of the kpatch-patch package in Red Hat Enterprise Linux 8.
4
What is the primary vulnerability associated with RHSA-2022:1619?
The primary vulnerability associated with RHSA-2022:1619 is CVE-2022-0435, which involves a remote stack overflow that could lead to a Denial of Service.
5
How can I determine if my system is vulnerable to RHSA-2022:1619?
You can determine if your system is vulnerable by checking the installed version of the kpatch-patch package and comparing it to the patched versions listed in the advisory.