What is the severity of RHSA-2022:7885?

The severity of RHSA-2022:7885 is classified as important.

How do I fix RHSA-2022:7885?

To fix RHSA-2022:7885, upgrade to the patched versions of the kpatch-patch package, as specified in the advisory.

What does the vulnerability in RHSA-2022:7885 pertain to?

RHSA-2022:7885 addresses a use-after-free vulnerability in the cls_route filter implementation that may lead to privilege escalation.

Which versions of the kpatch-patch package are affected by RHSA-2022:7885?

RHSA-2022:7885 affects several versions of the kpatch-patch package including versions prior to 4_18_0-193_92_1-1-1.el8_2.

Is there a workaround for RHSA-2022:7885 if I cannot apply the patch immediately?

There are no documented workarounds for RHSA-2022:7885; applying the patch is recommended to mitigate the vulnerability.

Vulnerability/
RHSA-2022:7885

CWE

416

9/11/2022

12/4/2025

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

First published: Wed Nov 09 2022(Updated: )

The kpatch management tool provides a kernel patching infrastructure which<br>allows you to patch a running kernel without rebooting or restarting any<br>processes.<br>Security Fix(es):<br><li> kernel: a use-after-free in cls_route filter implementation may lead to privilege escalation (CVE-2022-2588)</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	<4_18_0-193_80_1-1-2.el8_2	4_18_0-193_80_1-1-2.el8_2
redhat/kpatch-patch	<4_18_0-193_81_1-1-2.el8_2	4_18_0-193_81_1-1-2.el8_2
redhat/kpatch-patch	<4_18_0-193_87_1-1-1.el8_2	4_18_0-193_87_1-1-1.el8_2
redhat/kpatch-patch	<4_18_0-193_90_1-1-1.el8_2	4_18_0-193_90_1-1-1.el8_2
redhat/kpatch-patch	<4_18_0-193_91_1-1-1.el8_2	4_18_0-193_91_1-1-1.el8_2
redhat/kpatch-patch	<4_18_0-193_80_1-1-2.el8_2	4_18_0-193_80_1-1-2.el8_2
redhat/kpatch-patch	<4_18_0-193_80_1-debuginfo-1-2.el8_2	4_18_0-193_80_1-debuginfo-1-2.el8_2
redhat/kpatch-patch	<4_18_0-193_80_1-debugsource-1-2.el8_2	4_18_0-193_80_1-debugsource-1-2.el8_2
redhat/kpatch-patch	<4_18_0-193_81_1-1-2.el8_2	4_18_0-193_81_1-1-2.el8_2
redhat/kpatch-patch	<4_18_0-193_81_1-debuginfo-1-2.el8_2	4_18_0-193_81_1-debuginfo-1-2.el8_2
redhat/kpatch-patch	<4_18_0-193_81_1-debugsource-1-2.el8_2	4_18_0-193_81_1-debugsource-1-2.el8_2
redhat/kpatch-patch	<4_18_0-193_87_1-1-1.el8_2	4_18_0-193_87_1-1-1.el8_2
redhat/kpatch-patch	<4_18_0-193_87_1-debuginfo-1-1.el8_2	4_18_0-193_87_1-debuginfo-1-1.el8_2
redhat/kpatch-patch	<4_18_0-193_87_1-debugsource-1-1.el8_2	4_18_0-193_87_1-debugsource-1-1.el8_2
redhat/kpatch-patch	<4_18_0-193_90_1-1-1.el8_2	4_18_0-193_90_1-1-1.el8_2
redhat/kpatch-patch	<4_18_0-193_90_1-debuginfo-1-1.el8_2	4_18_0-193_90_1-debuginfo-1-1.el8_2
redhat/kpatch-patch	<4_18_0-193_90_1-debugsource-1-1.el8_2	4_18_0-193_90_1-debugsource-1-1.el8_2
redhat/kpatch-patch	<4_18_0-193_91_1-1-1.el8_2	4_18_0-193_91_1-1-1.el8_2
redhat/kpatch-patch	<4_18_0-193_91_1-debuginfo-1-1.el8_2	4_18_0-193_91_1-debuginfo-1-1.el8_2
redhat/kpatch-patch	<4_18_0-193_91_1-debugsource-1-1.el8_2	4_18_0-193_91_1-debugsource-1-1.el8_2
redhat/kpatch-patch	<4_18_0-193_80_1-1-2.el8_2	4_18_0-193_80_1-1-2.el8_2
redhat/kpatch-patch	<4_18_0-193_80_1-debuginfo-1-2.el8_2	4_18_0-193_80_1-debuginfo-1-2.el8_2
redhat/kpatch-patch	<4_18_0-193_80_1-debugsource-1-2.el8_2	4_18_0-193_80_1-debugsource-1-2.el8_2
redhat/kpatch-patch	<4_18_0-193_81_1-1-2.el8_2	4_18_0-193_81_1-1-2.el8_2
redhat/kpatch-patch	<4_18_0-193_81_1-debuginfo-1-2.el8_2	4_18_0-193_81_1-debuginfo-1-2.el8_2
redhat/kpatch-patch	<4_18_0-193_81_1-debugsource-1-2.el8_2	4_18_0-193_81_1-debugsource-1-2.el8_2
redhat/kpatch-patch	<4_18_0-193_87_1-1-1.el8_2	4_18_0-193_87_1-1-1.el8_2
redhat/kpatch-patch	<4_18_0-193_87_1-debuginfo-1-1.el8_2	4_18_0-193_87_1-debuginfo-1-1.el8_2
redhat/kpatch-patch	<4_18_0-193_87_1-debugsource-1-1.el8_2	4_18_0-193_87_1-debugsource-1-1.el8_2
redhat/kpatch-patch	<4_18_0-193_90_1-1-1.el8_2	4_18_0-193_90_1-1-1.el8_2
redhat/kpatch-patch	<4_18_0-193_90_1-debuginfo-1-1.el8_2	4_18_0-193_90_1-debuginfo-1-1.el8_2
redhat/kpatch-patch	<4_18_0-193_90_1-debugsource-1-1.el8_2	4_18_0-193_90_1-debugsource-1-1.el8_2
redhat/kpatch-patch	<4_18_0-193_91_1-1-1.el8_2	4_18_0-193_91_1-1-1.el8_2
redhat/kpatch-patch	<4_18_0-193_91_1-debuginfo-1-1.el8_2	4_18_0-193_91_1-debuginfo-1-1.el8_2
redhat/kpatch-patch	<4_18_0-193_91_1-debugsource-1-1.el8_2	4_18_0-193_91_1-debugsource-1-1.el8_2

Never miss a vulnerability like this again

Reference Links

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

Frequently Asked Questions

What is the severity of RHSA-2022:7885?
The severity of RHSA-2022:7885 is classified as important.
How do I fix RHSA-2022:7885?
To fix RHSA-2022:7885, upgrade to the patched versions of the kpatch-patch package, as specified in the advisory.
What does the vulnerability in RHSA-2022:7885 pertain to?
RHSA-2022:7885 addresses a use-after-free vulnerability in the cls_route filter implementation that may lead to privilege escalation.
Which versions of the kpatch-patch package are affected by RHSA-2022:7885?
RHSA-2022:7885 affects several versions of the kpatch-patch package including versions prior to 4_18_0-193_92_1-1-1.el8_2.
Is there a workaround for RHSA-2022:7885 if I cannot apply the patch immediately?
There are no documented workarounds for RHSA-2022:7885; applying the patch is recommended to mitigate the vulnerability.

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