RHSA-2022:0777HighCVSS 7.8

Red Hat Security Advisory: kernel security, bug fix, and enhancement update

Published
March 8, 2022
Last Modified
August 7, 2026

🔗 CVE IDs covered (7)

CVE-2022-0516 →CVE-2022-22942 →CVE-2021-0920 →CVE-2021-4028 →CVE-2021-47544 →CVE-2022-0330 →CVE-2022-0435 →

📋 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-47544 — kernel: tcp: fix page frag corruption on page fault CVE-2022-0330 — kernel: possible privileges escalation due to missing TLB flush CVE-2022-0435 — kernel: remote stack overflow via kernel panic on systems using TIPC may lead to DoS CVE-2022-0516 — kernel: missing check in ioctl allows kernel memory read/write CVE-2022-22942 — kernel: failing usercopy allows for use-after-free exploitation

🎯 Affected products122

  • Red Hat Enterprise Linux BaseOS EUS (v.8.4)
  • Red Hat Enterprise Linux CRB EUS (v.8.4)
  • bpftool-0:4.18.0-305.40.1.el8_4.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.4)
  • bpftool-0:4.18.0-305.40.1.el8_4.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.4)
  • bpftool-0:4.18.0-305.40.1.el8_4.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.4)
  • bpftool-0:4.18.0-305.40.1.el8_4.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.4)
  • bpftool-debuginfo-0:4.18.0-305.40.1.el8_4.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.4)
  • bpftool-debuginfo-0:4.18.0-305.40.1.el8_4.aarch64 as a component of Red Hat Enterprise Linux CRB EUS (v.8.4)
  • bpftool-debuginfo-0:4.18.0-305.40.1.el8_4.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.4)
  • bpftool-debuginfo-0:4.18.0-305.40.1.el8_4.ppc64le as a component of Red Hat Enterprise Linux CRB EUS (v.8.4)
  • bpftool-debuginfo-0:4.18.0-305.40.1.el8_4.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.4)
  • bpftool-debuginfo-0:4.18.0-305.40.1.el8_4.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.4)
  • bpftool-debuginfo-0:4.18.0-305.40.1.el8_4.x86_64 as a component of Red Hat Enterprise Linux CRB EUS (v.8.4)
  • kernel-0:4.18.0-305.40.1.el8_4.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.4)
  • kernel-0:4.18.0-305.40.1.el8_4.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.4)
  • kernel-0:4.18.0-305.40.1.el8_4.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.4)
  • kernel-0:4.18.0-305.40.1.el8_4.src as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.4)
  • kernel-0:4.18.0-305.40.1.el8_4.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.4)
  • kernel-abi-stablelists-0:4.18.0-305.40.1.el8_4.noarch as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.4)
  • kernel-core-0:4.18.0-305.40.1.el8_4.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.4)
  • kernel-core-0:4.18.0-305.40.1.el8_4.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.4)
  • kernel-core-0:4.18.0-305.40.1.el8_4.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.4)
  • kernel-core-0:4.18.0-305.40.1.el8_4.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.4)
  • kernel-debug-0:4.18.0-305.40.1.el8_4.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.4)
  • kernel-debug-0:4.18.0-305.40.1.el8_4.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.4)
  • kernel-debug-0:4.18.0-305.40.1.el8_4.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.4)
  • kernel-debug-0:4.18.0-305.40.1.el8_4.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.4)
  • kernel-debug-core-0:4.18.0-305.40.1.el8_4.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.4)
  • kernel-debug-core-0:4.18.0-305.40.1.el8_4.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.4)
  • kernel-debug-core-0:4.18.0-305.40.1.el8_4.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.4)
  • +92 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: 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: Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability. Workaround: The TIPC module will NOT be automatically loaded. When required, administrative action is needed to explicitly load this module. Loading the module can be prevented with the following instructions: # echo "install tipc /bin/true" >> /etc/modprobe.d/disable-tipc.conf The system will need to be restarted if the tipc module is loaded. In most circumstances, the TIPC kernel module will be unable to be unloaded while any network interfaces are active and the protocol is in use. If the system requires this module to work correctly, this mitigation may not be suitable. Workaround: As the kvm.ko kernel module will be auto-loaded when required, its use can be disabled by preventing the module from loading with the following instructions: # echo "install kvm /bin/true" >> /etc/modprobe.d/disable-kvm.conf If the system requires this module to work correctly, this mitigation may not be suitable. If you need further assistance, see the KCS article https://access.redhat.com/solutions/41278 or contact Red Hat Global Support Services. 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)