RHSA-2022:5220HighCVSS 7.8

Red Hat Security Advisory: kernel security and bug fix update

Published
June 28, 2022
Last Modified
October 14, 2026

🔗 CVE IDs covered (7)

CVE-2020-29368 →CVE-2021-47435 →CVE-2022-1012 →CVE-2022-1729 →CVE-2022-1966 · pendingCVE-2022-27666 →CVE-2022-32250 →

📋 Description

CVE-2020-29368 — kernel: the copy-on-write implementation can grant unintended write access because of a race condition in a THP mapcount check CVE-2021-47435 — kernel: dm: fix mempool NULL pointer race when completing IO CVE-2022-1012 — kernel: Small table perturb size in the TCP source port generation algorithm can lead to information leak CVE-2022-1729 — kernel: race condition in perf_event_open leads to privilege escalation CVE-2022-1966 — kernel: netfilter: nf_tables: incorrect NFT_STATEFUL_EXPR check leads to a use-after-free (write) CVE-2022-27666 — kernel: buffer overflow in IPsec ESP transformation code CVE-2022-32250 — kernel: a use-after-free write in the netfilter subsystem can lead to privilege escalation to root

🎯 Affected products122

  • Red Hat CodeReady Linux Builder EUS (v. 8.2)
  • Red Hat Enterprise Linux BaseOS EUS (v. 8.2)
  • bpftool-0:4.18.0-193.87.1.el8_2.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)
  • bpftool-0:4.18.0-193.87.1.el8_2.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)
  • bpftool-0:4.18.0-193.87.1.el8_2.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)
  • bpftool-0:4.18.0-193.87.1.el8_2.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)
  • bpftool-debuginfo-0:4.18.0-193.87.1.el8_2.aarch64 as a component of Red Hat CodeReady Linux Builder EUS (v. 8.2)
  • bpftool-debuginfo-0:4.18.0-193.87.1.el8_2.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)
  • bpftool-debuginfo-0:4.18.0-193.87.1.el8_2.ppc64le as a component of Red Hat CodeReady Linux Builder EUS (v. 8.2)
  • bpftool-debuginfo-0:4.18.0-193.87.1.el8_2.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)
  • bpftool-debuginfo-0:4.18.0-193.87.1.el8_2.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)
  • bpftool-debuginfo-0:4.18.0-193.87.1.el8_2.x86_64 as a component of Red Hat CodeReady Linux Builder EUS (v. 8.2)
  • bpftool-debuginfo-0:4.18.0-193.87.1.el8_2.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)
  • kernel-0:4.18.0-193.87.1.el8_2.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)
  • kernel-0:4.18.0-193.87.1.el8_2.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)
  • kernel-0:4.18.0-193.87.1.el8_2.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)
  • kernel-0:4.18.0-193.87.1.el8_2.src as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)
  • kernel-0:4.18.0-193.87.1.el8_2.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)
  • kernel-abi-whitelists-0:4.18.0-193.87.1.el8_2.noarch as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)
  • kernel-core-0:4.18.0-193.87.1.el8_2.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)
  • kernel-core-0:4.18.0-193.87.1.el8_2.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)
  • kernel-core-0:4.18.0-193.87.1.el8_2.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)
  • kernel-core-0:4.18.0-193.87.1.el8_2.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)
  • kernel-debug-0:4.18.0-193.87.1.el8_2.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)
  • kernel-debug-0:4.18.0-193.87.1.el8_2.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)
  • kernel-debug-0:4.18.0-193.87.1.el8_2.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)
  • kernel-debug-0:4.18.0-193.87.1.el8_2.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)
  • kernel-debug-core-0:4.18.0-193.87.1.el8_2.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)
  • kernel-debug-core-0:4.18.0-193.87.1.el8_2.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)
  • kernel-debug-core-0:4.18.0-193.87.1.el8_2.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)
  • +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 don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability. Workaround: The given exploit needs CAP_NET_ADMIN to set up IPsec SA and a user namespace is used to get that capability, so disabling unprivileged user namespaces gives some protection. ~~~ On non-containerized deployments of Red Hat Enterprise Linux 8, you can disable user namespaces by setting user.max_user_namespaces to 0: # echo "user.max_user_namespaces=0" > /etc/sysctl.d/userns.conf # sysctl -p /etc/sysctl.d/userns.conf On containerized deployments, such as Red Hat OpenShift Container Platform, do not use this mitigation as the functionality is needed to be enabled. ~~~ Note: If the target system is already using IPsec and has SA configured, then no additional privileges are needed to exploit the issue. Workaround: In order to trigger the issue, it requires the ability to create user/net namespaces. On non-containerized deployments of Red Hat Enterprise Linux 8, you can disable user namespaces by setting user.max_user_namespaces to 0: # echo "user.max_user_namespaces=0" > /etc/sysctl.d/userns.conf # sysctl -p /etc/sysctl.d/userns.conf On containerized deployments, such as Red Hat OpenShift Container Platform, do not use this mitigation as the functionality is needed to be enabled.

🔗 References (8)