RHSA-2021:2167: Important: kpatch-patch security update

Published Jun 1, 2021
·
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 eventpoll.c may lead to escalation of privilege (CVE-2020-0466) kernel: SCSI target (LIO) write to any block on ILO backstore (CVE-2020-28374) 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

84 affected componentsFixes available
redhat/kpatch-patch<4_18_0-193_13_2-1-9.el8_2
4_18_0-193_13_2-1-9.el8_2
redhat/kpatch-patch<4_18_0-193_14_3-1-9.el8_2
4_18_0-193_14_3-1-9.el8_2
redhat/kpatch-patch<4_18_0-193_19_1-1-9.el8_2
4_18_0-193_19_1-1-9.el8_2
redhat/kpatch-patch<4_18_0-193_28_1-1-7.el8_2
4_18_0-193_28_1-1-7.el8_2
redhat/kpatch-patch<4_18_0-193_29_1-1-7.el8_2
4_18_0-193_29_1-1-7.el8_2
redhat/kpatch-patch<4_18_0-193_37_1-1-7.el8_2
4_18_0-193_37_1-1-7.el8_2
redhat/kpatch-patch<4_18_0-193_40_1-1-7.el8_2
4_18_0-193_40_1-1-7.el8_2
redhat/kpatch-patch<4_18_0-193_41_1-1-7.el8_2
4_18_0-193_41_1-1-7.el8_2
redhat/kpatch-patch<4_18_0-193_46_1-1-4.el8_2
4_18_0-193_46_1-1-4.el8_2
redhat/kpatch-patch<4_18_0-193_47_1-1-4.el8_2
4_18_0-193_47_1-1-4.el8_2
redhat/kpatch-patch<4_18_0-193_51_1-1-1.el8_2
4_18_0-193_51_1-1-1.el8_2
redhat/kpatch-patch<4_18_0-193_6_3-1-11.el8_2
4_18_0-193_6_3-1-11.el8_2
redhat/kpatch-patch<4_18_0-193_13_2-1-9.el8_2
4_18_0-193_13_2-1-9.el8_2
redhat/kpatch-patch<4_18_0-193_13_2-debuginfo-1-9.el8_2
4_18_0-193_13_2-debuginfo-1-9.el8_2
redhat/kpatch-patch<4_18_0-193_13_2-debugsource-1-9.el8_2
4_18_0-193_13_2-debugsource-1-9.el8_2
redhat/kpatch-patch<4_18_0-193_14_3-1-9.el8_2
4_18_0-193_14_3-1-9.el8_2
redhat/kpatch-patch<4_18_0-193_14_3-debuginfo-1-9.el8_2
4_18_0-193_14_3-debuginfo-1-9.el8_2
redhat/kpatch-patch<4_18_0-193_14_3-debugsource-1-9.el8_2
4_18_0-193_14_3-debugsource-1-9.el8_2
redhat/kpatch-patch<4_18_0-193_19_1-1-9.el8_2
4_18_0-193_19_1-1-9.el8_2
redhat/kpatch-patch<4_18_0-193_19_1-debuginfo-1-9.el8_2
4_18_0-193_19_1-debuginfo-1-9.el8_2
redhat/kpatch-patch<4_18_0-193_19_1-debugsource-1-9.el8_2
4_18_0-193_19_1-debugsource-1-9.el8_2
redhat/kpatch-patch<4_18_0-193_28_1-1-7.el8_2
4_18_0-193_28_1-1-7.el8_2
redhat/kpatch-patch<4_18_0-193_28_1-debuginfo-1-7.el8_2
4_18_0-193_28_1-debuginfo-1-7.el8_2
redhat/kpatch-patch<4_18_0-193_28_1-debugsource-1-7.el8_2
4_18_0-193_28_1-debugsource-1-7.el8_2
redhat/kpatch-patch<4_18_0-193_29_1-1-7.el8_2
4_18_0-193_29_1-1-7.el8_2
redhat/kpatch-patch<4_18_0-193_29_1-debuginfo-1-7.el8_2
4_18_0-193_29_1-debuginfo-1-7.el8_2
redhat/kpatch-patch<4_18_0-193_29_1-debugsource-1-7.el8_2
4_18_0-193_29_1-debugsource-1-7.el8_2
redhat/kpatch-patch<4_18_0-193_37_1-1-7.el8_2
4_18_0-193_37_1-1-7.el8_2
redhat/kpatch-patch<4_18_0-193_37_1-debuginfo-1-7.el8_2
4_18_0-193_37_1-debuginfo-1-7.el8_2
redhat/kpatch-patch<4_18_0-193_37_1-debugsource-1-7.el8_2
4_18_0-193_37_1-debugsource-1-7.el8_2
redhat/kpatch-patch<4_18_0-193_40_1-1-7.el8_2
4_18_0-193_40_1-1-7.el8_2
redhat/kpatch-patch<4_18_0-193_40_1-debuginfo-1-7.el8_2
4_18_0-193_40_1-debuginfo-1-7.el8_2
redhat/kpatch-patch<4_18_0-193_40_1-debugsource-1-7.el8_2
4_18_0-193_40_1-debugsource-1-7.el8_2
redhat/kpatch-patch<4_18_0-193_41_1-1-7.el8_2
4_18_0-193_41_1-1-7.el8_2
redhat/kpatch-patch<4_18_0-193_41_1-debuginfo-1-7.el8_2
4_18_0-193_41_1-debuginfo-1-7.el8_2
redhat/kpatch-patch<4_18_0-193_41_1-debugsource-1-7.el8_2
4_18_0-193_41_1-debugsource-1-7.el8_2
redhat/kpatch-patch<4_18_0-193_46_1-1-4.el8_2
4_18_0-193_46_1-1-4.el8_2
redhat/kpatch-patch<4_18_0-193_46_1-debuginfo-1-4.el8_2
4_18_0-193_46_1-debuginfo-1-4.el8_2
redhat/kpatch-patch<4_18_0-193_46_1-debugsource-1-4.el8_2
4_18_0-193_46_1-debugsource-1-4.el8_2
redhat/kpatch-patch<4_18_0-193_47_1-1-4.el8_2
4_18_0-193_47_1-1-4.el8_2
redhat/kpatch-patch<4_18_0-193_47_1-debuginfo-1-4.el8_2
4_18_0-193_47_1-debuginfo-1-4.el8_2
redhat/kpatch-patch<4_18_0-193_47_1-debugsource-1-4.el8_2
4_18_0-193_47_1-debugsource-1-4.el8_2
redhat/kpatch-patch<4_18_0-193_51_1-1-1.el8_2
4_18_0-193_51_1-1-1.el8_2
redhat/kpatch-patch<4_18_0-193_51_1-debuginfo-1-1.el8_2
4_18_0-193_51_1-debuginfo-1-1.el8_2
redhat/kpatch-patch<4_18_0-193_51_1-debugsource-1-1.el8_2
4_18_0-193_51_1-debugsource-1-1.el8_2
redhat/kpatch-patch<4_18_0-193_6_3-1-11.el8_2
4_18_0-193_6_3-1-11.el8_2
redhat/kpatch-patch<4_18_0-193_6_3-debuginfo-1-11.el8_2
4_18_0-193_6_3-debuginfo-1-11.el8_2
redhat/kpatch-patch<4_18_0-193_6_3-debugsource-1-11.el8_2
4_18_0-193_6_3-debugsource-1-11.el8_2
redhat/kpatch-patch<4_18_0-193_13_2-1-9.el8_2
4_18_0-193_13_2-1-9.el8_2
redhat/kpatch-patch<4_18_0-193_13_2-debuginfo-1-9.el8_2
4_18_0-193_13_2-debuginfo-1-9.el8_2
redhat/kpatch-patch<4_18_0-193_13_2-debugsource-1-9.el8_2
4_18_0-193_13_2-debugsource-1-9.el8_2
redhat/kpatch-patch<4_18_0-193_14_3-1-9.el8_2
4_18_0-193_14_3-1-9.el8_2
redhat/kpatch-patch<4_18_0-193_14_3-debuginfo-1-9.el8_2
4_18_0-193_14_3-debuginfo-1-9.el8_2
redhat/kpatch-patch<4_18_0-193_14_3-debugsource-1-9.el8_2
4_18_0-193_14_3-debugsource-1-9.el8_2
redhat/kpatch-patch<4_18_0-193_19_1-1-9.el8_2
4_18_0-193_19_1-1-9.el8_2
redhat/kpatch-patch<4_18_0-193_19_1-debuginfo-1-9.el8_2
4_18_0-193_19_1-debuginfo-1-9.el8_2
redhat/kpatch-patch<4_18_0-193_19_1-debugsource-1-9.el8_2
4_18_0-193_19_1-debugsource-1-9.el8_2
redhat/kpatch-patch<4_18_0-193_28_1-1-7.el8_2
4_18_0-193_28_1-1-7.el8_2
redhat/kpatch-patch<4_18_0-193_28_1-debuginfo-1-7.el8_2
4_18_0-193_28_1-debuginfo-1-7.el8_2
redhat/kpatch-patch<4_18_0-193_28_1-debugsource-1-7.el8_2
4_18_0-193_28_1-debugsource-1-7.el8_2
redhat/kpatch-patch<4_18_0-193_29_1-1-7.el8_2
4_18_0-193_29_1-1-7.el8_2
redhat/kpatch-patch<4_18_0-193_29_1-debuginfo-1-7.el8_2
4_18_0-193_29_1-debuginfo-1-7.el8_2
redhat/kpatch-patch<4_18_0-193_29_1-debugsource-1-7.el8_2
4_18_0-193_29_1-debugsource-1-7.el8_2
redhat/kpatch-patch<4_18_0-193_37_1-1-7.el8_2
4_18_0-193_37_1-1-7.el8_2
redhat/kpatch-patch<4_18_0-193_37_1-debuginfo-1-7.el8_2
4_18_0-193_37_1-debuginfo-1-7.el8_2
redhat/kpatch-patch<4_18_0-193_37_1-debugsource-1-7.el8_2
4_18_0-193_37_1-debugsource-1-7.el8_2
redhat/kpatch-patch<4_18_0-193_40_1-1-7.el8_2
4_18_0-193_40_1-1-7.el8_2
redhat/kpatch-patch<4_18_0-193_40_1-debuginfo-1-7.el8_2
4_18_0-193_40_1-debuginfo-1-7.el8_2
redhat/kpatch-patch<4_18_0-193_40_1-debugsource-1-7.el8_2
4_18_0-193_40_1-debugsource-1-7.el8_2
redhat/kpatch-patch<4_18_0-193_41_1-1-7.el8_2
4_18_0-193_41_1-1-7.el8_2
redhat/kpatch-patch<4_18_0-193_41_1-debuginfo-1-7.el8_2
4_18_0-193_41_1-debuginfo-1-7.el8_2
redhat/kpatch-patch<4_18_0-193_41_1-debugsource-1-7.el8_2
4_18_0-193_41_1-debugsource-1-7.el8_2
redhat/kpatch-patch<4_18_0-193_46_1-1-4.el8_2
4_18_0-193_46_1-1-4.el8_2
redhat/kpatch-patch<4_18_0-193_46_1-debuginfo-1-4.el8_2
4_18_0-193_46_1-debuginfo-1-4.el8_2
redhat/kpatch-patch<4_18_0-193_46_1-debugsource-1-4.el8_2
4_18_0-193_46_1-debugsource-1-4.el8_2
redhat/kpatch-patch<4_18_0-193_47_1-1-4.el8_2
4_18_0-193_47_1-1-4.el8_2
redhat/kpatch-patch<4_18_0-193_47_1-debuginfo-1-4.el8_2
4_18_0-193_47_1-debuginfo-1-4.el8_2
redhat/kpatch-patch<4_18_0-193_47_1-debugsource-1-4.el8_2
4_18_0-193_47_1-debugsource-1-4.el8_2
redhat/kpatch-patch<4_18_0-193_51_1-1-1.el8_2
4_18_0-193_51_1-1-1.el8_2
redhat/kpatch-patch<4_18_0-193_51_1-debuginfo-1-1.el8_2
4_18_0-193_51_1-debuginfo-1-1.el8_2
redhat/kpatch-patch<4_18_0-193_51_1-debugsource-1-1.el8_2
4_18_0-193_51_1-debugsource-1-1.el8_2
redhat/kpatch-patch<4_18_0-193_6_3-1-11.el8_2
4_18_0-193_6_3-1-11.el8_2
redhat/kpatch-patch<4_18_0-193_6_3-debuginfo-1-11.el8_2
4_18_0-193_6_3-debuginfo-1-11.el8_2
redhat/kpatch-patch<4_18_0-193_6_3-debugsource-1-11.el8_2
4_18_0-193_6_3-debugsource-1-11.el8_2

Remediation

Event History

Jun 10, 2026
Advisory Published
via Red Hat·03:05 PM
Data Sourced
via Red Hat·03:05 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-2021:2167?

RHSA-2021:2167 has a severity classification of Important due to privilege escalation vulnerabilities.

2

How do I fix RHSA-2021:2167?

You can fix RHSA-2021:2167 by applying the updated kpatch-patch packages available in your system's package manager.

3

What vulnerabilities are addressed in RHSA-2021:2167?

RHSA-2021:2167 addresses a use after free vulnerability in eventpoll.c, which can lead to privilege escalation (CVE-2020-0466).

4

Which versions of kpatch-patch are affected by RHSA-2021:2167?

Versions of kpatch-patch prior to 4_18_0-193_13_2-1-9.el8_2 are affected by RHSA-2021:2167.

5

Is there a specific package to install for patching RHSA-2021:2167?

Yes, you need to install the kpatch-patch package version 4_18_0-193_13_2-1-9.el8_2 or higher to patch RHSA-2021:2167.

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