RHSA-2022:0629: Important: kernel-rt security and bug fix update
The kernel-rt packages provide the Real Time Linux Kernel, which enables fine-tuning for systems with extremely high determinism requirements.<br>Security Fix(es):<br><li> kernel: Use After Free in unixgc() which could result in a local privilege escalation (CVE-2021-0920)</li> <li> kernel: use-after-free in RDMA listen() (CVE-2021-4028)</li> <li> kernel: xfs: raw block device data leak in XFSIOCALLOCSP IOCTL (CVE-2021-4155)</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.<br>Bug Fix(es):<br><li> kernnel-rt-debug: do not call blocking ops when !TASKRUNNING; state=1 set at [<0000000050e86018>] handleuserfault+0x530/0x1820 (BZ#2029420)</li> <li> kernel-rt: update RT source tree to the latest RHEL-8.2.z15 Batch (BZ#2046275)</li>
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of RHSA-2022:0629?
The severity of RHSA-2022:0629 is considered critical due to a potential local privilege escalation vulnerability.
How do I fix RHSA-2022:0629?
To fix RHSA-2022:0629, you should update the affected kernel-rt packages to version 4.18.0-193.75.1.rt13.125.el8_2 or later.
What vulnerability does RHSA-2022:0629 address?
RHSA-2022:0629 addresses a Use After Free vulnerability in unix_gc(), which could lead to local privilege escalation (CVE-2021-0920).
Which packages are affected by RHSA-2022:0629?
The affected packages by RHSA-2022:0629 include kernel-rt, kernel-rt-core, and their related debug and development packages.
Is a reboot required after applying the fix for RHSA-2022:0629?
Yes, a reboot is typically required to fully apply the kernel updates after fixing RHSA-2022:0629.