RHSA-2022:5648: Important: kpatch-patch security update
Published Jul 19, 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: a use-after-free write in the netfilter subsystem can lead to privilege escalation to root (CVE-2022-32250) 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
63 affected componentsFixes available
redhat/kpatch-patch<4_18_0-147_51_2-1-8.el8_1
4_18_0-147_51_2-1-8.el8_1
redhat/kpatch-patch<4_18_0-147_52_1-1-7.el8_1
4_18_0-147_52_1-1-7.el8_1
redhat/kpatch-patch<4_18_0-147_54_2-1-6.el8_1
4_18_0-147_54_2-1-6.el8_1
redhat/kpatch-patch<4_18_0-147_56_1-1-6.el8_1
4_18_0-147_56_1-1-6.el8_1
redhat/kpatch-patch<4_18_0-147_58_1-1-4.el8_1
4_18_0-147_58_1-1-4.el8_1
redhat/kpatch-patch<4_18_0-147_59_1-1-4.el8_1
4_18_0-147_59_1-1-4.el8_1
redhat/kpatch-patch<4_18_0-147_64_1-1-3.el8_1
4_18_0-147_64_1-1-3.el8_1
redhat/kpatch-patch<4_18_0-147_65_1-1-2.el8_1
4_18_0-147_65_1-1-2.el8_1
redhat/kpatch-patch<4_18_0-147_67_1-1-1.el8_1
4_18_0-147_67_1-1-1.el8_1
redhat/kpatch-patch<4_18_0-147_51_2-1-8.el8_1
4_18_0-147_51_2-1-8.el8_1
redhat/kpatch-patch<4_18_0-147_51_2-debuginfo-1-8.el8_1
4_18_0-147_51_2-debuginfo-1-8.el8_1
redhat/kpatch-patch<4_18_0-147_51_2-debugsource-1-8.el8_1
4_18_0-147_51_2-debugsource-1-8.el8_1
redhat/kpatch-patch<4_18_0-147_52_1-1-7.el8_1
4_18_0-147_52_1-1-7.el8_1
redhat/kpatch-patch<4_18_0-147_52_1-debuginfo-1-7.el8_1
4_18_0-147_52_1-debuginfo-1-7.el8_1
redhat/kpatch-patch<4_18_0-147_52_1-debugsource-1-7.el8_1
4_18_0-147_52_1-debugsource-1-7.el8_1
redhat/kpatch-patch<4_18_0-147_54_2-1-6.el8_1
4_18_0-147_54_2-1-6.el8_1
redhat/kpatch-patch<4_18_0-147_54_2-debuginfo-1-6.el8_1
4_18_0-147_54_2-debuginfo-1-6.el8_1
redhat/kpatch-patch<4_18_0-147_54_2-debugsource-1-6.el8_1
4_18_0-147_54_2-debugsource-1-6.el8_1
redhat/kpatch-patch<4_18_0-147_56_1-1-6.el8_1
4_18_0-147_56_1-1-6.el8_1
redhat/kpatch-patch<4_18_0-147_56_1-debuginfo-1-6.el8_1
4_18_0-147_56_1-debuginfo-1-6.el8_1
redhat/kpatch-patch<4_18_0-147_56_1-debugsource-1-6.el8_1
4_18_0-147_56_1-debugsource-1-6.el8_1
redhat/kpatch-patch<4_18_0-147_58_1-1-4.el8_1
4_18_0-147_58_1-1-4.el8_1
redhat/kpatch-patch<4_18_0-147_58_1-debuginfo-1-4.el8_1
4_18_0-147_58_1-debuginfo-1-4.el8_1
redhat/kpatch-patch<4_18_0-147_58_1-debugsource-1-4.el8_1
4_18_0-147_58_1-debugsource-1-4.el8_1
redhat/kpatch-patch<4_18_0-147_59_1-1-4.el8_1
4_18_0-147_59_1-1-4.el8_1
redhat/kpatch-patch<4_18_0-147_59_1-debuginfo-1-4.el8_1
4_18_0-147_59_1-debuginfo-1-4.el8_1
redhat/kpatch-patch<4_18_0-147_59_1-debugsource-1-4.el8_1
4_18_0-147_59_1-debugsource-1-4.el8_1
redhat/kpatch-patch<4_18_0-147_64_1-1-3.el8_1
4_18_0-147_64_1-1-3.el8_1
redhat/kpatch-patch<4_18_0-147_64_1-debuginfo-1-3.el8_1
4_18_0-147_64_1-debuginfo-1-3.el8_1
redhat/kpatch-patch<4_18_0-147_64_1-debugsource-1-3.el8_1
4_18_0-147_64_1-debugsource-1-3.el8_1
redhat/kpatch-patch<4_18_0-147_65_1-1-2.el8_1
4_18_0-147_65_1-1-2.el8_1
redhat/kpatch-patch<4_18_0-147_65_1-debuginfo-1-2.el8_1
4_18_0-147_65_1-debuginfo-1-2.el8_1
redhat/kpatch-patch<4_18_0-147_65_1-debugsource-1-2.el8_1
4_18_0-147_65_1-debugsource-1-2.el8_1
redhat/kpatch-patch<4_18_0-147_67_1-1-1.el8_1
4_18_0-147_67_1-1-1.el8_1
redhat/kpatch-patch<4_18_0-147_67_1-debuginfo-1-1.el8_1
4_18_0-147_67_1-debuginfo-1-1.el8_1
redhat/kpatch-patch<4_18_0-147_67_1-debugsource-1-1.el8_1
4_18_0-147_67_1-debugsource-1-1.el8_1
redhat/kpatch-patch<4_18_0-147_51_2-1-8.el8_1
4_18_0-147_51_2-1-8.el8_1
redhat/kpatch-patch<4_18_0-147_51_2-debuginfo-1-8.el8_1
4_18_0-147_51_2-debuginfo-1-8.el8_1
redhat/kpatch-patch<4_18_0-147_51_2-debugsource-1-8.el8_1
4_18_0-147_51_2-debugsource-1-8.el8_1
redhat/kpatch-patch<4_18_0-147_52_1-1-7.el8_1
4_18_0-147_52_1-1-7.el8_1
redhat/kpatch-patch<4_18_0-147_52_1-debuginfo-1-7.el8_1
4_18_0-147_52_1-debuginfo-1-7.el8_1
redhat/kpatch-patch<4_18_0-147_52_1-debugsource-1-7.el8_1
4_18_0-147_52_1-debugsource-1-7.el8_1
redhat/kpatch-patch<4_18_0-147_54_2-1-6.el8_1
4_18_0-147_54_2-1-6.el8_1
redhat/kpatch-patch<4_18_0-147_54_2-debuginfo-1-6.el8_1
4_18_0-147_54_2-debuginfo-1-6.el8_1
redhat/kpatch-patch<4_18_0-147_54_2-debugsource-1-6.el8_1
4_18_0-147_54_2-debugsource-1-6.el8_1
redhat/kpatch-patch<4_18_0-147_56_1-1-6.el8_1
4_18_0-147_56_1-1-6.el8_1
redhat/kpatch-patch<4_18_0-147_56_1-debuginfo-1-6.el8_1
4_18_0-147_56_1-debuginfo-1-6.el8_1
redhat/kpatch-patch<4_18_0-147_56_1-debugsource-1-6.el8_1
4_18_0-147_56_1-debugsource-1-6.el8_1
redhat/kpatch-patch<4_18_0-147_58_1-1-4.el8_1
4_18_0-147_58_1-1-4.el8_1
redhat/kpatch-patch<4_18_0-147_58_1-debuginfo-1-4.el8_1
4_18_0-147_58_1-debuginfo-1-4.el8_1
redhat/kpatch-patch<4_18_0-147_58_1-debugsource-1-4.el8_1
4_18_0-147_58_1-debugsource-1-4.el8_1
redhat/kpatch-patch<4_18_0-147_59_1-1-4.el8_1
4_18_0-147_59_1-1-4.el8_1
redhat/kpatch-patch<4_18_0-147_59_1-debuginfo-1-4.el8_1
4_18_0-147_59_1-debuginfo-1-4.el8_1
redhat/kpatch-patch<4_18_0-147_59_1-debugsource-1-4.el8_1
4_18_0-147_59_1-debugsource-1-4.el8_1
redhat/kpatch-patch<4_18_0-147_64_1-1-3.el8_1
4_18_0-147_64_1-1-3.el8_1
redhat/kpatch-patch<4_18_0-147_64_1-debuginfo-1-3.el8_1
4_18_0-147_64_1-debuginfo-1-3.el8_1
redhat/kpatch-patch<4_18_0-147_64_1-debugsource-1-3.el8_1
4_18_0-147_64_1-debugsource-1-3.el8_1
redhat/kpatch-patch<4_18_0-147_65_1-1-2.el8_1
4_18_0-147_65_1-1-2.el8_1
redhat/kpatch-patch<4_18_0-147_65_1-debuginfo-1-2.el8_1
4_18_0-147_65_1-debuginfo-1-2.el8_1
redhat/kpatch-patch<4_18_0-147_65_1-debugsource-1-2.el8_1
4_18_0-147_65_1-debugsource-1-2.el8_1
redhat/kpatch-patch<4_18_0-147_67_1-1-1.el8_1
4_18_0-147_67_1-1-1.el8_1
redhat/kpatch-patch<4_18_0-147_67_1-debuginfo-1-1.el8_1
4_18_0-147_67_1-debuginfo-1-1.el8_1
redhat/kpatch-patch<4_18_0-147_67_1-debugsource-1-1.el8_1
4_18_0-147_67_1-debugsource-1-1.el8_1
Remediation
Event History
Jul 19, 2022
Advisory Published
via Red Hat·12:00 AM
Frequently Asked Questions
1
What is the severity of RHSA-2022:5648?
The severity of RHSA-2022:5648 is classified as important.
2
How do I fix RHSA-2022:5648?
To fix RHSA-2022:5648, you need to update the kpatch-patch package to the latest remedied version available from Red Hat.
3
What is the vulnerability in RHSA-2022:5648?
The vulnerability in RHSA-2022:5648 is a use-after-free write in the netfilter subsystem that can lead to privilege escalation to root (CVE-2022-32250).
4
Which versions of kpatch-patch are affected by RHSA-2022:5648?
RHSA-2022:5648 affects multiple versions of kpatch-patch, specifically those prior to the remedied versions 4_18_0-147_51_2-1-8.el8_1, 4_18_0-147_52_1-1-7.el8_1, and others listed.
5
Is there a specific command to update for RHSA-2022:5648?
Yes, you can run 'yum update kpatch-patch' to apply the necessary updates for RHSA-2022:5648.