RHSA-2022:0851: 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.<br>Security Fix(es):<br><li> kernel: Use After Free in unixgc() which could result in a local privilege escalation (CVE-2021-0920)</li> <li> kernel: use-after-free in RDMA listen() (CVE-2021-4028)</li> <li> kernel: fget: check that the fd still exists after getting a ref to it (CVE-2021-4083)</li> <li> kernel: possible privileges escalation due to missing TLB flush (CVE-2022-0330)</li> <li> kernel: cgroups v1 releaseagent feature may allow privilege escalation (CVE-2022-0492)</li> <li> kernel: failing usercopy allows for use-after-free exploitation (CVE-2022-22942)</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

63 affected componentsFixes available
redhat/kpatch-patch<4_18_0-147_44_1-1-10.el8_1
4_18_0-147_44_1-1-10.el8_1
redhat/kpatch-patch<4_18_0-147_48_1-1-7.el8_1
4_18_0-147_48_1-1-7.el8_1
redhat/kpatch-patch<4_18_0-147_51_1-1-6.el8_1
4_18_0-147_51_1-1-6.el8_1
redhat/kpatch-patch<4_18_0-147_51_2-1-5.el8_1
4_18_0-147_51_2-1-5.el8_1
redhat/kpatch-patch<4_18_0-147_52_1-1-4.el8_1
4_18_0-147_52_1-1-4.el8_1
redhat/kpatch-patch<4_18_0-147_54_2-1-3.el8_1
4_18_0-147_54_2-1-3.el8_1
redhat/kpatch-patch<4_18_0-147_56_1-1-3.el8_1
4_18_0-147_56_1-1-3.el8_1
redhat/kpatch-patch<4_18_0-147_57_1-1-2.el8_1
4_18_0-147_57_1-1-2.el8_1
redhat/kpatch-patch<4_18_0-147_59_1-1-1.el8_1
4_18_0-147_59_1-1-1.el8_1
redhat/kpatch-patch<4_18_0-147_44_1-1-10.el8_1
4_18_0-147_44_1-1-10.el8_1
redhat/kpatch-patch<4_18_0-147_44_1-debuginfo-1-10.el8_1
4_18_0-147_44_1-debuginfo-1-10.el8_1
redhat/kpatch-patch<4_18_0-147_44_1-debugsource-1-10.el8_1
4_18_0-147_44_1-debugsource-1-10.el8_1
redhat/kpatch-patch<4_18_0-147_48_1-1-7.el8_1
4_18_0-147_48_1-1-7.el8_1
redhat/kpatch-patch<4_18_0-147_48_1-debuginfo-1-7.el8_1
4_18_0-147_48_1-debuginfo-1-7.el8_1
redhat/kpatch-patch<4_18_0-147_48_1-debugsource-1-7.el8_1
4_18_0-147_48_1-debugsource-1-7.el8_1
redhat/kpatch-patch<4_18_0-147_51_1-1-6.el8_1
4_18_0-147_51_1-1-6.el8_1
redhat/kpatch-patch<4_18_0-147_51_1-debuginfo-1-6.el8_1
4_18_0-147_51_1-debuginfo-1-6.el8_1
redhat/kpatch-patch<4_18_0-147_51_1-debugsource-1-6.el8_1
4_18_0-147_51_1-debugsource-1-6.el8_1
redhat/kpatch-patch<4_18_0-147_51_2-1-5.el8_1
4_18_0-147_51_2-1-5.el8_1
redhat/kpatch-patch<4_18_0-147_51_2-debuginfo-1-5.el8_1
4_18_0-147_51_2-debuginfo-1-5.el8_1
redhat/kpatch-patch<4_18_0-147_51_2-debugsource-1-5.el8_1
4_18_0-147_51_2-debugsource-1-5.el8_1
redhat/kpatch-patch<4_18_0-147_52_1-1-4.el8_1
4_18_0-147_52_1-1-4.el8_1
redhat/kpatch-patch<4_18_0-147_52_1-debuginfo-1-4.el8_1
4_18_0-147_52_1-debuginfo-1-4.el8_1
redhat/kpatch-patch<4_18_0-147_52_1-debugsource-1-4.el8_1
4_18_0-147_52_1-debugsource-1-4.el8_1
redhat/kpatch-patch<4_18_0-147_54_2-1-3.el8_1
4_18_0-147_54_2-1-3.el8_1
redhat/kpatch-patch<4_18_0-147_54_2-debuginfo-1-3.el8_1
4_18_0-147_54_2-debuginfo-1-3.el8_1
redhat/kpatch-patch<4_18_0-147_54_2-debugsource-1-3.el8_1
4_18_0-147_54_2-debugsource-1-3.el8_1
redhat/kpatch-patch<4_18_0-147_56_1-1-3.el8_1
4_18_0-147_56_1-1-3.el8_1
redhat/kpatch-patch<4_18_0-147_56_1-debuginfo-1-3.el8_1
4_18_0-147_56_1-debuginfo-1-3.el8_1
redhat/kpatch-patch<4_18_0-147_56_1-debugsource-1-3.el8_1
4_18_0-147_56_1-debugsource-1-3.el8_1
redhat/kpatch-patch<4_18_0-147_57_1-1-2.el8_1
4_18_0-147_57_1-1-2.el8_1
redhat/kpatch-patch<4_18_0-147_57_1-debuginfo-1-2.el8_1
4_18_0-147_57_1-debuginfo-1-2.el8_1
redhat/kpatch-patch<4_18_0-147_57_1-debugsource-1-2.el8_1
4_18_0-147_57_1-debugsource-1-2.el8_1
redhat/kpatch-patch<4_18_0-147_59_1-1-1.el8_1
4_18_0-147_59_1-1-1.el8_1
redhat/kpatch-patch<4_18_0-147_59_1-debuginfo-1-1.el8_1
4_18_0-147_59_1-debuginfo-1-1.el8_1
redhat/kpatch-patch<4_18_0-147_59_1-debugsource-1-1.el8_1
4_18_0-147_59_1-debugsource-1-1.el8_1
redhat/kpatch-patch<4_18_0-147_44_1-1-10.el8_1
4_18_0-147_44_1-1-10.el8_1
redhat/kpatch-patch<4_18_0-147_44_1-debuginfo-1-10.el8_1
4_18_0-147_44_1-debuginfo-1-10.el8_1
redhat/kpatch-patch<4_18_0-147_44_1-debugsource-1-10.el8_1
4_18_0-147_44_1-debugsource-1-10.el8_1
redhat/kpatch-patch<4_18_0-147_48_1-1-7.el8_1
4_18_0-147_48_1-1-7.el8_1
redhat/kpatch-patch<4_18_0-147_48_1-debuginfo-1-7.el8_1
4_18_0-147_48_1-debuginfo-1-7.el8_1
redhat/kpatch-patch<4_18_0-147_48_1-debugsource-1-7.el8_1
4_18_0-147_48_1-debugsource-1-7.el8_1
redhat/kpatch-patch<4_18_0-147_51_1-1-6.el8_1
4_18_0-147_51_1-1-6.el8_1
redhat/kpatch-patch<4_18_0-147_51_1-debuginfo-1-6.el8_1
4_18_0-147_51_1-debuginfo-1-6.el8_1
redhat/kpatch-patch<4_18_0-147_51_1-debugsource-1-6.el8_1
4_18_0-147_51_1-debugsource-1-6.el8_1
redhat/kpatch-patch<4_18_0-147_51_2-1-5.el8_1
4_18_0-147_51_2-1-5.el8_1
redhat/kpatch-patch<4_18_0-147_51_2-debuginfo-1-5.el8_1
4_18_0-147_51_2-debuginfo-1-5.el8_1
redhat/kpatch-patch<4_18_0-147_51_2-debugsource-1-5.el8_1
4_18_0-147_51_2-debugsource-1-5.el8_1
redhat/kpatch-patch<4_18_0-147_52_1-1-4.el8_1
4_18_0-147_52_1-1-4.el8_1
redhat/kpatch-patch<4_18_0-147_52_1-debuginfo-1-4.el8_1
4_18_0-147_52_1-debuginfo-1-4.el8_1
redhat/kpatch-patch<4_18_0-147_52_1-debugsource-1-4.el8_1
4_18_0-147_52_1-debugsource-1-4.el8_1
redhat/kpatch-patch<4_18_0-147_54_2-1-3.el8_1
4_18_0-147_54_2-1-3.el8_1
redhat/kpatch-patch<4_18_0-147_54_2-debuginfo-1-3.el8_1
4_18_0-147_54_2-debuginfo-1-3.el8_1
redhat/kpatch-patch<4_18_0-147_54_2-debugsource-1-3.el8_1
4_18_0-147_54_2-debugsource-1-3.el8_1
redhat/kpatch-patch<4_18_0-147_56_1-1-3.el8_1
4_18_0-147_56_1-1-3.el8_1
redhat/kpatch-patch<4_18_0-147_56_1-debuginfo-1-3.el8_1
4_18_0-147_56_1-debuginfo-1-3.el8_1
redhat/kpatch-patch<4_18_0-147_56_1-debugsource-1-3.el8_1
4_18_0-147_56_1-debugsource-1-3.el8_1
redhat/kpatch-patch<4_18_0-147_57_1-1-2.el8_1
4_18_0-147_57_1-1-2.el8_1
redhat/kpatch-patch<4_18_0-147_57_1-debuginfo-1-2.el8_1
4_18_0-147_57_1-debuginfo-1-2.el8_1
redhat/kpatch-patch<4_18_0-147_57_1-debugsource-1-2.el8_1
4_18_0-147_57_1-debugsource-1-2.el8_1
redhat/kpatch-patch<4_18_0-147_59_1-1-1.el8_1
4_18_0-147_59_1-1-1.el8_1
redhat/kpatch-patch<4_18_0-147_59_1-debuginfo-1-1.el8_1
4_18_0-147_59_1-debuginfo-1-1.el8_1
redhat/kpatch-patch<4_18_0-147_59_1-debugsource-1-1.el8_1
4_18_0-147_59_1-debugsource-1-1.el8_1

Remediation

Event History

Jun 20, 2024
Advisory Published
via Red Hat·01:39 AM
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:0851?

The RHSA-2022:0851 vulnerability is categorized as having a local privilege escalation severity.

2

How do I fix RHSA-2022:0851?

You can fix RHSA-2022:0851 by updating the kpatch-patch package to the latest version specified in the advisory.

3

What systems are affected by RHSA-2022:0851?

RHSA-2022:0851 affects systems running specific versions of the kernel live patch module kpatch-patch.

4

Is there a CVE associated with RHSA-2022:0851?

Yes, the vulnerability described in RHSA-2022:0851 is associated with CVE-2021-0920.

5

What should I do if I cannot update my system due to RHSA-2022:0851?

If you cannot update, consider implementing additional security measures like limiting access to affected systems until the update can be applied.

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