RHSA-2022:0622HighCVSS 7.8

Red Hat Security Advisory: kernel-rt security and bug fix update

Published
February 22, 2022
Last Modified
August 7, 2026

🔗 CVE IDs covered (9)

CVE-2020-0465 →CVE-2020-0466 →CVE-2021-0920 →CVE-2021-3573 →CVE-2021-3752 →CVE-2022-22942 →CVE-2021-3564 →CVE-2021-4155 →CVE-2022-0330 →

📋 Description

CVE-2020-0465 — kernel: out of bounds write in hid-multitouch.c may lead to escalation of privilege CVE-2020-0466 — kernel: use after free in eventpoll.c may lead to escalation of privilege CVE-2021-0920 — kernel: Use After Free in unix_gc() which could result in a local privilege escalation CVE-2021-3564 — kernel: double free in bluetooth subsystem when the HCI device initialization fails CVE-2021-3573 — kernel: use-after-free in function hci_sock_bound_ioctl() CVE-2021-3752 — kernel: possible use-after-free in bluetooth module 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-22942 — kernel: failing usercopy allows for use-after-free exploitation

🎯 Affected products32

  • Red Hat Enterprise Linux for Real Time (v. 7)
  • Red Hat Enterprise Linux for Real Time for NFV (v. 7)
  • kernel-rt-0:3.10.0-1160.59.1.rt56.1200.el7.src as a component of Red Hat Enterprise Linux for Real Time (v. 7)
  • kernel-rt-0:3.10.0-1160.59.1.rt56.1200.el7.src as a component of Red Hat Enterprise Linux for Real Time for NFV (v. 7)
  • kernel-rt-0:3.10.0-1160.59.1.rt56.1200.el7.x86_64 as a component of Red Hat Enterprise Linux for Real Time (v. 7)
  • kernel-rt-0:3.10.0-1160.59.1.rt56.1200.el7.x86_64 as a component of Red Hat Enterprise Linux for Real Time for NFV (v. 7)
  • kernel-rt-debug-0:3.10.0-1160.59.1.rt56.1200.el7.x86_64 as a component of Red Hat Enterprise Linux for Real Time (v. 7)
  • kernel-rt-debug-0:3.10.0-1160.59.1.rt56.1200.el7.x86_64 as a component of Red Hat Enterprise Linux for Real Time for NFV (v. 7)
  • kernel-rt-debug-debuginfo-0:3.10.0-1160.59.1.rt56.1200.el7.x86_64 as a component of Red Hat Enterprise Linux for Real Time (v. 7)
  • kernel-rt-debug-debuginfo-0:3.10.0-1160.59.1.rt56.1200.el7.x86_64 as a component of Red Hat Enterprise Linux for Real Time for NFV (v. 7)
  • kernel-rt-debug-devel-0:3.10.0-1160.59.1.rt56.1200.el7.x86_64 as a component of Red Hat Enterprise Linux for Real Time (v. 7)
  • kernel-rt-debug-devel-0:3.10.0-1160.59.1.rt56.1200.el7.x86_64 as a component of Red Hat Enterprise Linux for Real Time for NFV (v. 7)
  • kernel-rt-debug-kvm-0:3.10.0-1160.59.1.rt56.1200.el7.x86_64 as a component of Red Hat Enterprise Linux for Real Time for NFV (v. 7)
  • kernel-rt-debug-kvm-debuginfo-0:3.10.0-1160.59.1.rt56.1200.el7.x86_64 as a component of Red Hat Enterprise Linux for Real Time for NFV (v. 7)
  • kernel-rt-debuginfo-0:3.10.0-1160.59.1.rt56.1200.el7.x86_64 as a component of Red Hat Enterprise Linux for Real Time (v. 7)
  • kernel-rt-debuginfo-0:3.10.0-1160.59.1.rt56.1200.el7.x86_64 as a component of Red Hat Enterprise Linux for Real Time for NFV (v. 7)
  • kernel-rt-debuginfo-common-x86_64-0:3.10.0-1160.59.1.rt56.1200.el7.x86_64 as a component of Red Hat Enterprise Linux for Real Time (v. 7)
  • kernel-rt-debuginfo-common-x86_64-0:3.10.0-1160.59.1.rt56.1200.el7.x86_64 as a component of Red Hat Enterprise Linux for Real Time for NFV (v. 7)
  • kernel-rt-devel-0:3.10.0-1160.59.1.rt56.1200.el7.x86_64 as a component of Red Hat Enterprise Linux for Real Time (v. 7)
  • kernel-rt-devel-0:3.10.0-1160.59.1.rt56.1200.el7.x86_64 as a component of Red Hat Enterprise Linux for Real Time for NFV (v. 7)
  • kernel-rt-doc-0:3.10.0-1160.59.1.rt56.1200.el7.noarch as a component of Red Hat Enterprise Linux for Real Time (v. 7)
  • kernel-rt-doc-0:3.10.0-1160.59.1.rt56.1200.el7.noarch as a component of Red Hat Enterprise Linux for Real Time for NFV (v. 7)
  • kernel-rt-kvm-0:3.10.0-1160.59.1.rt56.1200.el7.x86_64 as a component of Red Hat Enterprise Linux for Real Time for NFV (v. 7)
  • kernel-rt-kvm-debuginfo-0:3.10.0-1160.59.1.rt56.1200.el7.x86_64 as a component of Red Hat Enterprise Linux for Real Time for NFV (v. 7)
  • kernel-rt-trace-0:3.10.0-1160.59.1.rt56.1200.el7.x86_64 as a component of Red Hat Enterprise Linux for Real Time (v. 7)
  • kernel-rt-trace-0:3.10.0-1160.59.1.rt56.1200.el7.x86_64 as a component of Red Hat Enterprise Linux for Real Time for NFV (v. 7)
  • kernel-rt-trace-debuginfo-0:3.10.0-1160.59.1.rt56.1200.el7.x86_64 as a component of Red Hat Enterprise Linux for Real Time (v. 7)
  • kernel-rt-trace-debuginfo-0:3.10.0-1160.59.1.rt56.1200.el7.x86_64 as a component of Red Hat Enterprise Linux for Real Time for NFV (v. 7)
  • kernel-rt-trace-devel-0:3.10.0-1160.59.1.rt56.1200.el7.x86_64 as a component of Red Hat Enterprise Linux for Real Time (v. 7)
  • kernel-rt-trace-devel-0:3.10.0-1160.59.1.rt56.1200.el7.x86_64 as a component of Red Hat Enterprise Linux for Real Time for NFV (v. 7)
  • +2 more not shown

✅ 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 The system must be rebooted for this update to take effect. Workaround: As the multitouch module will be auto-loaded when required, its use can be disabled by preventing the module from loading with the following instructions: # echo "install hid-multitouch /bin/true" >> /etc/modprobe.d/disable-hid-multitouch.conf The system may need to be restarted if the hid-multitouch module is loaded. In most circumstances, a kernel modules will be unable to be unloaded while in use. If the system requires this module to work correctly, this mitigation may not be suitable. If you need further assistance, see KCS article https://access.redhat.com/solutions/41278 or contact Red Hat Global Support Services. Workaround: Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update as soon as possible. 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 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 don't meet the Red Hat Product Security criteria comprising easThe required privileges is CAP_NET_ADMIN capabilities. This would require a privileged user with CAP_SYS_ADMIN or root to be able to abuse this flaw reducing its attack space.e 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 don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation baser or stability. The possible solution is to disable Bluetooth completely: https://access.redhat.com/solutions/2682931 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 (12)