RHSA-2022:0590: Important: kpatch-patch security update
Published Feb 22, 2022
·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 unixgc() which could result in a local privilege escalation (CVE-2021-0920) kernel: use-after-free in RDMA listen() (CVE-2021-4028) kernel: xfs: raw block device data leak in XFSIOCALLOCSP IOCTL (CVE-2021-4155) 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-193_46_1-1-9.el8_2
4_18_0-193_46_1-1-9.el8_2
redhat/kpatch-patch<4_18_0-193_47_1-1-9.el8_2
4_18_0-193_47_1-1-9.el8_2
redhat/kpatch-patch<4_18_0-193_51_1-1-6.el8_2
4_18_0-193_51_1-1-6.el8_2
redhat/kpatch-patch<4_18_0-193_56_1-1-5.el8_2
4_18_0-193_56_1-1-5.el8_2
redhat/kpatch-patch<4_18_0-193_60_2-1-4.el8_2
4_18_0-193_60_2-1-4.el8_2
redhat/kpatch-patch<4_18_0-193_64_1-1-3.el8_2
4_18_0-193_64_1-1-3.el8_2
redhat/kpatch-patch<4_18_0-193_65_2-1-2.el8_2
4_18_0-193_65_2-1-2.el8_2
redhat/kpatch-patch<4_18_0-193_68_1-1-2.el8_2
4_18_0-193_68_1-1-2.el8_2
redhat/kpatch-patch<4_18_0-193_70_1-1-1.el8_2
4_18_0-193_70_1-1-1.el8_2
redhat/kpatch-patch<4_18_0-193_71_1-1-1.el8_2
4_18_0-193_71_1-1-1.el8_2
redhat/kpatch-patch<4_18_0-193_46_1-1-9.el8_2
4_18_0-193_46_1-1-9.el8_2
redhat/kpatch-patch<4_18_0-193_46_1-debuginfo-1-9.el8_2
4_18_0-193_46_1-debuginfo-1-9.el8_2
redhat/kpatch-patch<4_18_0-193_46_1-debugsource-1-9.el8_2
4_18_0-193_46_1-debugsource-1-9.el8_2
redhat/kpatch-patch<4_18_0-193_47_1-1-9.el8_2
4_18_0-193_47_1-1-9.el8_2
redhat/kpatch-patch<4_18_0-193_47_1-debuginfo-1-9.el8_2
4_18_0-193_47_1-debuginfo-1-9.el8_2
redhat/kpatch-patch<4_18_0-193_47_1-debugsource-1-9.el8_2
4_18_0-193_47_1-debugsource-1-9.el8_2
redhat/kpatch-patch<4_18_0-193_51_1-1-6.el8_2
4_18_0-193_51_1-1-6.el8_2
redhat/kpatch-patch<4_18_0-193_51_1-debuginfo-1-6.el8_2
4_18_0-193_51_1-debuginfo-1-6.el8_2
redhat/kpatch-patch<4_18_0-193_51_1-debugsource-1-6.el8_2
4_18_0-193_51_1-debugsource-1-6.el8_2
redhat/kpatch-patch<4_18_0-193_56_1-1-5.el8_2
4_18_0-193_56_1-1-5.el8_2
redhat/kpatch-patch<4_18_0-193_56_1-debuginfo-1-5.el8_2
4_18_0-193_56_1-debuginfo-1-5.el8_2
redhat/kpatch-patch<4_18_0-193_56_1-debugsource-1-5.el8_2
4_18_0-193_56_1-debugsource-1-5.el8_2
redhat/kpatch-patch<4_18_0-193_60_2-1-4.el8_2
4_18_0-193_60_2-1-4.el8_2
redhat/kpatch-patch<4_18_0-193_60_2-debuginfo-1-4.el8_2
4_18_0-193_60_2-debuginfo-1-4.el8_2
redhat/kpatch-patch<4_18_0-193_60_2-debugsource-1-4.el8_2
4_18_0-193_60_2-debugsource-1-4.el8_2
redhat/kpatch-patch<4_18_0-193_64_1-1-3.el8_2
4_18_0-193_64_1-1-3.el8_2
redhat/kpatch-patch<4_18_0-193_64_1-debuginfo-1-3.el8_2
4_18_0-193_64_1-debuginfo-1-3.el8_2
redhat/kpatch-patch<4_18_0-193_64_1-debugsource-1-3.el8_2
4_18_0-193_64_1-debugsource-1-3.el8_2
redhat/kpatch-patch<4_18_0-193_65_2-1-2.el8_2
4_18_0-193_65_2-1-2.el8_2
redhat/kpatch-patch<4_18_0-193_65_2-debuginfo-1-2.el8_2
4_18_0-193_65_2-debuginfo-1-2.el8_2
redhat/kpatch-patch<4_18_0-193_65_2-debugsource-1-2.el8_2
4_18_0-193_65_2-debugsource-1-2.el8_2
redhat/kpatch-patch<4_18_0-193_68_1-1-2.el8_2
4_18_0-193_68_1-1-2.el8_2
redhat/kpatch-patch<4_18_0-193_68_1-debuginfo-1-2.el8_2
4_18_0-193_68_1-debuginfo-1-2.el8_2
redhat/kpatch-patch<4_18_0-193_68_1-debugsource-1-2.el8_2
4_18_0-193_68_1-debugsource-1-2.el8_2
redhat/kpatch-patch<4_18_0-193_70_1-1-1.el8_2
4_18_0-193_70_1-1-1.el8_2
redhat/kpatch-patch<4_18_0-193_70_1-debuginfo-1-1.el8_2
4_18_0-193_70_1-debuginfo-1-1.el8_2
redhat/kpatch-patch<4_18_0-193_70_1-debugsource-1-1.el8_2
4_18_0-193_70_1-debugsource-1-1.el8_2
redhat/kpatch-patch<4_18_0-193_71_1-1-1.el8_2
4_18_0-193_71_1-1-1.el8_2
redhat/kpatch-patch<4_18_0-193_71_1-debuginfo-1-1.el8_2
4_18_0-193_71_1-debuginfo-1-1.el8_2
redhat/kpatch-patch<4_18_0-193_71_1-debugsource-1-1.el8_2
4_18_0-193_71_1-debugsource-1-1.el8_2
redhat/kpatch-patch<4_18_0-193_46_1-1-9.el8_2
4_18_0-193_46_1-1-9.el8_2
redhat/kpatch-patch<4_18_0-193_46_1-debuginfo-1-9.el8_2
4_18_0-193_46_1-debuginfo-1-9.el8_2
redhat/kpatch-patch<4_18_0-193_46_1-debugsource-1-9.el8_2
4_18_0-193_46_1-debugsource-1-9.el8_2
redhat/kpatch-patch<4_18_0-193_47_1-1-9.el8_2
4_18_0-193_47_1-1-9.el8_2
redhat/kpatch-patch<4_18_0-193_47_1-debuginfo-1-9.el8_2
4_18_0-193_47_1-debuginfo-1-9.el8_2
redhat/kpatch-patch<4_18_0-193_47_1-debugsource-1-9.el8_2
4_18_0-193_47_1-debugsource-1-9.el8_2
redhat/kpatch-patch<4_18_0-193_51_1-1-6.el8_2
4_18_0-193_51_1-1-6.el8_2
redhat/kpatch-patch<4_18_0-193_51_1-debuginfo-1-6.el8_2
4_18_0-193_51_1-debuginfo-1-6.el8_2
redhat/kpatch-patch<4_18_0-193_51_1-debugsource-1-6.el8_2
4_18_0-193_51_1-debugsource-1-6.el8_2
redhat/kpatch-patch<4_18_0-193_56_1-1-5.el8_2
4_18_0-193_56_1-1-5.el8_2
redhat/kpatch-patch<4_18_0-193_56_1-debuginfo-1-5.el8_2
4_18_0-193_56_1-debuginfo-1-5.el8_2
redhat/kpatch-patch<4_18_0-193_56_1-debugsource-1-5.el8_2
4_18_0-193_56_1-debugsource-1-5.el8_2
redhat/kpatch-patch<4_18_0-193_60_2-1-4.el8_2
4_18_0-193_60_2-1-4.el8_2
redhat/kpatch-patch<4_18_0-193_60_2-debuginfo-1-4.el8_2
4_18_0-193_60_2-debuginfo-1-4.el8_2
redhat/kpatch-patch<4_18_0-193_60_2-debugsource-1-4.el8_2
4_18_0-193_60_2-debugsource-1-4.el8_2
redhat/kpatch-patch<4_18_0-193_64_1-1-3.el8_2
4_18_0-193_64_1-1-3.el8_2
redhat/kpatch-patch<4_18_0-193_64_1-debuginfo-1-3.el8_2
4_18_0-193_64_1-debuginfo-1-3.el8_2
redhat/kpatch-patch<4_18_0-193_64_1-debugsource-1-3.el8_2
4_18_0-193_64_1-debugsource-1-3.el8_2
redhat/kpatch-patch<4_18_0-193_65_2-1-2.el8_2
4_18_0-193_65_2-1-2.el8_2
redhat/kpatch-patch<4_18_0-193_65_2-debuginfo-1-2.el8_2
4_18_0-193_65_2-debuginfo-1-2.el8_2
redhat/kpatch-patch<4_18_0-193_65_2-debugsource-1-2.el8_2
4_18_0-193_65_2-debugsource-1-2.el8_2
redhat/kpatch-patch<4_18_0-193_68_1-1-2.el8_2
4_18_0-193_68_1-1-2.el8_2
redhat/kpatch-patch<4_18_0-193_68_1-debuginfo-1-2.el8_2
4_18_0-193_68_1-debuginfo-1-2.el8_2
redhat/kpatch-patch<4_18_0-193_68_1-debugsource-1-2.el8_2
4_18_0-193_68_1-debugsource-1-2.el8_2
redhat/kpatch-patch<4_18_0-193_70_1-1-1.el8_2
4_18_0-193_70_1-1-1.el8_2
redhat/kpatch-patch<4_18_0-193_70_1-debuginfo-1-1.el8_2
4_18_0-193_70_1-debuginfo-1-1.el8_2
redhat/kpatch-patch<4_18_0-193_70_1-debugsource-1-1.el8_2
4_18_0-193_70_1-debugsource-1-1.el8_2
redhat/kpatch-patch<4_18_0-193_71_1-1-1.el8_2
4_18_0-193_71_1-1-1.el8_2
redhat/kpatch-patch<4_18_0-193_71_1-debuginfo-1-1.el8_2
4_18_0-193_71_1-debuginfo-1-1.el8_2
redhat/kpatch-patch<4_18_0-193_71_1-debugsource-1-1.el8_2
4_18_0-193_71_1-debugsource-1-1.el8_2
Remediation
Event History
Feb 22, 2022
Advisory Published
via Red Hat·12:00 AM
Frequently Asked Questions
1
What is the severity of RHSA-2022:0590?
RHSA-2022:0590 addresses a critical use-after-free vulnerability that can allow local privilege escalation.
2
How do I fix RHSA-2022:0590?
To fix RHSA-2022:0590, apply the appropriate updates for the kpatch-patch package as specified in the advisory.
3
What packages are affected by RHSA-2022:0590?
RHSA-2022:0590 affects multiple versions of the kpatch-patch package across various architectures.
4
What does RHSA-2022:0590 mean for system security?
RHSA-2022:0590 indicates a security threat that requires immediate attention to prevent potential local privilege escalations.
5
When was RHSA-2022:0590 released?
RHSA-2022:0590 was released as a security advisory addressing vulnerabilities in the kernel.