RHSA-2022:0958HighCVSS 7.4

Red Hat Security Advisory: kpatch-patch-4_18_0-147_58_1 security and bug fix update

Published
March 17, 2022
Last Modified
August 7, 2026

🔗 CVE IDs covered (7)

CVE-2021-4155 →CVE-2022-0330 →CVE-2022-0492 →CVE-2022-22942 →CVE-2021-0920 →CVE-2021-4028 →CVE-2021-4083 →

📋 Description

CVE-2021-0920 — kernel: Use After Free in unix_gc() which could result in a local privilege escalation CVE-2021-4028 — kernel: use-after-free in RDMA listen() CVE-2021-4083 — kernel: fget: check that the fd still exists after getting a ref to it CVE-2021-4155 — kernel: xfs: raw block device data leak in XFS_IOC_ALLOCSP IOCTL CVE-2022-0330 — kernel: possible privileges escalation due to missing TLB flush CVE-2022-0492 — kernel: cgroups v1 release_agent feature may allow privilege escalation CVE-2022-22942 — kernel: failing usercopy allows for use-after-free exploitation

🎯 Affected products8

  • Red Hat Enterprise Linux BaseOS E4S (v. 8.1)
  • kpatch-patch-4_18_0-147_58_1-0:1-1.el8_1.ppc64le as a component of Red Hat Enterprise Linux BaseOS E4S (v. 8.1)
  • kpatch-patch-4_18_0-147_58_1-0:1-1.el8_1.src as a component of Red Hat Enterprise Linux BaseOS E4S (v. 8.1)
  • kpatch-patch-4_18_0-147_58_1-0:1-1.el8_1.x86_64 as a component of Red Hat Enterprise Linux BaseOS E4S (v. 8.1)
  • kpatch-patch-4_18_0-147_58_1-debuginfo-0:1-1.el8_1.ppc64le as a component of Red Hat Enterprise Linux BaseOS E4S (v. 8.1)
  • kpatch-patch-4_18_0-147_58_1-debuginfo-0:1-1.el8_1.x86_64 as a component of Red Hat Enterprise Linux BaseOS E4S (v. 8.1)
  • kpatch-patch-4_18_0-147_58_1-debugsource-0:1-1.el8_1.ppc64le as a component of Red Hat Enterprise Linux BaseOS E4S (v. 8.1)
  • kpatch-patch-4_18_0-147_58_1-debugsource-0:1-1.el8_1.x86_64 as a component of Red Hat Enterprise Linux BaseOS E4S (v. 8.1)

✅ Remediation

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 Workaround: Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability. Workaround: Mitigation for this issue is either not available or the currently available options does not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability. Workaround: This issue can be mitigated by ensuring xfs_alloc_file_space is not called with "0" as an argument. This can be done with a SystemTap script (which resets "0" with XFS_BMAPI_PREALLOC), below are the steps: 1) Save the following script in a 'CVE-2021-4155.stp' file --- On Red Hat Enterprise Linux 6 --- probe module("xfs").function("xfs_alloc_file_space") { if ($alloc_type == 0) $alloc_type = 0x40; # XFS_BMAPI_PREALLOC } --- On Red Hat Enterprise Linux 6 --- --- On Red Hat Enterprise Linux 7 onwards --- probe module("xfs").function("xfs_alloc_file_space") { if ($alloc_type == 0) $alloc_type = 0x8; # XFS_BMAPI_PREALLOC } --- On Red Hat Enterprise Linux 7 onwards --- 2) Install systemtap package and its dependencies # yum install -y systemtap systemtap-runtime # yum install -y kernel-devel kernel-debuginfo 3) Build the mitigation kernel module as root. # stap -r `uname -r` -m cve_2021_4155.ko -g CVE-2021-4155.stp -p4 4) Load the mitigation module as root # staprun -L cve_2021_4155.ko What is SystemTap and how to use it? https://access.redhat.com/solutions/5441 Workaround: Mitigation for this issue is to skip loading the affected module vmwgfx onto the system until we have a fix available. This can be done by a blacklist mechanism and ensures the driver is not loaded at the boot time. ~~~ How do I blacklist a kernel module to prevent it from loading automatically? https://access.redhat.com/solutions/41278 ~~~

🔗 References (10)