What is the severity of RHSA-2023:0536?

The severity of RHSA-2023:0536 is classified as important.

How do I fix RHSA-2023:0536?

To fix RHSA-2023:0536, you need to update the kpatch-patch package to the latest version specified in the advisory.

What vulnerabilities does RHSA-2023:0536 address?

RHSA-2023:0536 addresses memory corruption issues in AX88179_178A based USB ethernet devices as identified by CVE-2022-2964.

Which packages are affected by RHSA-2023:0536?

Packages affected by RHSA-2023:0536 include various versions of the kpatch-patch related to kernel updates.

Is a reboot required after applying RHSA-2023:0536?

Typically, a reboot is required after applying RHSA-2023:0536 to ensure the kernel updates take effect.

Vulnerability/
RHSA-2023:0536

30/1/2023

RHSA-2023:0536: Important: kpatch-patch security update

First published: Mon Jan 30 2023(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: memory corruption in AX88179_178A based USB ethernet device. (CVE-2022-2964)</li> <li> kernel: i915: Incorrect GPU TLB flush can lead to random memory access (CVE-2022-4139)</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	<5_14_0-70_17_1-1-5.el9_0	5_14_0-70_17_1-1-5.el9_0
redhat/kpatch-patch	<5_14_0-70_22_1-1-5.el9_0	5_14_0-70_22_1-1-5.el9_0
redhat/kpatch-patch	<5_14_0-70_26_1-1-4.el9_0	5_14_0-70_26_1-1-4.el9_0
redhat/kpatch-patch	<5_14_0-70_30_1-1-2.el9_0	5_14_0-70_30_1-1-2.el9_0
redhat/kpatch-patch	<5_14_0-70_36_1-1-1.el9_0	5_14_0-70_36_1-1-1.el9_0
redhat/kpatch-patch	<5_14_0-70_17_1-1-5.el9_0	5_14_0-70_17_1-1-5.el9_0
redhat/kpatch-patch	<5_14_0-70_17_1-debuginfo-1-5.el9_0	5_14_0-70_17_1-debuginfo-1-5.el9_0
redhat/kpatch-patch	<5_14_0-70_17_1-debugsource-1-5.el9_0	5_14_0-70_17_1-debugsource-1-5.el9_0
redhat/kpatch-patch	<5_14_0-70_22_1-1-5.el9_0	5_14_0-70_22_1-1-5.el9_0
redhat/kpatch-patch	<5_14_0-70_22_1-debuginfo-1-5.el9_0	5_14_0-70_22_1-debuginfo-1-5.el9_0
redhat/kpatch-patch	<5_14_0-70_22_1-debugsource-1-5.el9_0	5_14_0-70_22_1-debugsource-1-5.el9_0
redhat/kpatch-patch	<5_14_0-70_26_1-1-4.el9_0	5_14_0-70_26_1-1-4.el9_0
redhat/kpatch-patch	<5_14_0-70_26_1-debuginfo-1-4.el9_0	5_14_0-70_26_1-debuginfo-1-4.el9_0
redhat/kpatch-patch	<5_14_0-70_26_1-debugsource-1-4.el9_0	5_14_0-70_26_1-debugsource-1-4.el9_0
redhat/kpatch-patch	<5_14_0-70_30_1-1-2.el9_0	5_14_0-70_30_1-1-2.el9_0
redhat/kpatch-patch	<5_14_0-70_30_1-debuginfo-1-2.el9_0	5_14_0-70_30_1-debuginfo-1-2.el9_0
redhat/kpatch-patch	<5_14_0-70_30_1-debugsource-1-2.el9_0	5_14_0-70_30_1-debugsource-1-2.el9_0
redhat/kpatch-patch	<5_14_0-70_36_1-1-1.el9_0	5_14_0-70_36_1-1-1.el9_0
redhat/kpatch-patch	<5_14_0-70_36_1-debuginfo-1-1.el9_0	5_14_0-70_36_1-debuginfo-1-1.el9_0
redhat/kpatch-patch	<5_14_0-70_36_1-debugsource-1-1.el9_0	5_14_0-70_36_1-debugsource-1-1.el9_0
redhat/kpatch-patch	<5_14_0-70_17_1-1-5.el9_0	5_14_0-70_17_1-1-5.el9_0
redhat/kpatch-patch	<5_14_0-70_17_1-debuginfo-1-5.el9_0	5_14_0-70_17_1-debuginfo-1-5.el9_0
redhat/kpatch-patch	<5_14_0-70_17_1-debugsource-1-5.el9_0	5_14_0-70_17_1-debugsource-1-5.el9_0
redhat/kpatch-patch	<5_14_0-70_22_1-1-5.el9_0	5_14_0-70_22_1-1-5.el9_0
redhat/kpatch-patch	<5_14_0-70_22_1-debuginfo-1-5.el9_0	5_14_0-70_22_1-debuginfo-1-5.el9_0
redhat/kpatch-patch	<5_14_0-70_22_1-debugsource-1-5.el9_0	5_14_0-70_22_1-debugsource-1-5.el9_0
redhat/kpatch-patch	<5_14_0-70_26_1-1-4.el9_0	5_14_0-70_26_1-1-4.el9_0
redhat/kpatch-patch	<5_14_0-70_26_1-debuginfo-1-4.el9_0	5_14_0-70_26_1-debuginfo-1-4.el9_0
redhat/kpatch-patch	<5_14_0-70_26_1-debugsource-1-4.el9_0	5_14_0-70_26_1-debugsource-1-4.el9_0
redhat/kpatch-patch	<5_14_0-70_30_1-1-2.el9_0	5_14_0-70_30_1-1-2.el9_0
redhat/kpatch-patch	<5_14_0-70_30_1-debuginfo-1-2.el9_0	5_14_0-70_30_1-debuginfo-1-2.el9_0
redhat/kpatch-patch	<5_14_0-70_30_1-debugsource-1-2.el9_0	5_14_0-70_30_1-debugsource-1-2.el9_0
redhat/kpatch-patch	<5_14_0-70_36_1-1-1.el9_0	5_14_0-70_36_1-1-1.el9_0
redhat/kpatch-patch	<5_14_0-70_36_1-debuginfo-1-1.el9_0	5_14_0-70_36_1-debuginfo-1-1.el9_0
redhat/kpatch-patch	<5_14_0-70_36_1-debugsource-1-1.el9_0	5_14_0-70_36_1-debugsource-1-1.el9_0

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of RHSA-2023:0536?
The severity of RHSA-2023:0536 is classified as important.
How do I fix RHSA-2023:0536?
To fix RHSA-2023:0536, you need to update the kpatch-patch package to the latest version specified in the advisory.
What vulnerabilities does RHSA-2023:0536 address?
RHSA-2023:0536 addresses memory corruption issues in AX88179_178A based USB ethernet devices as identified by CVE-2022-2964.
Which packages are affected by RHSA-2023:0536?
Packages affected by RHSA-2023:0536 include various versions of the kpatch-patch related to kernel updates.
Is a reboot required after applying RHSA-2023:0536?
Typically, a reboot is required after applying RHSA-2023:0536 to ensure the kernel updates take effect.

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