First published: Tue Jan 09 2024(Updated: )
Important: kpatch-patch security update
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/kpatch-patch | <4_18_0-513_5_1-1-2.el8_9 | 4_18_0-513_5_1-1-2.el8_9 |
redhat/kpatch-patch | <4_18_0-513_9_1-1-1.el8_9 | 4_18_0-513_9_1-1-1.el8_9 |
redhat/kpatch-patch | <4_18_0-513_5_1-1-2.el8_9 | 4_18_0-513_5_1-1-2.el8_9 |
redhat/kpatch-patch | <4_18_0-513_5_1-debuginfo-1-2.el8_9 | 4_18_0-513_5_1-debuginfo-1-2.el8_9 |
redhat/kpatch-patch | <4_18_0-513_5_1-debugsource-1-2.el8_9 | 4_18_0-513_5_1-debugsource-1-2.el8_9 |
redhat/kpatch-patch | <4_18_0-513_9_1-1-1.el8_9 | 4_18_0-513_9_1-1-1.el8_9 |
redhat/kpatch-patch | <4_18_0-513_9_1-debuginfo-1-1.el8_9 | 4_18_0-513_9_1-debuginfo-1-1.el8_9 |
redhat/kpatch-patch | <4_18_0-513_9_1-debugsource-1-1.el8_9 | 4_18_0-513_9_1-debugsource-1-1.el8_9 |
redhat/kpatch-patch | <4_18_0-513_5_1-1-2.el8_9 | 4_18_0-513_5_1-1-2.el8_9 |
redhat/kpatch-patch | <4_18_0-513_5_1-debuginfo-1-2.el8_9 | 4_18_0-513_5_1-debuginfo-1-2.el8_9 |
redhat/kpatch-patch | <4_18_0-513_5_1-debugsource-1-2.el8_9 | 4_18_0-513_5_1-debugsource-1-2.el8_9 |
redhat/kpatch-patch | <4_18_0-513_9_1-1-1.el8_9 | 4_18_0-513_9_1-1-1.el8_9 |
redhat/kpatch-patch | <4_18_0-513_9_1-debuginfo-1-1.el8_9 | 4_18_0-513_9_1-debuginfo-1-1.el8_9 |
redhat/kpatch-patch | <4_18_0-513_9_1-debugsource-1-1.el8_9 | 4_18_0-513_9_1-debugsource-1-1.el8_9 |
Red Hat Enterprise Linux 8 | ||
Red Hat Enterprise Linux for Power, little endian - Extended Update Support |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of RHSA-2024:0089 is classified as important due to the use after free vulnerability in unix_stream_sendpage.
You can fix RHSA-2024:0089 by updating to the patched version of the kpatch-patch package available for your system.
RHSA-2024:0089 affects Red Hat Enterprise Linux for x86_64 and Power architectures that are using the vulnerable kernel.
RHSA-2024:0089 addresses a use after free vulnerability identified by CVE-2023-4622.
No specific workaround is recommended for RHSA-2024:0089; applying the security update is the best course of action.