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

Published Dec 6, 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): kernel: KVM: cmpxchggpte can write to pfns outside the userspace region (CVE-2022-1158) kernel: openvswitch: integer underflow leads to out-of-bounds write in reservesfasize() (CVE-2022-2639) 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

42 affected componentsFixes available
redhat/kpatch-patch<4_18_0-372_13_1-1-3.el8_6
4_18_0-372_13_1-1-3.el8_6
redhat/kpatch-patch<4_18_0-372_16_1-1-3.el8_6
4_18_0-372_16_1-1-3.el8_6
redhat/kpatch-patch<4_18_0-372_19_1-1-2.el8_6
4_18_0-372_19_1-1-2.el8_6
redhat/kpatch-patch<4_18_0-372_26_1-1-2.el8_6
4_18_0-372_26_1-1-2.el8_6
redhat/kpatch-patch<4_18_0-372_32_1-1-1.el8_6
4_18_0-372_32_1-1-1.el8_6
redhat/kpatch-patch<4_18_0-372_9_1-1-4.el8
4_18_0-372_9_1-1-4.el8
redhat/kpatch-patch<4_18_0-372_13_1-1-3.el8_6
4_18_0-372_13_1-1-3.el8_6
redhat/kpatch-patch<4_18_0-372_13_1-debuginfo-1-3.el8_6
4_18_0-372_13_1-debuginfo-1-3.el8_6
redhat/kpatch-patch<4_18_0-372_13_1-debugsource-1-3.el8_6
4_18_0-372_13_1-debugsource-1-3.el8_6
redhat/kpatch-patch<4_18_0-372_16_1-1-3.el8_6
4_18_0-372_16_1-1-3.el8_6
redhat/kpatch-patch<4_18_0-372_16_1-debuginfo-1-3.el8_6
4_18_0-372_16_1-debuginfo-1-3.el8_6
redhat/kpatch-patch<4_18_0-372_16_1-debugsource-1-3.el8_6
4_18_0-372_16_1-debugsource-1-3.el8_6
redhat/kpatch-patch<4_18_0-372_19_1-1-2.el8_6
4_18_0-372_19_1-1-2.el8_6
redhat/kpatch-patch<4_18_0-372_19_1-debuginfo-1-2.el8_6
4_18_0-372_19_1-debuginfo-1-2.el8_6
redhat/kpatch-patch<4_18_0-372_19_1-debugsource-1-2.el8_6
4_18_0-372_19_1-debugsource-1-2.el8_6
redhat/kpatch-patch<4_18_0-372_26_1-1-2.el8_6
4_18_0-372_26_1-1-2.el8_6
redhat/kpatch-patch<4_18_0-372_26_1-debuginfo-1-2.el8_6
4_18_0-372_26_1-debuginfo-1-2.el8_6
redhat/kpatch-patch<4_18_0-372_26_1-debugsource-1-2.el8_6
4_18_0-372_26_1-debugsource-1-2.el8_6
redhat/kpatch-patch<4_18_0-372_32_1-1-1.el8_6
4_18_0-372_32_1-1-1.el8_6
redhat/kpatch-patch<4_18_0-372_32_1-debuginfo-1-1.el8_6
4_18_0-372_32_1-debuginfo-1-1.el8_6
redhat/kpatch-patch<4_18_0-372_32_1-debugsource-1-1.el8_6
4_18_0-372_32_1-debugsource-1-1.el8_6
redhat/kpatch-patch<4_18_0-372_9_1-1-4.el8
4_18_0-372_9_1-1-4.el8
redhat/kpatch-patch<4_18_0-372_9_1-debuginfo-1-4.el8
4_18_0-372_9_1-debuginfo-1-4.el8
redhat/kpatch-patch<4_18_0-372_9_1-debugsource-1-4.el8
4_18_0-372_9_1-debugsource-1-4.el8
redhat/kpatch-patch<4_18_0-372_13_1-1-3.el8_6
4_18_0-372_13_1-1-3.el8_6
redhat/kpatch-patch<4_18_0-372_13_1-debuginfo-1-3.el8_6
4_18_0-372_13_1-debuginfo-1-3.el8_6
redhat/kpatch-patch<4_18_0-372_13_1-debugsource-1-3.el8_6
4_18_0-372_13_1-debugsource-1-3.el8_6
redhat/kpatch-patch<4_18_0-372_16_1-1-3.el8_6
4_18_0-372_16_1-1-3.el8_6
redhat/kpatch-patch<4_18_0-372_16_1-debuginfo-1-3.el8_6
4_18_0-372_16_1-debuginfo-1-3.el8_6
redhat/kpatch-patch<4_18_0-372_16_1-debugsource-1-3.el8_6
4_18_0-372_16_1-debugsource-1-3.el8_6
redhat/kpatch-patch<4_18_0-372_19_1-1-2.el8_6
4_18_0-372_19_1-1-2.el8_6
redhat/kpatch-patch<4_18_0-372_19_1-debuginfo-1-2.el8_6
4_18_0-372_19_1-debuginfo-1-2.el8_6
redhat/kpatch-patch<4_18_0-372_19_1-debugsource-1-2.el8_6
4_18_0-372_19_1-debugsource-1-2.el8_6
redhat/kpatch-patch<4_18_0-372_26_1-1-2.el8_6
4_18_0-372_26_1-1-2.el8_6
redhat/kpatch-patch<4_18_0-372_26_1-debuginfo-1-2.el8_6
4_18_0-372_26_1-debuginfo-1-2.el8_6
redhat/kpatch-patch<4_18_0-372_26_1-debugsource-1-2.el8_6
4_18_0-372_26_1-debugsource-1-2.el8_6
redhat/kpatch-patch<4_18_0-372_32_1-1-1.el8_6
4_18_0-372_32_1-1-1.el8_6
redhat/kpatch-patch<4_18_0-372_32_1-debuginfo-1-1.el8_6
4_18_0-372_32_1-debuginfo-1-1.el8_6
redhat/kpatch-patch<4_18_0-372_32_1-debugsource-1-1.el8_6
4_18_0-372_32_1-debugsource-1-1.el8_6
redhat/kpatch-patch<4_18_0-372_9_1-1-4.el8
4_18_0-372_9_1-1-4.el8
redhat/kpatch-patch<4_18_0-372_9_1-debuginfo-1-4.el8
4_18_0-372_9_1-debuginfo-1-4.el8
redhat/kpatch-patch<4_18_0-372_9_1-debugsource-1-4.el8
4_18_0-372_9_1-debugsource-1-4.el8

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-372_13_1-1-3.el8_6
  2. Upgrade

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

    Fixed in 4_18_0-372_16_1-1-3.el8_6
  3. Upgrade

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

    Fixed in 4_18_0-372_19_1-1-2.el8_6
  4. Upgrade

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

    Fixed in 4_18_0-372_26_1-1-2.el8_6
  5. Upgrade

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

    Fixed in 4_18_0-372_32_1-1-1.el8_6
  6. Upgrade

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

    Fixed in 4_18_0-372_9_1-1-4.el8
  7. Upgrade

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

    Fixed in 4_18_0-372_13_1-debuginfo-1-3.el8_6
  8. Upgrade

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

    Fixed in 4_18_0-372_13_1-debugsource-1-3.el8_6
  9. Upgrade

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

    Fixed in 4_18_0-372_16_1-debuginfo-1-3.el8_6
  10. Upgrade

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

    Fixed in 4_18_0-372_16_1-debugsource-1-3.el8_6
  11. Upgrade

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

    Fixed in 4_18_0-372_19_1-debuginfo-1-2.el8_6
  12. Upgrade

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

    Fixed in 4_18_0-372_19_1-debugsource-1-2.el8_6
  13. Upgrade

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

    Fixed in 4_18_0-372_26_1-debuginfo-1-2.el8_6
  14. Upgrade

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

    Fixed in 4_18_0-372_26_1-debugsource-1-2.el8_6
  15. Upgrade

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

    Fixed in 4_18_0-372_32_1-debuginfo-1-1.el8_6
  16. Upgrade

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

    Fixed in 4_18_0-372_32_1-debugsource-1-1.el8_6
  17. Upgrade

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

    Fixed in 4_18_0-372_9_1-debuginfo-1-4.el8
  18. Upgrade

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

    Fixed in 4_18_0-372_9_1-debugsource-1-4.el8
  19. Upgrade

    Upgrade openvswitch/kernel (CVE-2022-2639) to a version that resolves this vulnerability.

    Patch kpatch-patch security update
  20. Upgrade

    Upgrade KVM (CVE-2022-1158) to a version that resolves this vulnerability.

    Patch kpatch-patch security update

Event History

May 29, 2026
Advisory Published
via Red Hat·09:18 PM
Data Sourced
via Red Hat·09:18 PM
RemedyDescriptionAffected Software

Frequently Asked Questions

1

What is the severity of RHSA-2022:8831?

The severity of RHSA-2022:8831 is classified as important.

2

How do I fix RHSA-2022:8831?

To fix RHSA-2022:8831, update the kpatch-patch to the latest version available for your system.

3

What vulnerabilities does RHSA-2022:8831 address?

RHSA-2022:8831 addresses vulnerabilities including CVE-2022-1158 related to the kernel's KVM component.

4

Which versions of kpatch-patch are affected by RHSA-2022:8831?

Affected versions of kpatch-patch include 4_18_0-372_9_1-1-4.el8 and other specified versions up to 4_18_0-372_32_1-1-1.el8_6.

5

Is upgrading kpatch-patch sufficient to resolve RHSA-2022:8831?

Yes, upgrading kpatch-patch to the remedied versions will resolve the issues outlined in RHSA-2022:8831.

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