What is the severity of RHSA-2022:4721?

The severity of RHSA-2022:4721 is high due to the potential for privilege escalation via the cgroups v1 release_agent feature.

How do I fix RHSA-2022:4721?

To fix RHSA-2022:4721, update the kpatch-patch package to one of the specified remedied versions listed in the advisory.

What does RHSA-2022:4721 address?

RHSA-2022:4721 addresses a vulnerability in the kernel that may allow privilege escalation through the cgroups v1 release_agent feature.

Which versions of kpatch-patch are affected by RHSA-2022:4721?

Multiple versions of kpatch-patch prior to the remedied versions indicated in RHSA-2022:4721 are affected.

What command should I use to check if my system is affected by RHSA-2022:4721?

You can check if your system is affected by running 'rpm -qa kpatch-patch' and comparing the installed version against those mentioned in RHSA-2022:4721.

Vulnerability/
RHSA-2022:4721

24/5/2022

27/3/2024

RHSA-2022:4721: Important: kpatch-patch security update

First published: Tue May 24 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.<br>Security Fix(es):<br><li> kernel: cgroups v1 release_agent feature may allow privilege escalation (CVE-2022-0492)</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	Affected Version	How to fix
redhat/kpatch-patch	<3_10_0-1062_51_1-1-7.el7	3_10_0-1062_51_1-1-7.el7
redhat/kpatch-patch	<3_10_0-1062_52_2-1-6.el7	3_10_0-1062_52_2-1-6.el7
redhat/kpatch-patch	<3_10_0-1062_56_1-1-5.el7	3_10_0-1062_56_1-1-5.el7
redhat/kpatch-patch	<3_10_0-1062_59_1-1-3.el7	3_10_0-1062_59_1-1-3.el7
redhat/kpatch-patch	<3_10_0-1062_60_1-1-3.el7	3_10_0-1062_60_1-1-3.el7
redhat/kpatch-patch	<3_10_0-1062_61_1-1-3.el7	3_10_0-1062_61_1-1-3.el7
redhat/kpatch-patch	<3_10_0-1062_63_1-1-2.el7	3_10_0-1062_63_1-1-2.el7
redhat/kpatch-patch	<3_10_0-1062_66_1-1-1.el7	3_10_0-1062_66_1-1-1.el7
redhat/kpatch-patch	<3_10_0-1062_51_1-1-7.el7	3_10_0-1062_51_1-1-7.el7
redhat/kpatch-patch	<3_10_0-1062_51_1-debuginfo-1-7.el7	3_10_0-1062_51_1-debuginfo-1-7.el7
redhat/kpatch-patch	<3_10_0-1062_52_2-1-6.el7	3_10_0-1062_52_2-1-6.el7
redhat/kpatch-patch	<3_10_0-1062_52_2-debuginfo-1-6.el7	3_10_0-1062_52_2-debuginfo-1-6.el7
redhat/kpatch-patch	<3_10_0-1062_56_1-1-5.el7	3_10_0-1062_56_1-1-5.el7
redhat/kpatch-patch	<3_10_0-1062_56_1-debuginfo-1-5.el7	3_10_0-1062_56_1-debuginfo-1-5.el7
redhat/kpatch-patch	<3_10_0-1062_59_1-1-3.el7	3_10_0-1062_59_1-1-3.el7
redhat/kpatch-patch	<3_10_0-1062_59_1-debuginfo-1-3.el7	3_10_0-1062_59_1-debuginfo-1-3.el7
redhat/kpatch-patch	<3_10_0-1062_60_1-1-3.el7	3_10_0-1062_60_1-1-3.el7
redhat/kpatch-patch	<3_10_0-1062_60_1-debuginfo-1-3.el7	3_10_0-1062_60_1-debuginfo-1-3.el7
redhat/kpatch-patch	<3_10_0-1062_61_1-1-3.el7	3_10_0-1062_61_1-1-3.el7
redhat/kpatch-patch	<3_10_0-1062_61_1-debuginfo-1-3.el7	3_10_0-1062_61_1-debuginfo-1-3.el7
redhat/kpatch-patch	<3_10_0-1062_63_1-1-2.el7	3_10_0-1062_63_1-1-2.el7
redhat/kpatch-patch	<3_10_0-1062_63_1-debuginfo-1-2.el7	3_10_0-1062_63_1-debuginfo-1-2.el7
redhat/kpatch-patch	<3_10_0-1062_66_1-1-1.el7	3_10_0-1062_66_1-1-1.el7
redhat/kpatch-patch	<3_10_0-1062_66_1-debuginfo-1-1.el7	3_10_0-1062_66_1-debuginfo-1-1.el7
redhat/kpatch-patch	<3_10_0-1062_51_1-1-7.el7	3_10_0-1062_51_1-1-7.el7
redhat/kpatch-patch	<3_10_0-1062_51_1-debuginfo-1-7.el7	3_10_0-1062_51_1-debuginfo-1-7.el7
redhat/kpatch-patch	<3_10_0-1062_52_2-1-6.el7	3_10_0-1062_52_2-1-6.el7
redhat/kpatch-patch	<3_10_0-1062_52_2-debuginfo-1-6.el7	3_10_0-1062_52_2-debuginfo-1-6.el7
redhat/kpatch-patch	<3_10_0-1062_56_1-1-5.el7	3_10_0-1062_56_1-1-5.el7
redhat/kpatch-patch	<3_10_0-1062_56_1-debuginfo-1-5.el7	3_10_0-1062_56_1-debuginfo-1-5.el7
redhat/kpatch-patch	<3_10_0-1062_59_1-1-3.el7	3_10_0-1062_59_1-1-3.el7
redhat/kpatch-patch	<3_10_0-1062_59_1-debuginfo-1-3.el7	3_10_0-1062_59_1-debuginfo-1-3.el7
redhat/kpatch-patch	<3_10_0-1062_60_1-1-3.el7	3_10_0-1062_60_1-1-3.el7
redhat/kpatch-patch	<3_10_0-1062_60_1-debuginfo-1-3.el7	3_10_0-1062_60_1-debuginfo-1-3.el7
redhat/kpatch-patch	<3_10_0-1062_61_1-1-3.el7	3_10_0-1062_61_1-1-3.el7
redhat/kpatch-patch	<3_10_0-1062_61_1-debuginfo-1-3.el7	3_10_0-1062_61_1-debuginfo-1-3.el7
redhat/kpatch-patch	<3_10_0-1062_63_1-1-2.el7	3_10_0-1062_63_1-1-2.el7
redhat/kpatch-patch	<3_10_0-1062_63_1-debuginfo-1-2.el7	3_10_0-1062_63_1-debuginfo-1-2.el7
redhat/kpatch-patch	<3_10_0-1062_66_1-1-1.el7	3_10_0-1062_66_1-1-1.el7
redhat/kpatch-patch	<3_10_0-1062_66_1-debuginfo-1-1.el7	3_10_0-1062_66_1-debuginfo-1-1.el7

Never miss a vulnerability like this again

Reference Links

https://access.redhat.com/errata/RHSA-2022:4721 (Advisory)

Frequently Asked Questions

What is the severity of RHSA-2022:4721?
The severity of RHSA-2022:4721 is high due to the potential for privilege escalation via the cgroups v1 release_agent feature.
How do I fix RHSA-2022:4721?
To fix RHSA-2022:4721, update the kpatch-patch package to one of the specified remedied versions listed in the advisory.
What does RHSA-2022:4721 address?
RHSA-2022:4721 addresses a vulnerability in the kernel that may allow privilege escalation through the cgroups v1 release_agent feature.
Which versions of kpatch-patch are affected by RHSA-2022:4721?
Multiple versions of kpatch-patch prior to the remedied versions indicated in RHSA-2022:4721 are affected.
What command should I use to check if my system is affected by RHSA-2022:4721?
You can check if your system is affected by running 'rpm -qa kpatch-patch' and comparing the installed version against those mentioned in RHSA-2022:4721.

agent/severity
agent/first-publish-date
agent/last-modified-date
agent/type
agent/softwarecombine
agent/title
agent/description
collector/redhat-errata
source/Red Hat
anchor-id/RHSA-2022:4721
agent/software-canonical-lookup
agent/remedy
agent/references
agent/event
agent/tags
agent/source
package-manager/redhat