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

Published Sep 7, 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: race condition in net/can/bcm.c leads to local privilege escalation (CVE-2021-3609) kernel: use-after-free in route4change() in net/sched/clsroute.c (CVE-2021-3715) kernel: powerpc: KVM guest OS users can cause host OS memory corruption (CVE-2021-37576) 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

70 affected componentsFixes available
redhat/kpatch-patch<4_18_0-147_27_1-1-13.el8_1
4_18_0-147_27_1-1-13.el8_1
redhat/kpatch-patch<4_18_0-147_32_1-1-11.el8_1
4_18_0-147_32_1-1-11.el8_1
redhat/kpatch-patch<4_18_0-147_34_1-1-11.el8_1
4_18_0-147_34_1-1-11.el8_1
redhat/kpatch-patch<4_18_0-147_38_1-1-10.el8_1
4_18_0-147_38_1-1-10.el8_1
redhat/kpatch-patch<4_18_0-147_43_1-1-8.el8_1
4_18_0-147_43_1-1-8.el8_1
redhat/kpatch-patch<4_18_0-147_44_1-1-7.el8_1
4_18_0-147_44_1-1-7.el8_1
redhat/kpatch-patch<4_18_0-147_48_1-1-4.el8_1
4_18_0-147_48_1-1-4.el8_1
redhat/kpatch-patch<4_18_0-147_51_1-1-3.el8_1
4_18_0-147_51_1-1-3.el8_1
redhat/kpatch-patch<4_18_0-147_51_2-1-2.el8_1
4_18_0-147_51_2-1-2.el8_1
redhat/kpatch-patch<4_18_0-147_52_1-1-1.el8_1
4_18_0-147_52_1-1-1.el8_1
redhat/kpatch-patch<4_18_0-147_27_1-1-13.el8_1
4_18_0-147_27_1-1-13.el8_1
redhat/kpatch-patch<4_18_0-147_27_1-debuginfo-1-13.el8_1
4_18_0-147_27_1-debuginfo-1-13.el8_1
redhat/kpatch-patch<4_18_0-147_27_1-debugsource-1-13.el8_1
4_18_0-147_27_1-debugsource-1-13.el8_1
redhat/kpatch-patch<4_18_0-147_32_1-1-11.el8_1
4_18_0-147_32_1-1-11.el8_1
redhat/kpatch-patch<4_18_0-147_32_1-debuginfo-1-11.el8_1
4_18_0-147_32_1-debuginfo-1-11.el8_1
redhat/kpatch-patch<4_18_0-147_32_1-debugsource-1-11.el8_1
4_18_0-147_32_1-debugsource-1-11.el8_1
redhat/kpatch-patch<4_18_0-147_34_1-1-11.el8_1
4_18_0-147_34_1-1-11.el8_1
redhat/kpatch-patch<4_18_0-147_34_1-debuginfo-1-11.el8_1
4_18_0-147_34_1-debuginfo-1-11.el8_1
redhat/kpatch-patch<4_18_0-147_34_1-debugsource-1-11.el8_1
4_18_0-147_34_1-debugsource-1-11.el8_1
redhat/kpatch-patch<4_18_0-147_38_1-1-10.el8_1
4_18_0-147_38_1-1-10.el8_1
redhat/kpatch-patch<4_18_0-147_38_1-debuginfo-1-10.el8_1
4_18_0-147_38_1-debuginfo-1-10.el8_1
redhat/kpatch-patch<4_18_0-147_38_1-debugsource-1-10.el8_1
4_18_0-147_38_1-debugsource-1-10.el8_1
redhat/kpatch-patch<4_18_0-147_43_1-1-8.el8_1
4_18_0-147_43_1-1-8.el8_1
redhat/kpatch-patch<4_18_0-147_43_1-debuginfo-1-8.el8_1
4_18_0-147_43_1-debuginfo-1-8.el8_1
redhat/kpatch-patch<4_18_0-147_43_1-debugsource-1-8.el8_1
4_18_0-147_43_1-debugsource-1-8.el8_1
redhat/kpatch-patch<4_18_0-147_44_1-1-7.el8_1
4_18_0-147_44_1-1-7.el8_1
redhat/kpatch-patch<4_18_0-147_44_1-debuginfo-1-7.el8_1
4_18_0-147_44_1-debuginfo-1-7.el8_1
redhat/kpatch-patch<4_18_0-147_44_1-debugsource-1-7.el8_1
4_18_0-147_44_1-debugsource-1-7.el8_1
redhat/kpatch-patch<4_18_0-147_48_1-1-4.el8_1
4_18_0-147_48_1-1-4.el8_1
redhat/kpatch-patch<4_18_0-147_48_1-debuginfo-1-4.el8_1
4_18_0-147_48_1-debuginfo-1-4.el8_1
redhat/kpatch-patch<4_18_0-147_48_1-debugsource-1-4.el8_1
4_18_0-147_48_1-debugsource-1-4.el8_1
redhat/kpatch-patch<4_18_0-147_51_1-1-3.el8_1
4_18_0-147_51_1-1-3.el8_1
redhat/kpatch-patch<4_18_0-147_51_1-debuginfo-1-3.el8_1
4_18_0-147_51_1-debuginfo-1-3.el8_1
redhat/kpatch-patch<4_18_0-147_51_1-debugsource-1-3.el8_1
4_18_0-147_51_1-debugsource-1-3.el8_1
redhat/kpatch-patch<4_18_0-147_51_2-1-2.el8_1
4_18_0-147_51_2-1-2.el8_1
redhat/kpatch-patch<4_18_0-147_51_2-debuginfo-1-2.el8_1
4_18_0-147_51_2-debuginfo-1-2.el8_1
redhat/kpatch-patch<4_18_0-147_51_2-debugsource-1-2.el8_1
4_18_0-147_51_2-debugsource-1-2.el8_1
redhat/kpatch-patch<4_18_0-147_52_1-1-1.el8_1
4_18_0-147_52_1-1-1.el8_1
redhat/kpatch-patch<4_18_0-147_52_1-debuginfo-1-1.el8_1
4_18_0-147_52_1-debuginfo-1-1.el8_1
redhat/kpatch-patch<4_18_0-147_52_1-debugsource-1-1.el8_1
4_18_0-147_52_1-debugsource-1-1.el8_1
redhat/kpatch-patch<4_18_0-147_27_1-1-13.el8_1
4_18_0-147_27_1-1-13.el8_1
redhat/kpatch-patch<4_18_0-147_27_1-debuginfo-1-13.el8_1
4_18_0-147_27_1-debuginfo-1-13.el8_1
redhat/kpatch-patch<4_18_0-147_27_1-debugsource-1-13.el8_1
4_18_0-147_27_1-debugsource-1-13.el8_1
redhat/kpatch-patch<4_18_0-147_32_1-1-11.el8_1
4_18_0-147_32_1-1-11.el8_1
redhat/kpatch-patch<4_18_0-147_32_1-debuginfo-1-11.el8_1
4_18_0-147_32_1-debuginfo-1-11.el8_1
redhat/kpatch-patch<4_18_0-147_32_1-debugsource-1-11.el8_1
4_18_0-147_32_1-debugsource-1-11.el8_1
redhat/kpatch-patch<4_18_0-147_34_1-1-11.el8_1
4_18_0-147_34_1-1-11.el8_1
redhat/kpatch-patch<4_18_0-147_34_1-debuginfo-1-11.el8_1
4_18_0-147_34_1-debuginfo-1-11.el8_1
redhat/kpatch-patch<4_18_0-147_34_1-debugsource-1-11.el8_1
4_18_0-147_34_1-debugsource-1-11.el8_1
redhat/kpatch-patch<4_18_0-147_38_1-1-10.el8_1
4_18_0-147_38_1-1-10.el8_1
redhat/kpatch-patch<4_18_0-147_38_1-debuginfo-1-10.el8_1
4_18_0-147_38_1-debuginfo-1-10.el8_1
redhat/kpatch-patch<4_18_0-147_38_1-debugsource-1-10.el8_1
4_18_0-147_38_1-debugsource-1-10.el8_1
redhat/kpatch-patch<4_18_0-147_43_1-1-8.el8_1
4_18_0-147_43_1-1-8.el8_1
redhat/kpatch-patch<4_18_0-147_43_1-debuginfo-1-8.el8_1
4_18_0-147_43_1-debuginfo-1-8.el8_1
redhat/kpatch-patch<4_18_0-147_43_1-debugsource-1-8.el8_1
4_18_0-147_43_1-debugsource-1-8.el8_1
redhat/kpatch-patch<4_18_0-147_44_1-1-7.el8_1
4_18_0-147_44_1-1-7.el8_1
redhat/kpatch-patch<4_18_0-147_44_1-debuginfo-1-7.el8_1
4_18_0-147_44_1-debuginfo-1-7.el8_1
redhat/kpatch-patch<4_18_0-147_44_1-debugsource-1-7.el8_1
4_18_0-147_44_1-debugsource-1-7.el8_1
redhat/kpatch-patch<4_18_0-147_48_1-1-4.el8_1
4_18_0-147_48_1-1-4.el8_1
redhat/kpatch-patch<4_18_0-147_48_1-debuginfo-1-4.el8_1
4_18_0-147_48_1-debuginfo-1-4.el8_1
redhat/kpatch-patch<4_18_0-147_48_1-debugsource-1-4.el8_1
4_18_0-147_48_1-debugsource-1-4.el8_1
redhat/kpatch-patch<4_18_0-147_51_1-1-3.el8_1
4_18_0-147_51_1-1-3.el8_1
redhat/kpatch-patch<4_18_0-147_51_1-debuginfo-1-3.el8_1
4_18_0-147_51_1-debuginfo-1-3.el8_1
redhat/kpatch-patch<4_18_0-147_51_1-debugsource-1-3.el8_1
4_18_0-147_51_1-debugsource-1-3.el8_1
redhat/kpatch-patch<4_18_0-147_51_2-1-2.el8_1
4_18_0-147_51_2-1-2.el8_1
redhat/kpatch-patch<4_18_0-147_51_2-debuginfo-1-2.el8_1
4_18_0-147_51_2-debuginfo-1-2.el8_1
redhat/kpatch-patch<4_18_0-147_51_2-debugsource-1-2.el8_1
4_18_0-147_51_2-debugsource-1-2.el8_1
redhat/kpatch-patch<4_18_0-147_52_1-1-1.el8_1
4_18_0-147_52_1-1-1.el8_1
redhat/kpatch-patch<4_18_0-147_52_1-debuginfo-1-1.el8_1
4_18_0-147_52_1-debuginfo-1-1.el8_1
redhat/kpatch-patch<4_18_0-147_52_1-debugsource-1-1.el8_1
4_18_0-147_52_1-debugsource-1-1.el8_1

Remediation

Event History

Feb 11, 2026
Advisory Published
via Red Hat·03:06 PM
Data Sourced
via Red Hat·03:06 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:3442?

RHSA-2021:3442 addresses a critical race condition vulnerability leading to local privilege escalation.

2

How do I fix RHSA-2021:3442?

To fix RHSA-2021:3442, ensure that you update the kpatch-patch package to the recommended versions listed in the advisory.

3

What software is affected by RHSA-2021:3442?

RHSA-2021:3442 affects various versions of the kpatch-patch package on Red Hat Enterprise Linux 8.

4

What is the impact of failing to address RHSA-2021:3442?

Failing to address RHSA-2021:3442 could allow an attacker to gain unauthorized privileges on the affected system.

5

When was RHSA-2021:3442 released?

RHSA-2021:3442 was released as a security update in November 2021.

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