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

Published Oct 18, 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.Security Fix(es): a use-after-free in clsroute filter implementation may lead to privilege escalation (CVE-2022-2588) 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

35 affected componentsFixes available
redhat/kpatch-patch<4_18_0-305_25_1-1-9.el8_4
4_18_0-305_25_1-1-9.el8_4
redhat/kpatch-patch<4_18_0-305_45_1-1-3.el8_4
4_18_0-305_45_1-1-3.el8_4
redhat/kpatch-patch<4_18_0-305_49_1-1-2.el8_4
4_18_0-305_49_1-1-2.el8_4
redhat/kpatch-patch<4_18_0-305_57_1-1-1.el8_4
4_18_0-305_57_1-1-1.el8_4
redhat/kpatch-patch<4_18_0-305_62_1-1-1.el8_4
4_18_0-305_62_1-1-1.el8_4
redhat/kpatch-patch<4_18_0-305_25_1-1-9.el8_4
4_18_0-305_25_1-1-9.el8_4
redhat/kpatch-patch<4_18_0-305_25_1-debuginfo-1-9.el8_4
4_18_0-305_25_1-debuginfo-1-9.el8_4
redhat/kpatch-patch<4_18_0-305_25_1-debugsource-1-9.el8_4
4_18_0-305_25_1-debugsource-1-9.el8_4
redhat/kpatch-patch<4_18_0-305_45_1-1-3.el8_4
4_18_0-305_45_1-1-3.el8_4
redhat/kpatch-patch<4_18_0-305_45_1-debuginfo-1-3.el8_4
4_18_0-305_45_1-debuginfo-1-3.el8_4
redhat/kpatch-patch<4_18_0-305_45_1-debugsource-1-3.el8_4
4_18_0-305_45_1-debugsource-1-3.el8_4
redhat/kpatch-patch<4_18_0-305_49_1-1-2.el8_4
4_18_0-305_49_1-1-2.el8_4
redhat/kpatch-patch<4_18_0-305_49_1-debuginfo-1-2.el8_4
4_18_0-305_49_1-debuginfo-1-2.el8_4
redhat/kpatch-patch<4_18_0-305_49_1-debugsource-1-2.el8_4
4_18_0-305_49_1-debugsource-1-2.el8_4
redhat/kpatch-patch<4_18_0-305_57_1-1-1.el8_4
4_18_0-305_57_1-1-1.el8_4
redhat/kpatch-patch<4_18_0-305_57_1-debuginfo-1-1.el8_4
4_18_0-305_57_1-debuginfo-1-1.el8_4
redhat/kpatch-patch<4_18_0-305_57_1-debugsource-1-1.el8_4
4_18_0-305_57_1-debugsource-1-1.el8_4
redhat/kpatch-patch<4_18_0-305_62_1-1-1.el8_4
4_18_0-305_62_1-1-1.el8_4
redhat/kpatch-patch<4_18_0-305_62_1-debuginfo-1-1.el8_4
4_18_0-305_62_1-debuginfo-1-1.el8_4
redhat/kpatch-patch<4_18_0-305_62_1-debugsource-1-1.el8_4
4_18_0-305_62_1-debugsource-1-1.el8_4
redhat/kpatch-patch<4_18_0-305_25_1-1-9.el8_4
4_18_0-305_25_1-1-9.el8_4
redhat/kpatch-patch<4_18_0-305_25_1-debuginfo-1-9.el8_4
4_18_0-305_25_1-debuginfo-1-9.el8_4
redhat/kpatch-patch<4_18_0-305_25_1-debugsource-1-9.el8_4
4_18_0-305_25_1-debugsource-1-9.el8_4
redhat/kpatch-patch<4_18_0-305_45_1-1-3.el8_4
4_18_0-305_45_1-1-3.el8_4
redhat/kpatch-patch<4_18_0-305_45_1-debuginfo-1-3.el8_4
4_18_0-305_45_1-debuginfo-1-3.el8_4
redhat/kpatch-patch<4_18_0-305_45_1-debugsource-1-3.el8_4
4_18_0-305_45_1-debugsource-1-3.el8_4
redhat/kpatch-patch<4_18_0-305_49_1-1-2.el8_4
4_18_0-305_49_1-1-2.el8_4
redhat/kpatch-patch<4_18_0-305_49_1-debuginfo-1-2.el8_4
4_18_0-305_49_1-debuginfo-1-2.el8_4
redhat/kpatch-patch<4_18_0-305_49_1-debugsource-1-2.el8_4
4_18_0-305_49_1-debugsource-1-2.el8_4
redhat/kpatch-patch<4_18_0-305_57_1-1-1.el8_4
4_18_0-305_57_1-1-1.el8_4
redhat/kpatch-patch<4_18_0-305_57_1-debuginfo-1-1.el8_4
4_18_0-305_57_1-debuginfo-1-1.el8_4
redhat/kpatch-patch<4_18_0-305_57_1-debugsource-1-1.el8_4
4_18_0-305_57_1-debugsource-1-1.el8_4
redhat/kpatch-patch<4_18_0-305_62_1-1-1.el8_4
4_18_0-305_62_1-1-1.el8_4
redhat/kpatch-patch<4_18_0-305_62_1-debuginfo-1-1.el8_4
4_18_0-305_62_1-debuginfo-1-1.el8_4
redhat/kpatch-patch<4_18_0-305_62_1-debugsource-1-1.el8_4
4_18_0-305_62_1-debugsource-1-1.el8_4

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade redhat/kpatch-patch to a version that resolves this vulnerability.

    Fixed in 4_18_0-305_25_1-1-9.el8_4
  2. Upgrade

    Upgrade redhat/kpatch-patch to a version that resolves this vulnerability.

    Fixed in 4_18_0-305_45_1-1-3.el8_4
  3. Upgrade

    Upgrade redhat/kpatch-patch to a version that resolves this vulnerability.

    Fixed in 4_18_0-305_49_1-1-2.el8_4
  4. Upgrade

    Upgrade redhat/kpatch-patch to a version that resolves this vulnerability.

    Fixed in 4_18_0-305_57_1-1-1.el8_4
  5. Upgrade

    Upgrade redhat/kpatch-patch to a version that resolves this vulnerability.

    Fixed in 4_18_0-305_62_1-1-1.el8_4
  6. Upgrade

    Upgrade redhat/kpatch-patch to a version that resolves this vulnerability.

    Fixed in 4_18_0-305_25_1-debuginfo-1-9.el8_4
  7. Upgrade

    Upgrade redhat/kpatch-patch to a version that resolves this vulnerability.

    Fixed in 4_18_0-305_25_1-debugsource-1-9.el8_4
  8. Upgrade

    Upgrade redhat/kpatch-patch to a version that resolves this vulnerability.

    Fixed in 4_18_0-305_45_1-debuginfo-1-3.el8_4
  9. Upgrade

    Upgrade redhat/kpatch-patch to a version that resolves this vulnerability.

    Fixed in 4_18_0-305_45_1-debugsource-1-3.el8_4
  10. Upgrade

    Upgrade redhat/kpatch-patch to a version that resolves this vulnerability.

    Fixed in 4_18_0-305_49_1-debuginfo-1-2.el8_4
  11. Upgrade

    Upgrade redhat/kpatch-patch to a version that resolves this vulnerability.

    Fixed in 4_18_0-305_49_1-debugsource-1-2.el8_4
  12. Upgrade

    Upgrade redhat/kpatch-patch to a version that resolves this vulnerability.

    Fixed in 4_18_0-305_57_1-debuginfo-1-1.el8_4
  13. Upgrade

    Upgrade redhat/kpatch-patch to a version that resolves this vulnerability.

    Fixed in 4_18_0-305_57_1-debugsource-1-1.el8_4
  14. Upgrade

    Upgrade redhat/kpatch-patch to a version that resolves this vulnerability.

    Fixed in 4_18_0-305_62_1-debuginfo-1-1.el8_4
  15. Upgrade

    Upgrade redhat/kpatch-patch to a version that resolves this vulnerability.

    Fixed in 4_18_0-305_62_1-debugsource-1-1.el8_4
  16. Compensating control

    Apply the kpatch-patch security update so the kpatch live patch module is automatically loaded (via RPM post-install) to address the kernel use-after-free in the cls_route filter implementation that could lead to privilege escalation (CVE-2022-2588).

Event History

Jun 4, 2026
Advisory Published
via Red Hat·10:50 PM
Data Sourced
via Red Hat·10:50 PM
RemedyDescriptionAffected Software

Frequently Asked Questions

1

What is the severity of RHSA-2022:6978?

The severity of RHSA-2022:6978 is rated as important.

2

How do I fix RHSA-2022:6978?

To fix RHSA-2022:6978, you should update to kpatch-patch versions 4_18_0-305_25_1-1-9.el8_4 or later.

3

What vulnerability does RHSA-2022:6978 address?

RHSA-2022:6978 addresses a use-after-free vulnerability in the cls_route filter implementation, which may lead to privilege escalation.

4

Which systems are impacted by RHSA-2022:6978?

RHSA-2022:6978 impacts systems running the affected versions of the kpatch-patch package.

5

Is there an alternative to applying the RHSA-2022:6978 update?

Applying the update for RHSA-2022:6978 is strongly recommended as it's the only effective way to mitigate the identified vulnerability.

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.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203