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

Published Jul 20, 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: sizet-to-int conversion vulnerability in the filesystem layer (CVE-2021-33909) kernel: use-after-free in net/bluetooth/hcievent.c when destroying an hcichan (CVE-2021-33034) 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-10.el8_2
4_18_0-193_13_2-1-10.el8_2
redhat/kpatch-patch<4_18_0-193_14_3-1-10.el8_2
4_18_0-193_14_3-1-10.el8_2
redhat/kpatch-patch<4_18_0-193_19_1-1-10.el8_2
4_18_0-193_19_1-1-10.el8_2
redhat/kpatch-patch<4_18_0-193_28_1-1-8.el8_2
4_18_0-193_28_1-1-8.el8_2
redhat/kpatch-patch<4_18_0-193_29_1-1-8.el8_2
4_18_0-193_29_1-1-8.el8_2
redhat/kpatch-patch<4_18_0-193_37_1-1-8.el8_2
4_18_0-193_37_1-1-8.el8_2
redhat/kpatch-patch<4_18_0-193_40_1-1-8.el8_2
4_18_0-193_40_1-1-8.el8_2
redhat/kpatch-patch<4_18_0-193_41_1-1-8.el8_2
4_18_0-193_41_1-1-8.el8_2
redhat/kpatch-patch<4_18_0-193_46_1-1-5.el8_2
4_18_0-193_46_1-1-5.el8_2
redhat/kpatch-patch<4_18_0-193_47_1-1-5.el8_2
4_18_0-193_47_1-1-5.el8_2
redhat/kpatch-patch<4_18_0-193_51_1-1-2.el8_2
4_18_0-193_51_1-1-2.el8_2
redhat/kpatch-patch<4_18_0-193_56_1-1-1.el8_2
4_18_0-193_56_1-1-1.el8_2
redhat/kpatch-patch<4_18_0-193_13_2-1-10.el8_2
4_18_0-193_13_2-1-10.el8_2
redhat/kpatch-patch<4_18_0-193_13_2-debuginfo-1-10.el8_2
4_18_0-193_13_2-debuginfo-1-10.el8_2
redhat/kpatch-patch<4_18_0-193_13_2-debugsource-1-10.el8_2
4_18_0-193_13_2-debugsource-1-10.el8_2
redhat/kpatch-patch<4_18_0-193_14_3-1-10.el8_2
4_18_0-193_14_3-1-10.el8_2
redhat/kpatch-patch<4_18_0-193_14_3-debuginfo-1-10.el8_2
4_18_0-193_14_3-debuginfo-1-10.el8_2
redhat/kpatch-patch<4_18_0-193_14_3-debugsource-1-10.el8_2
4_18_0-193_14_3-debugsource-1-10.el8_2
redhat/kpatch-patch<4_18_0-193_19_1-1-10.el8_2
4_18_0-193_19_1-1-10.el8_2
redhat/kpatch-patch<4_18_0-193_19_1-debuginfo-1-10.el8_2
4_18_0-193_19_1-debuginfo-1-10.el8_2
redhat/kpatch-patch<4_18_0-193_19_1-debugsource-1-10.el8_2
4_18_0-193_19_1-debugsource-1-10.el8_2
redhat/kpatch-patch<4_18_0-193_28_1-1-8.el8_2
4_18_0-193_28_1-1-8.el8_2
redhat/kpatch-patch<4_18_0-193_28_1-debuginfo-1-8.el8_2
4_18_0-193_28_1-debuginfo-1-8.el8_2
redhat/kpatch-patch<4_18_0-193_28_1-debugsource-1-8.el8_2
4_18_0-193_28_1-debugsource-1-8.el8_2
redhat/kpatch-patch<4_18_0-193_29_1-1-8.el8_2
4_18_0-193_29_1-1-8.el8_2
redhat/kpatch-patch<4_18_0-193_29_1-debuginfo-1-8.el8_2
4_18_0-193_29_1-debuginfo-1-8.el8_2
redhat/kpatch-patch<4_18_0-193_29_1-debugsource-1-8.el8_2
4_18_0-193_29_1-debugsource-1-8.el8_2
redhat/kpatch-patch<4_18_0-193_37_1-1-8.el8_2
4_18_0-193_37_1-1-8.el8_2
redhat/kpatch-patch<4_18_0-193_37_1-debuginfo-1-8.el8_2
4_18_0-193_37_1-debuginfo-1-8.el8_2
redhat/kpatch-patch<4_18_0-193_37_1-debugsource-1-8.el8_2
4_18_0-193_37_1-debugsource-1-8.el8_2
redhat/kpatch-patch<4_18_0-193_40_1-1-8.el8_2
4_18_0-193_40_1-1-8.el8_2
redhat/kpatch-patch<4_18_0-193_40_1-debuginfo-1-8.el8_2
4_18_0-193_40_1-debuginfo-1-8.el8_2
redhat/kpatch-patch<4_18_0-193_40_1-debugsource-1-8.el8_2
4_18_0-193_40_1-debugsource-1-8.el8_2
redhat/kpatch-patch<4_18_0-193_41_1-1-8.el8_2
4_18_0-193_41_1-1-8.el8_2
redhat/kpatch-patch<4_18_0-193_41_1-debuginfo-1-8.el8_2
4_18_0-193_41_1-debuginfo-1-8.el8_2
redhat/kpatch-patch<4_18_0-193_41_1-debugsource-1-8.el8_2
4_18_0-193_41_1-debugsource-1-8.el8_2
redhat/kpatch-patch<4_18_0-193_46_1-1-5.el8_2
4_18_0-193_46_1-1-5.el8_2
redhat/kpatch-patch<4_18_0-193_46_1-debuginfo-1-5.el8_2
4_18_0-193_46_1-debuginfo-1-5.el8_2
redhat/kpatch-patch<4_18_0-193_46_1-debugsource-1-5.el8_2
4_18_0-193_46_1-debugsource-1-5.el8_2
redhat/kpatch-patch<4_18_0-193_47_1-1-5.el8_2
4_18_0-193_47_1-1-5.el8_2
redhat/kpatch-patch<4_18_0-193_47_1-debuginfo-1-5.el8_2
4_18_0-193_47_1-debuginfo-1-5.el8_2
redhat/kpatch-patch<4_18_0-193_47_1-debugsource-1-5.el8_2
4_18_0-193_47_1-debugsource-1-5.el8_2
redhat/kpatch-patch<4_18_0-193_51_1-1-2.el8_2
4_18_0-193_51_1-1-2.el8_2
redhat/kpatch-patch<4_18_0-193_51_1-debuginfo-1-2.el8_2
4_18_0-193_51_1-debuginfo-1-2.el8_2
redhat/kpatch-patch<4_18_0-193_51_1-debugsource-1-2.el8_2
4_18_0-193_51_1-debugsource-1-2.el8_2
redhat/kpatch-patch<4_18_0-193_56_1-1-1.el8_2
4_18_0-193_56_1-1-1.el8_2
redhat/kpatch-patch<4_18_0-193_56_1-debuginfo-1-1.el8_2
4_18_0-193_56_1-debuginfo-1-1.el8_2
redhat/kpatch-patch<4_18_0-193_56_1-debugsource-1-1.el8_2
4_18_0-193_56_1-debugsource-1-1.el8_2
redhat/kpatch-patch<4_18_0-193_13_2-1-10.el8_2
4_18_0-193_13_2-1-10.el8_2
redhat/kpatch-patch<4_18_0-193_13_2-debuginfo-1-10.el8_2
4_18_0-193_13_2-debuginfo-1-10.el8_2
redhat/kpatch-patch<4_18_0-193_13_2-debugsource-1-10.el8_2
4_18_0-193_13_2-debugsource-1-10.el8_2
redhat/kpatch-patch<4_18_0-193_14_3-1-10.el8_2
4_18_0-193_14_3-1-10.el8_2
redhat/kpatch-patch<4_18_0-193_14_3-debuginfo-1-10.el8_2
4_18_0-193_14_3-debuginfo-1-10.el8_2
redhat/kpatch-patch<4_18_0-193_14_3-debugsource-1-10.el8_2
4_18_0-193_14_3-debugsource-1-10.el8_2
redhat/kpatch-patch<4_18_0-193_19_1-1-10.el8_2
4_18_0-193_19_1-1-10.el8_2
redhat/kpatch-patch<4_18_0-193_19_1-debuginfo-1-10.el8_2
4_18_0-193_19_1-debuginfo-1-10.el8_2
redhat/kpatch-patch<4_18_0-193_19_1-debugsource-1-10.el8_2
4_18_0-193_19_1-debugsource-1-10.el8_2
redhat/kpatch-patch<4_18_0-193_28_1-1-8.el8_2
4_18_0-193_28_1-1-8.el8_2
redhat/kpatch-patch<4_18_0-193_28_1-debuginfo-1-8.el8_2
4_18_0-193_28_1-debuginfo-1-8.el8_2
redhat/kpatch-patch<4_18_0-193_28_1-debugsource-1-8.el8_2
4_18_0-193_28_1-debugsource-1-8.el8_2
redhat/kpatch-patch<4_18_0-193_29_1-1-8.el8_2
4_18_0-193_29_1-1-8.el8_2
redhat/kpatch-patch<4_18_0-193_29_1-debuginfo-1-8.el8_2
4_18_0-193_29_1-debuginfo-1-8.el8_2
redhat/kpatch-patch<4_18_0-193_29_1-debugsource-1-8.el8_2
4_18_0-193_29_1-debugsource-1-8.el8_2
redhat/kpatch-patch<4_18_0-193_37_1-1-8.el8_2
4_18_0-193_37_1-1-8.el8_2
redhat/kpatch-patch<4_18_0-193_37_1-debuginfo-1-8.el8_2
4_18_0-193_37_1-debuginfo-1-8.el8_2
redhat/kpatch-patch<4_18_0-193_37_1-debugsource-1-8.el8_2
4_18_0-193_37_1-debugsource-1-8.el8_2
redhat/kpatch-patch<4_18_0-193_40_1-1-8.el8_2
4_18_0-193_40_1-1-8.el8_2
redhat/kpatch-patch<4_18_0-193_40_1-debuginfo-1-8.el8_2
4_18_0-193_40_1-debuginfo-1-8.el8_2
redhat/kpatch-patch<4_18_0-193_40_1-debugsource-1-8.el8_2
4_18_0-193_40_1-debugsource-1-8.el8_2
redhat/kpatch-patch<4_18_0-193_41_1-1-8.el8_2
4_18_0-193_41_1-1-8.el8_2
redhat/kpatch-patch<4_18_0-193_41_1-debuginfo-1-8.el8_2
4_18_0-193_41_1-debuginfo-1-8.el8_2
redhat/kpatch-patch<4_18_0-193_41_1-debugsource-1-8.el8_2
4_18_0-193_41_1-debugsource-1-8.el8_2
redhat/kpatch-patch<4_18_0-193_46_1-1-5.el8_2
4_18_0-193_46_1-1-5.el8_2
redhat/kpatch-patch<4_18_0-193_46_1-debuginfo-1-5.el8_2
4_18_0-193_46_1-debuginfo-1-5.el8_2
redhat/kpatch-patch<4_18_0-193_46_1-debugsource-1-5.el8_2
4_18_0-193_46_1-debugsource-1-5.el8_2
redhat/kpatch-patch<4_18_0-193_47_1-1-5.el8_2
4_18_0-193_47_1-1-5.el8_2
redhat/kpatch-patch<4_18_0-193_47_1-debuginfo-1-5.el8_2
4_18_0-193_47_1-debuginfo-1-5.el8_2
redhat/kpatch-patch<4_18_0-193_47_1-debugsource-1-5.el8_2
4_18_0-193_47_1-debugsource-1-5.el8_2
redhat/kpatch-patch<4_18_0-193_51_1-1-2.el8_2
4_18_0-193_51_1-1-2.el8_2
redhat/kpatch-patch<4_18_0-193_51_1-debuginfo-1-2.el8_2
4_18_0-193_51_1-debuginfo-1-2.el8_2
redhat/kpatch-patch<4_18_0-193_51_1-debugsource-1-2.el8_2
4_18_0-193_51_1-debugsource-1-2.el8_2
redhat/kpatch-patch<4_18_0-193_56_1-1-1.el8_2
4_18_0-193_56_1-1-1.el8_2
redhat/kpatch-patch<4_18_0-193_56_1-debuginfo-1-1.el8_2
4_18_0-193_56_1-debuginfo-1-1.el8_2
redhat/kpatch-patch<4_18_0-193_56_1-debugsource-1-1.el8_2
4_18_0-193_56_1-debugsource-1-1.el8_2

Remediation

Event History

Jun 4, 2026
Advisory Published
via Red Hat·08:20 PM
Data Sourced
via Red Hat·08:20 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:2720?

The severity of RHSA-2021:2720 is classified as important.

2

How do I fix RHSA-2021:2720?

To fix RHSA-2021:2720, update the kpatch-patch package to the latest version addressing the vulnerability.

3

What vulnerabilities are addressed in RHSA-2021:2720?

RHSA-2021:2720 addresses a size_t-to-int conversion vulnerability and a use-after-free vulnerability in the kernel.

4

Which versions of the kpatch-patch package are affected by RHSA-2021:2720?

Affected versions include various iterations of the kpatch-patch package up to the specified version types listed in the advisory.

5

Is the kpatch-patch package for RHSA-2021:2720 available for multiple architectures?

Yes, the kpatch-patch package for RHSA-2021:2720 is available for multiple architectures, including x86_64 and ppc64le.

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