RHSA-2021:2668: Important: kpatch-patch security update
Published Jul 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: 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
56 affected componentsFixes available
redhat/kpatch-patch<4_18_0-147_24_2-1-10.el8_1
4_18_0-147_24_2-1-10.el8_1
redhat/kpatch-patch<4_18_0-147_27_1-1-10.el8_1
4_18_0-147_27_1-1-10.el8_1
redhat/kpatch-patch<4_18_0-147_32_1-1-8.el8_1
4_18_0-147_32_1-1-8.el8_1
redhat/kpatch-patch<4_18_0-147_34_1-1-8.el8_1
4_18_0-147_34_1-1-8.el8_1
redhat/kpatch-patch<4_18_0-147_38_1-1-7.el8_1
4_18_0-147_38_1-1-7.el8_1
redhat/kpatch-patch<4_18_0-147_43_1-1-5.el8_1
4_18_0-147_43_1-1-5.el8_1
redhat/kpatch-patch<4_18_0-147_44_1-1-4.el8_1
4_18_0-147_44_1-1-4.el8_1
redhat/kpatch-patch<4_18_0-147_48_1-1-1.el8_1
4_18_0-147_48_1-1-1.el8_1
redhat/kpatch-patch<4_18_0-147_24_2-1-10.el8_1
4_18_0-147_24_2-1-10.el8_1
redhat/kpatch-patch<4_18_0-147_24_2-debuginfo-1-10.el8_1
4_18_0-147_24_2-debuginfo-1-10.el8_1
redhat/kpatch-patch<4_18_0-147_24_2-debugsource-1-10.el8_1
4_18_0-147_24_2-debugsource-1-10.el8_1
redhat/kpatch-patch<4_18_0-147_27_1-1-10.el8_1
4_18_0-147_27_1-1-10.el8_1
redhat/kpatch-patch<4_18_0-147_27_1-debuginfo-1-10.el8_1
4_18_0-147_27_1-debuginfo-1-10.el8_1
redhat/kpatch-patch<4_18_0-147_27_1-debugsource-1-10.el8_1
4_18_0-147_27_1-debugsource-1-10.el8_1
redhat/kpatch-patch<4_18_0-147_32_1-1-8.el8_1
4_18_0-147_32_1-1-8.el8_1
redhat/kpatch-patch<4_18_0-147_32_1-debuginfo-1-8.el8_1
4_18_0-147_32_1-debuginfo-1-8.el8_1
redhat/kpatch-patch<4_18_0-147_32_1-debugsource-1-8.el8_1
4_18_0-147_32_1-debugsource-1-8.el8_1
redhat/kpatch-patch<4_18_0-147_34_1-1-8.el8_1
4_18_0-147_34_1-1-8.el8_1
redhat/kpatch-patch<4_18_0-147_34_1-debuginfo-1-8.el8_1
4_18_0-147_34_1-debuginfo-1-8.el8_1
redhat/kpatch-patch<4_18_0-147_34_1-debugsource-1-8.el8_1
4_18_0-147_34_1-debugsource-1-8.el8_1
redhat/kpatch-patch<4_18_0-147_38_1-1-7.el8_1
4_18_0-147_38_1-1-7.el8_1
redhat/kpatch-patch<4_18_0-147_38_1-debuginfo-1-7.el8_1
4_18_0-147_38_1-debuginfo-1-7.el8_1
redhat/kpatch-patch<4_18_0-147_38_1-debugsource-1-7.el8_1
4_18_0-147_38_1-debugsource-1-7.el8_1
redhat/kpatch-patch<4_18_0-147_43_1-1-5.el8_1
4_18_0-147_43_1-1-5.el8_1
redhat/kpatch-patch<4_18_0-147_43_1-debuginfo-1-5.el8_1
4_18_0-147_43_1-debuginfo-1-5.el8_1
redhat/kpatch-patch<4_18_0-147_43_1-debugsource-1-5.el8_1
4_18_0-147_43_1-debugsource-1-5.el8_1
redhat/kpatch-patch<4_18_0-147_44_1-1-4.el8_1
4_18_0-147_44_1-1-4.el8_1
redhat/kpatch-patch<4_18_0-147_44_1-debuginfo-1-4.el8_1
4_18_0-147_44_1-debuginfo-1-4.el8_1
redhat/kpatch-patch<4_18_0-147_44_1-debugsource-1-4.el8_1
4_18_0-147_44_1-debugsource-1-4.el8_1
redhat/kpatch-patch<4_18_0-147_48_1-1-1.el8_1
4_18_0-147_48_1-1-1.el8_1
redhat/kpatch-patch<4_18_0-147_48_1-debuginfo-1-1.el8_1
4_18_0-147_48_1-debuginfo-1-1.el8_1
redhat/kpatch-patch<4_18_0-147_48_1-debugsource-1-1.el8_1
4_18_0-147_48_1-debugsource-1-1.el8_1
redhat/kpatch-patch<4_18_0-147_24_2-1-10.el8_1
4_18_0-147_24_2-1-10.el8_1
redhat/kpatch-patch<4_18_0-147_24_2-debuginfo-1-10.el8_1
4_18_0-147_24_2-debuginfo-1-10.el8_1
redhat/kpatch-patch<4_18_0-147_24_2-debugsource-1-10.el8_1
4_18_0-147_24_2-debugsource-1-10.el8_1
redhat/kpatch-patch<4_18_0-147_27_1-1-10.el8_1
4_18_0-147_27_1-1-10.el8_1
redhat/kpatch-patch<4_18_0-147_27_1-debuginfo-1-10.el8_1
4_18_0-147_27_1-debuginfo-1-10.el8_1
redhat/kpatch-patch<4_18_0-147_27_1-debugsource-1-10.el8_1
4_18_0-147_27_1-debugsource-1-10.el8_1
redhat/kpatch-patch<4_18_0-147_32_1-1-8.el8_1
4_18_0-147_32_1-1-8.el8_1
redhat/kpatch-patch<4_18_0-147_32_1-debuginfo-1-8.el8_1
4_18_0-147_32_1-debuginfo-1-8.el8_1
redhat/kpatch-patch<4_18_0-147_32_1-debugsource-1-8.el8_1
4_18_0-147_32_1-debugsource-1-8.el8_1
redhat/kpatch-patch<4_18_0-147_34_1-1-8.el8_1
4_18_0-147_34_1-1-8.el8_1
redhat/kpatch-patch<4_18_0-147_34_1-debuginfo-1-8.el8_1
4_18_0-147_34_1-debuginfo-1-8.el8_1
redhat/kpatch-patch<4_18_0-147_34_1-debugsource-1-8.el8_1
4_18_0-147_34_1-debugsource-1-8.el8_1
redhat/kpatch-patch<4_18_0-147_38_1-1-7.el8_1
4_18_0-147_38_1-1-7.el8_1
redhat/kpatch-patch<4_18_0-147_38_1-debuginfo-1-7.el8_1
4_18_0-147_38_1-debuginfo-1-7.el8_1
redhat/kpatch-patch<4_18_0-147_38_1-debugsource-1-7.el8_1
4_18_0-147_38_1-debugsource-1-7.el8_1
redhat/kpatch-patch<4_18_0-147_43_1-1-5.el8_1
4_18_0-147_43_1-1-5.el8_1
redhat/kpatch-patch<4_18_0-147_43_1-debuginfo-1-5.el8_1
4_18_0-147_43_1-debuginfo-1-5.el8_1
redhat/kpatch-patch<4_18_0-147_43_1-debugsource-1-5.el8_1
4_18_0-147_43_1-debugsource-1-5.el8_1
redhat/kpatch-patch<4_18_0-147_44_1-1-4.el8_1
4_18_0-147_44_1-1-4.el8_1
redhat/kpatch-patch<4_18_0-147_44_1-debuginfo-1-4.el8_1
4_18_0-147_44_1-debuginfo-1-4.el8_1
redhat/kpatch-patch<4_18_0-147_44_1-debugsource-1-4.el8_1
4_18_0-147_44_1-debugsource-1-4.el8_1
redhat/kpatch-patch<4_18_0-147_48_1-1-1.el8_1
4_18_0-147_48_1-1-1.el8_1
redhat/kpatch-patch<4_18_0-147_48_1-debuginfo-1-1.el8_1
4_18_0-147_48_1-debuginfo-1-1.el8_1
redhat/kpatch-patch<4_18_0-147_48_1-debugsource-1-1.el8_1
4_18_0-147_48_1-debugsource-1-1.el8_1
Remediation
Event History
May 14, 2026
Advisory Published
via Red Hat·06:47 PM
Data Sourced
via Red Hat·06:47 PM
RemedyDescriptionAffected Software
Frequently Asked Questions
1
What is the severity of RHSA-2021:2668?
The severity of RHSA-2021:2668 is classified as important.
2
What vulnerabilities are addressed in RHSA-2021:2668?
RHSA-2021:2668 addresses a use-after-free vulnerability in net/bluetooth/hci_event.c when destroying an hci_chan (CVE-2021-33034).
3
How do I fix RHSA-2021:2668?
To fix RHSA-2021:2668, apply the recommended update for the kpatch-patch package, version 4_18_0-147_24_2-1-10.el8_1 or later.
4
Which versions of kpatch-patch are affected by RHSA-2021:2668?
Versions of kpatch-patch prior to 4_18_0-147_24_2-1-10.el8_1 are affected by RHSA-2021:2668.
5
Is there a specific package I need to update for RHSA-2021:2668?
Yes, you need to update the kpatch-patch package to address the vulnerability detailed in RHSA-2021:2668.