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

Published Mar 14, 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: Use After Free in unixgc() which could result in a local privilege escalation (CVE-2021-0920) kernel: local privilege escalation by exploiting the fsconfig syscall parameter leads to container breakout (CVE-2021-4154) kernel: possible privileges escalation due to missing TLB flush (CVE-2022-0330) kernel: remote stack overflow via kernel panic on systems using TIPC may lead to DoS (CVE-2022-0435) kernel: cgroups v1 releaseagent feature may allow privilege escalation (CVE-2022-0492) kernel: failing usercopy allows for use-after-free exploitation (CVE-2022-22942) 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

28 affected componentsFixes available
redhat/kpatch-patch<4_18_0-348-1-3.el8
4_18_0-348-1-3.el8
redhat/kpatch-patch<4_18_0-348_12_2-1-1.el8_5
4_18_0-348_12_2-1-1.el8_5
redhat/kpatch-patch<4_18_0-348_2_1-1-2.el8_5
4_18_0-348_2_1-1-2.el8_5
redhat/kpatch-patch<4_18_0-348_7_1-1-2.el8_5
4_18_0-348_7_1-1-2.el8_5
redhat/kpatch-patch<4_18_0-348-1-3.el8
4_18_0-348-1-3.el8
redhat/kpatch-patch<4_18_0-348-debuginfo-1-3.el8
4_18_0-348-debuginfo-1-3.el8
redhat/kpatch-patch<4_18_0-348-debugsource-1-3.el8
4_18_0-348-debugsource-1-3.el8
redhat/kpatch-patch<4_18_0-348_12_2-1-1.el8_5
4_18_0-348_12_2-1-1.el8_5
redhat/kpatch-patch<4_18_0-348_12_2-debuginfo-1-1.el8_5
4_18_0-348_12_2-debuginfo-1-1.el8_5
redhat/kpatch-patch<4_18_0-348_12_2-debugsource-1-1.el8_5
4_18_0-348_12_2-debugsource-1-1.el8_5
redhat/kpatch-patch<4_18_0-348_2_1-1-2.el8_5
4_18_0-348_2_1-1-2.el8_5
redhat/kpatch-patch<4_18_0-348_2_1-debuginfo-1-2.el8_5
4_18_0-348_2_1-debuginfo-1-2.el8_5
redhat/kpatch-patch<4_18_0-348_2_1-debugsource-1-2.el8_5
4_18_0-348_2_1-debugsource-1-2.el8_5
redhat/kpatch-patch<4_18_0-348_7_1-1-2.el8_5
4_18_0-348_7_1-1-2.el8_5
redhat/kpatch-patch<4_18_0-348_7_1-debuginfo-1-2.el8_5
4_18_0-348_7_1-debuginfo-1-2.el8_5
redhat/kpatch-patch<4_18_0-348_7_1-debugsource-1-2.el8_5
4_18_0-348_7_1-debugsource-1-2.el8_5
redhat/kpatch-patch<4_18_0-348-1-3.el8
4_18_0-348-1-3.el8
redhat/kpatch-patch<4_18_0-348-debuginfo-1-3.el8
4_18_0-348-debuginfo-1-3.el8
redhat/kpatch-patch<4_18_0-348-debugsource-1-3.el8
4_18_0-348-debugsource-1-3.el8
redhat/kpatch-patch<4_18_0-348_12_2-1-1.el8_5
4_18_0-348_12_2-1-1.el8_5
redhat/kpatch-patch<4_18_0-348_12_2-debuginfo-1-1.el8_5
4_18_0-348_12_2-debuginfo-1-1.el8_5
redhat/kpatch-patch<4_18_0-348_12_2-debugsource-1-1.el8_5
4_18_0-348_12_2-debugsource-1-1.el8_5
redhat/kpatch-patch<4_18_0-348_2_1-1-2.el8_5
4_18_0-348_2_1-1-2.el8_5
redhat/kpatch-patch<4_18_0-348_2_1-debuginfo-1-2.el8_5
4_18_0-348_2_1-debuginfo-1-2.el8_5
redhat/kpatch-patch<4_18_0-348_2_1-debugsource-1-2.el8_5
4_18_0-348_2_1-debugsource-1-2.el8_5
redhat/kpatch-patch<4_18_0-348_7_1-1-2.el8_5
4_18_0-348_7_1-1-2.el8_5
redhat/kpatch-patch<4_18_0-348_7_1-debuginfo-1-2.el8_5
4_18_0-348_7_1-debuginfo-1-2.el8_5
redhat/kpatch-patch<4_18_0-348_7_1-debugsource-1-2.el8_5
4_18_0-348_7_1-debugsource-1-2.el8_5

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-348-1-3.el8
  2. Upgrade

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

    Fixed in 4_18_0-348_12_2-1-1.el8_5
  3. Upgrade

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

    Fixed in 4_18_0-348_2_1-1-2.el8_5
  4. Upgrade

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

    Fixed in 4_18_0-348_7_1-1-2.el8_5
  5. Upgrade

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

    Fixed in 4_18_0-348-debuginfo-1-3.el8
  6. Upgrade

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

    Fixed in 4_18_0-348-debugsource-1-3.el8
  7. Upgrade

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

    Fixed in 4_18_0-348_12_2-debuginfo-1-1.el8_5
  8. Upgrade

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

    Fixed in 4_18_0-348_12_2-debugsource-1-1.el8_5
  9. Upgrade

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

    Fixed in 4_18_0-348_2_1-debuginfo-1-2.el8_5
  10. Upgrade

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

    Fixed in 4_18_0-348_2_1-debugsource-1-2.el8_5
  11. Upgrade

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

    Fixed in 4_18_0-348_7_1-debuginfo-1-2.el8_5
  12. Upgrade

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

    Fixed in 4_18_0-348_7_1-debugsource-1-2.el8_5
  13. Upgrade

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

    Patch kpatch-patch security update
  14. Compensating control

    Apply the kpatch-patch kernel live patch update; it is automatically loaded by the RPM post-install script to modify the code of a running kernel.

Event History

Jul 16, 2026
Advisory Published
via Red Hat·08:43 PM
Data Sourced
via Red Hat·08:43 PM
RemedyDescriptionAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of RHSA-2022:0849?

The severity of RHSA-2022:0849 is classified as high due to the potential for local privilege escalation.

2

How do I fix RHSA-2022:0849?

To fix RHSA-2022:0849, update the kpatch-patch package to the recommended versions listed in the advisory.

3

What vulnerabilities are addressed in RHSA-2022:0849?

RHSA-2022:0849 addresses a use-after-free vulnerability in unix_gc() that may lead to local privilege escalation (CVE-2021-0920).

4

Which software packages are affected by RHSA-2022:0849?

Affected packages include various versions of the kpatch-patch package specifically for el8 and el8_5 distributions.

5

Is a reboot required after applying the fix for RHSA-2022:0849?

A reboot may be required after applying the fix for RHSA-2022:0849 to ensure that all components are properly updated.

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