RHSA-2021:2099: Important: kpatch-patch security update
Published May 25, 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.<br>Security Fix(es):<br><li> kernel: use after free in eventpoll.c may lead to escalation of privilege (CVE-2020-0466)</li> <li> kernel: SCSI target (LIO) write to any block on ILO backstore (CVE-2020-28374)</li> <li> kernel: Use after free via PI futex state (CVE-2021-3347)</li> 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_20_1-1-11.el8_1
4_18_0-147_20_1-1-11.el8_1
redhat/kpatch-patch<4_18_0-147_24_2-1-9.el8_1
4_18_0-147_24_2-1-9.el8_1
redhat/kpatch-patch<4_18_0-147_27_1-1-9.el8_1
4_18_0-147_27_1-1-9.el8_1
redhat/kpatch-patch<4_18_0-147_32_1-1-7.el8_1
4_18_0-147_32_1-1-7.el8_1
redhat/kpatch-patch<4_18_0-147_34_1-1-7.el8_1
4_18_0-147_34_1-1-7.el8_1
redhat/kpatch-patch<4_18_0-147_38_1-1-6.el8_1
4_18_0-147_38_1-1-6.el8_1
redhat/kpatch-patch<4_18_0-147_43_1-1-4.el8_1
4_18_0-147_43_1-1-4.el8_1
redhat/kpatch-patch<4_18_0-147_44_1-1-3.el8_1
4_18_0-147_44_1-1-3.el8_1
redhat/kpatch-patch<4_18_0-147_20_1-1-11.el8_1
4_18_0-147_20_1-1-11.el8_1
redhat/kpatch-patch<4_18_0-147_20_1-debuginfo-1-11.el8_1
4_18_0-147_20_1-debuginfo-1-11.el8_1
redhat/kpatch-patch<4_18_0-147_20_1-debugsource-1-11.el8_1
4_18_0-147_20_1-debugsource-1-11.el8_1
redhat/kpatch-patch<4_18_0-147_24_2-1-9.el8_1
4_18_0-147_24_2-1-9.el8_1
redhat/kpatch-patch<4_18_0-147_24_2-debuginfo-1-9.el8_1
4_18_0-147_24_2-debuginfo-1-9.el8_1
redhat/kpatch-patch<4_18_0-147_24_2-debugsource-1-9.el8_1
4_18_0-147_24_2-debugsource-1-9.el8_1
redhat/kpatch-patch<4_18_0-147_27_1-1-9.el8_1
4_18_0-147_27_1-1-9.el8_1
redhat/kpatch-patch<4_18_0-147_27_1-debuginfo-1-9.el8_1
4_18_0-147_27_1-debuginfo-1-9.el8_1
redhat/kpatch-patch<4_18_0-147_27_1-debugsource-1-9.el8_1
4_18_0-147_27_1-debugsource-1-9.el8_1
redhat/kpatch-patch<4_18_0-147_32_1-1-7.el8_1
4_18_0-147_32_1-1-7.el8_1
redhat/kpatch-patch<4_18_0-147_32_1-debuginfo-1-7.el8_1
4_18_0-147_32_1-debuginfo-1-7.el8_1
redhat/kpatch-patch<4_18_0-147_32_1-debugsource-1-7.el8_1
4_18_0-147_32_1-debugsource-1-7.el8_1
redhat/kpatch-patch<4_18_0-147_34_1-1-7.el8_1
4_18_0-147_34_1-1-7.el8_1
redhat/kpatch-patch<4_18_0-147_34_1-debuginfo-1-7.el8_1
4_18_0-147_34_1-debuginfo-1-7.el8_1
redhat/kpatch-patch<4_18_0-147_34_1-debugsource-1-7.el8_1
4_18_0-147_34_1-debugsource-1-7.el8_1
redhat/kpatch-patch<4_18_0-147_38_1-1-6.el8_1
4_18_0-147_38_1-1-6.el8_1
redhat/kpatch-patch<4_18_0-147_38_1-debuginfo-1-6.el8_1
4_18_0-147_38_1-debuginfo-1-6.el8_1
redhat/kpatch-patch<4_18_0-147_38_1-debugsource-1-6.el8_1
4_18_0-147_38_1-debugsource-1-6.el8_1
redhat/kpatch-patch<4_18_0-147_43_1-1-4.el8_1
4_18_0-147_43_1-1-4.el8_1
redhat/kpatch-patch<4_18_0-147_43_1-debuginfo-1-4.el8_1
4_18_0-147_43_1-debuginfo-1-4.el8_1
redhat/kpatch-patch<4_18_0-147_43_1-debugsource-1-4.el8_1
4_18_0-147_43_1-debugsource-1-4.el8_1
redhat/kpatch-patch<4_18_0-147_44_1-1-3.el8_1
4_18_0-147_44_1-1-3.el8_1
redhat/kpatch-patch<4_18_0-147_44_1-debuginfo-1-3.el8_1
4_18_0-147_44_1-debuginfo-1-3.el8_1
redhat/kpatch-patch<4_18_0-147_44_1-debugsource-1-3.el8_1
4_18_0-147_44_1-debugsource-1-3.el8_1
redhat/kpatch-patch<4_18_0-147_20_1-1-11.el8_1
4_18_0-147_20_1-1-11.el8_1
redhat/kpatch-patch<4_18_0-147_20_1-debuginfo-1-11.el8_1
4_18_0-147_20_1-debuginfo-1-11.el8_1
redhat/kpatch-patch<4_18_0-147_20_1-debugsource-1-11.el8_1
4_18_0-147_20_1-debugsource-1-11.el8_1
redhat/kpatch-patch<4_18_0-147_24_2-1-9.el8_1
4_18_0-147_24_2-1-9.el8_1
redhat/kpatch-patch<4_18_0-147_24_2-debuginfo-1-9.el8_1
4_18_0-147_24_2-debuginfo-1-9.el8_1
redhat/kpatch-patch<4_18_0-147_24_2-debugsource-1-9.el8_1
4_18_0-147_24_2-debugsource-1-9.el8_1
redhat/kpatch-patch<4_18_0-147_27_1-1-9.el8_1
4_18_0-147_27_1-1-9.el8_1
redhat/kpatch-patch<4_18_0-147_27_1-debuginfo-1-9.el8_1
4_18_0-147_27_1-debuginfo-1-9.el8_1
redhat/kpatch-patch<4_18_0-147_27_1-debugsource-1-9.el8_1
4_18_0-147_27_1-debugsource-1-9.el8_1
redhat/kpatch-patch<4_18_0-147_32_1-1-7.el8_1
4_18_0-147_32_1-1-7.el8_1
redhat/kpatch-patch<4_18_0-147_32_1-debuginfo-1-7.el8_1
4_18_0-147_32_1-debuginfo-1-7.el8_1
redhat/kpatch-patch<4_18_0-147_32_1-debugsource-1-7.el8_1
4_18_0-147_32_1-debugsource-1-7.el8_1
redhat/kpatch-patch<4_18_0-147_34_1-1-7.el8_1
4_18_0-147_34_1-1-7.el8_1
redhat/kpatch-patch<4_18_0-147_34_1-debuginfo-1-7.el8_1
4_18_0-147_34_1-debuginfo-1-7.el8_1
redhat/kpatch-patch<4_18_0-147_34_1-debugsource-1-7.el8_1
4_18_0-147_34_1-debugsource-1-7.el8_1
redhat/kpatch-patch<4_18_0-147_38_1-1-6.el8_1
4_18_0-147_38_1-1-6.el8_1
redhat/kpatch-patch<4_18_0-147_38_1-debuginfo-1-6.el8_1
4_18_0-147_38_1-debuginfo-1-6.el8_1
redhat/kpatch-patch<4_18_0-147_38_1-debugsource-1-6.el8_1
4_18_0-147_38_1-debugsource-1-6.el8_1
redhat/kpatch-patch<4_18_0-147_43_1-1-4.el8_1
4_18_0-147_43_1-1-4.el8_1
redhat/kpatch-patch<4_18_0-147_43_1-debuginfo-1-4.el8_1
4_18_0-147_43_1-debuginfo-1-4.el8_1
redhat/kpatch-patch<4_18_0-147_43_1-debugsource-1-4.el8_1
4_18_0-147_43_1-debugsource-1-4.el8_1
redhat/kpatch-patch<4_18_0-147_44_1-1-3.el8_1
4_18_0-147_44_1-1-3.el8_1
redhat/kpatch-patch<4_18_0-147_44_1-debuginfo-1-3.el8_1
4_18_0-147_44_1-debuginfo-1-3.el8_1
redhat/kpatch-patch<4_18_0-147_44_1-debugsource-1-3.el8_1
4_18_0-147_44_1-debugsource-1-3.el8_1
Remediation
Event History
Jun 20, 2024
Advisory Published
via Red Hat·01:28 AM
Frequently Asked Questions
1
What is the severity of RHSA-2021:2099?
The severity of RHSA-2021:2099 is classified as important due to a use-after-free vulnerability that may lead to privilege escalation.
2
How do I fix RHSA-2021:2099?
To fix RHSA-2021:2099, you should update the kpatch-patch package to the latest recommended version as specified in the advisory.
3
What does the RHSA-2021:2099 vulnerability affect?
The RHSA-2021:2099 vulnerability affects the kernel live patch module used in the Red Hat Enterprise Linux operating system.
4
Is the RHSA-2021:2099 vulnerability remote?
The RHSA-2021:2099 vulnerability is not remote; it requires local access to exploit the use-after-free condition.
5
What is CVE-2020-0466 related to RHSA-2021:2099?
CVE-2020-0466 is the identifier for the specific vulnerability exploited under RHSA-2021:2099, which allows for potential privilege escalation.