Advisory Published
Advisory Published

RHSA-2022:1619: Important: kpatch-patch security update

First published: Wed 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 SoftwareAffected VersionHow to fix
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

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Frequently Asked Questions

  • 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).

  • 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.

  • 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.

  • 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.

  • 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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203