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

Published Aug 31, 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: Improper handling of VMIO|VMPFNMAP vmas in KVM can bypass RO checks (CVE-2021-22543) kernel: out-of-bounds write in xtcompattargetfromuser() in net/netfilter/xtables.c (CVE-2021-22555) kernel: race condition for removal of the HCI controller (CVE-2021-32399) 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

77 affected componentsFixes available
redhat/kpatch-patch<4_18_0-193_19_1-1-11.el8_2
4_18_0-193_19_1-1-11.el8_2
redhat/kpatch-patch<4_18_0-193_28_1-1-9.el8_2
4_18_0-193_28_1-1-9.el8_2
redhat/kpatch-patch<4_18_0-193_29_1-1-9.el8_2
4_18_0-193_29_1-1-9.el8_2
redhat/kpatch-patch<4_18_0-193_37_1-1-9.el8_2
4_18_0-193_37_1-1-9.el8_2
redhat/kpatch-patch<4_18_0-193_40_1-1-9.el8_2
4_18_0-193_40_1-1-9.el8_2
redhat/kpatch-patch<4_18_0-193_41_1-1-9.el8_2
4_18_0-193_41_1-1-9.el8_2
redhat/kpatch-patch<4_18_0-193_46_1-1-6.el8_2
4_18_0-193_46_1-1-6.el8_2
redhat/kpatch-patch<4_18_0-193_47_1-1-6.el8_2
4_18_0-193_47_1-1-6.el8_2
redhat/kpatch-patch<4_18_0-193_51_1-1-3.el8_2
4_18_0-193_51_1-1-3.el8_2
redhat/kpatch-patch<4_18_0-193_56_1-1-2.el8_2
4_18_0-193_56_1-1-2.el8_2
redhat/kpatch-patch<4_18_0-193_60_2-1-1.el8_2
4_18_0-193_60_2-1-1.el8_2
redhat/kpatch-patch<4_18_0-193_19_1-1-11.el8_2
4_18_0-193_19_1-1-11.el8_2
redhat/kpatch-patch<4_18_0-193_19_1-debuginfo-1-11.el8_2
4_18_0-193_19_1-debuginfo-1-11.el8_2
redhat/kpatch-patch<4_18_0-193_19_1-debugsource-1-11.el8_2
4_18_0-193_19_1-debugsource-1-11.el8_2
redhat/kpatch-patch<4_18_0-193_28_1-1-9.el8_2
4_18_0-193_28_1-1-9.el8_2
redhat/kpatch-patch<4_18_0-193_28_1-debuginfo-1-9.el8_2
4_18_0-193_28_1-debuginfo-1-9.el8_2
redhat/kpatch-patch<4_18_0-193_28_1-debugsource-1-9.el8_2
4_18_0-193_28_1-debugsource-1-9.el8_2
redhat/kpatch-patch<4_18_0-193_29_1-1-9.el8_2
4_18_0-193_29_1-1-9.el8_2
redhat/kpatch-patch<4_18_0-193_29_1-debuginfo-1-9.el8_2
4_18_0-193_29_1-debuginfo-1-9.el8_2
redhat/kpatch-patch<4_18_0-193_29_1-debugsource-1-9.el8_2
4_18_0-193_29_1-debugsource-1-9.el8_2
redhat/kpatch-patch<4_18_0-193_37_1-1-9.el8_2
4_18_0-193_37_1-1-9.el8_2
redhat/kpatch-patch<4_18_0-193_37_1-debuginfo-1-9.el8_2
4_18_0-193_37_1-debuginfo-1-9.el8_2
redhat/kpatch-patch<4_18_0-193_37_1-debugsource-1-9.el8_2
4_18_0-193_37_1-debugsource-1-9.el8_2
redhat/kpatch-patch<4_18_0-193_40_1-1-9.el8_2
4_18_0-193_40_1-1-9.el8_2
redhat/kpatch-patch<4_18_0-193_40_1-debuginfo-1-9.el8_2
4_18_0-193_40_1-debuginfo-1-9.el8_2
redhat/kpatch-patch<4_18_0-193_40_1-debugsource-1-9.el8_2
4_18_0-193_40_1-debugsource-1-9.el8_2
redhat/kpatch-patch<4_18_0-193_41_1-1-9.el8_2
4_18_0-193_41_1-1-9.el8_2
redhat/kpatch-patch<4_18_0-193_41_1-debuginfo-1-9.el8_2
4_18_0-193_41_1-debuginfo-1-9.el8_2
redhat/kpatch-patch<4_18_0-193_41_1-debugsource-1-9.el8_2
4_18_0-193_41_1-debugsource-1-9.el8_2
redhat/kpatch-patch<4_18_0-193_46_1-1-6.el8_2
4_18_0-193_46_1-1-6.el8_2
redhat/kpatch-patch<4_18_0-193_46_1-debuginfo-1-6.el8_2
4_18_0-193_46_1-debuginfo-1-6.el8_2
redhat/kpatch-patch<4_18_0-193_46_1-debugsource-1-6.el8_2
4_18_0-193_46_1-debugsource-1-6.el8_2
redhat/kpatch-patch<4_18_0-193_47_1-1-6.el8_2
4_18_0-193_47_1-1-6.el8_2
redhat/kpatch-patch<4_18_0-193_47_1-debuginfo-1-6.el8_2
4_18_0-193_47_1-debuginfo-1-6.el8_2
redhat/kpatch-patch<4_18_0-193_47_1-debugsource-1-6.el8_2
4_18_0-193_47_1-debugsource-1-6.el8_2
redhat/kpatch-patch<4_18_0-193_51_1-1-3.el8_2
4_18_0-193_51_1-1-3.el8_2
redhat/kpatch-patch<4_18_0-193_51_1-debuginfo-1-3.el8_2
4_18_0-193_51_1-debuginfo-1-3.el8_2
redhat/kpatch-patch<4_18_0-193_51_1-debugsource-1-3.el8_2
4_18_0-193_51_1-debugsource-1-3.el8_2
redhat/kpatch-patch<4_18_0-193_56_1-1-2.el8_2
4_18_0-193_56_1-1-2.el8_2
redhat/kpatch-patch<4_18_0-193_56_1-debuginfo-1-2.el8_2
4_18_0-193_56_1-debuginfo-1-2.el8_2
redhat/kpatch-patch<4_18_0-193_56_1-debugsource-1-2.el8_2
4_18_0-193_56_1-debugsource-1-2.el8_2
redhat/kpatch-patch<4_18_0-193_60_2-1-1.el8_2
4_18_0-193_60_2-1-1.el8_2
redhat/kpatch-patch<4_18_0-193_60_2-debuginfo-1-1.el8_2
4_18_0-193_60_2-debuginfo-1-1.el8_2
redhat/kpatch-patch<4_18_0-193_60_2-debugsource-1-1.el8_2
4_18_0-193_60_2-debugsource-1-1.el8_2
redhat/kpatch-patch<4_18_0-193_19_1-1-11.el8_2
4_18_0-193_19_1-1-11.el8_2
redhat/kpatch-patch<4_18_0-193_19_1-debuginfo-1-11.el8_2
4_18_0-193_19_1-debuginfo-1-11.el8_2
redhat/kpatch-patch<4_18_0-193_19_1-debugsource-1-11.el8_2
4_18_0-193_19_1-debugsource-1-11.el8_2
redhat/kpatch-patch<4_18_0-193_28_1-1-9.el8_2
4_18_0-193_28_1-1-9.el8_2
redhat/kpatch-patch<4_18_0-193_28_1-debuginfo-1-9.el8_2
4_18_0-193_28_1-debuginfo-1-9.el8_2
redhat/kpatch-patch<4_18_0-193_28_1-debugsource-1-9.el8_2
4_18_0-193_28_1-debugsource-1-9.el8_2
redhat/kpatch-patch<4_18_0-193_29_1-1-9.el8_2
4_18_0-193_29_1-1-9.el8_2
redhat/kpatch-patch<4_18_0-193_29_1-debuginfo-1-9.el8_2
4_18_0-193_29_1-debuginfo-1-9.el8_2
redhat/kpatch-patch<4_18_0-193_29_1-debugsource-1-9.el8_2
4_18_0-193_29_1-debugsource-1-9.el8_2
redhat/kpatch-patch<4_18_0-193_37_1-1-9.el8_2
4_18_0-193_37_1-1-9.el8_2
redhat/kpatch-patch<4_18_0-193_37_1-debuginfo-1-9.el8_2
4_18_0-193_37_1-debuginfo-1-9.el8_2
redhat/kpatch-patch<4_18_0-193_37_1-debugsource-1-9.el8_2
4_18_0-193_37_1-debugsource-1-9.el8_2
redhat/kpatch-patch<4_18_0-193_40_1-1-9.el8_2
4_18_0-193_40_1-1-9.el8_2
redhat/kpatch-patch<4_18_0-193_40_1-debuginfo-1-9.el8_2
4_18_0-193_40_1-debuginfo-1-9.el8_2
redhat/kpatch-patch<4_18_0-193_40_1-debugsource-1-9.el8_2
4_18_0-193_40_1-debugsource-1-9.el8_2
redhat/kpatch-patch<4_18_0-193_41_1-1-9.el8_2
4_18_0-193_41_1-1-9.el8_2
redhat/kpatch-patch<4_18_0-193_41_1-debuginfo-1-9.el8_2
4_18_0-193_41_1-debuginfo-1-9.el8_2
redhat/kpatch-patch<4_18_0-193_41_1-debugsource-1-9.el8_2
4_18_0-193_41_1-debugsource-1-9.el8_2
redhat/kpatch-patch<4_18_0-193_46_1-1-6.el8_2
4_18_0-193_46_1-1-6.el8_2
redhat/kpatch-patch<4_18_0-193_46_1-debuginfo-1-6.el8_2
4_18_0-193_46_1-debuginfo-1-6.el8_2
redhat/kpatch-patch<4_18_0-193_46_1-debugsource-1-6.el8_2
4_18_0-193_46_1-debugsource-1-6.el8_2
redhat/kpatch-patch<4_18_0-193_47_1-1-6.el8_2
4_18_0-193_47_1-1-6.el8_2
redhat/kpatch-patch<4_18_0-193_47_1-debuginfo-1-6.el8_2
4_18_0-193_47_1-debuginfo-1-6.el8_2
redhat/kpatch-patch<4_18_0-193_47_1-debugsource-1-6.el8_2
4_18_0-193_47_1-debugsource-1-6.el8_2
redhat/kpatch-patch<4_18_0-193_51_1-1-3.el8_2
4_18_0-193_51_1-1-3.el8_2
redhat/kpatch-patch<4_18_0-193_51_1-debuginfo-1-3.el8_2
4_18_0-193_51_1-debuginfo-1-3.el8_2
redhat/kpatch-patch<4_18_0-193_51_1-debugsource-1-3.el8_2
4_18_0-193_51_1-debugsource-1-3.el8_2
redhat/kpatch-patch<4_18_0-193_56_1-1-2.el8_2
4_18_0-193_56_1-1-2.el8_2
redhat/kpatch-patch<4_18_0-193_56_1-debuginfo-1-2.el8_2
4_18_0-193_56_1-debuginfo-1-2.el8_2
redhat/kpatch-patch<4_18_0-193_56_1-debugsource-1-2.el8_2
4_18_0-193_56_1-debugsource-1-2.el8_2
redhat/kpatch-patch<4_18_0-193_60_2-1-1.el8_2
4_18_0-193_60_2-1-1.el8_2
redhat/kpatch-patch<4_18_0-193_60_2-debuginfo-1-1.el8_2
4_18_0-193_60_2-debuginfo-1-1.el8_2
redhat/kpatch-patch<4_18_0-193_60_2-debugsource-1-1.el8_2
4_18_0-193_60_2-debugsource-1-1.el8_2

Remediation

Event History

Mar 2, 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:3380?

The severity of RHSA-2021:3380 is classified as important due to the potential local privilege escalation.

2

How do I fix RHSA-2021:3380?

To fix RHSA-2021:3380, upgrade to the latest kpatch-patch versions provided by Red Hat.

3

What vulnerabilities are addressed in RHSA-2021:3380?

RHSA-2021:3380 addresses a race condition in net/can/bcm.c that leads to local privilege escalation (CVE-2021-3609).

4

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

Affected versions include kpatch-patch versions prior to 4_18_0-193_19_1-1-11.el8_2 and subsequent updates listed in the advisory.

5

Is a reboot required after applying the fix for RHSA-2021:3380?

Yes, a reboot may be necessary to fully apply the kernel live patch and ensure security updates take effect.

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