RHSA-2024:3421HighCVSS 7.8

Red Hat Security Advisory: kernel security and bug fix update

Published
May 28, 2024
Last Modified
August 25, 2026

🔗 CVE IDs covered (16)

CVE-2023-53304 →CVE-2023-53566 →CVE-2024-1086 →CVE-2024-25743 →CVE-2022-50048 →CVE-2023-6817 →CVE-2023-52628 →CVE-2023-52924 →CVE-2023-4244 →CVE-2023-52993 →CVE-2024-25742 →CVE-2022-49920 →CVE-2023-54035 →CVE-2024-26586 →CVE-2022-50213 →CVE-2023-6240 →

📋 Description

CVE-2022-49920 — kernel: netfilter: nf_tables: netlink notifier might race to release objects CVE-2022-50048 — kernel: netfilter: nf_tables: possible module reference underflow in error path CVE-2022-50213 — kernel: netfilter: nf_tables: do not allow SET_ID to refer to another table CVE-2023-4244 — kernel: Use-after-free in nft_verdict_dump due to a race between set GC and transaction CVE-2023-6240 — kernel: Marvin vulnerability side-channel leakage in the RSA decryption operation CVE-2023-6817 — kernel: inactive elements in nft_pipapo_walk CVE-2023-52628 — kernel: netfilter: nftables: exthdr: fix 4-byte stack OOB write CVE-2023-52924 — kernel: netfilter: nf_tables: don't skip expired elements during walk CVE-2023-52993 — kernel: x86/i8259: Mark legacy PIC interrupts with IRQ_LEVEL CVE-2023-53304 — kernel: Linux kernel: Denial of Service in netfilter due to improper garbage collection CVE-2023-53566 — kernel: netfilter: nft_set_rbtree: fix null deref on element insertion CVE-2023-54035 — kernel: netfilter: nf_tables: fix underflow in chain reference counter CVE-2024-1086 — kernel: nf_tables: use-after-free vulnerability in the nft_verdict_init() function CVE-2024-25742 — hw: amd: Instruction raise #VC exception at exit CVE-2024-25743 — hw: amd: Instruction raise #VC exception at exit CVE-2024-26586 — kernel: mlxsw: spectrum_acl_tcam: Fix stack corruption

🎯 Affected products169

  • Red Hat CodeReady Linux Builder EUS (v.9.0)
  • Red Hat Enterprise Linux AppStream EUS (v.9.0)
  • Red Hat Enterprise Linux BaseOS EUS (v.9.0)
  • bpftool-0:5.14.0-70.101.1.el9_0.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.0)
  • bpftool-0:5.14.0-70.101.1.el9_0.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.0)
  • bpftool-0:5.14.0-70.101.1.el9_0.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.0)
  • bpftool-0:5.14.0-70.101.1.el9_0.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.0)
  • bpftool-debuginfo-0:5.14.0-70.101.1.el9_0.aarch64 as a component of Red Hat CodeReady Linux Builder EUS (v.9.0)
  • bpftool-debuginfo-0:5.14.0-70.101.1.el9_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v.9.0)
  • bpftool-debuginfo-0:5.14.0-70.101.1.el9_0.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.0)
  • bpftool-debuginfo-0:5.14.0-70.101.1.el9_0.ppc64le as a component of Red Hat CodeReady Linux Builder EUS (v.9.0)
  • bpftool-debuginfo-0:5.14.0-70.101.1.el9_0.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v.9.0)
  • bpftool-debuginfo-0:5.14.0-70.101.1.el9_0.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.0)
  • bpftool-debuginfo-0:5.14.0-70.101.1.el9_0.s390x as a component of Red Hat CodeReady Linux Builder EUS (v.9.0)
  • bpftool-debuginfo-0:5.14.0-70.101.1.el9_0.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v.9.0)
  • bpftool-debuginfo-0:5.14.0-70.101.1.el9_0.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.0)
  • bpftool-debuginfo-0:5.14.0-70.101.1.el9_0.x86_64 as a component of Red Hat CodeReady Linux Builder EUS (v.9.0)
  • bpftool-debuginfo-0:5.14.0-70.101.1.el9_0.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v.9.0)
  • bpftool-debuginfo-0:5.14.0-70.101.1.el9_0.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.0)
  • kernel-0:5.14.0-70.101.1.el9_0.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.0)
  • kernel-0:5.14.0-70.101.1.el9_0.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.0)
  • kernel-0:5.14.0-70.101.1.el9_0.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.0)
  • kernel-0:5.14.0-70.101.1.el9_0.src as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.0)
  • kernel-0:5.14.0-70.101.1.el9_0.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.0)
  • kernel-abi-stablelists-0:5.14.0-70.101.1.el9_0.noarch as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.0)
  • kernel-core-0:5.14.0-70.101.1.el9_0.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.0)
  • kernel-core-0:5.14.0-70.101.1.el9_0.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.0)
  • kernel-core-0:5.14.0-70.101.1.el9_0.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.0)
  • kernel-core-0:5.14.0-70.101.1.el9_0.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.0)
  • kernel-debug-0:5.14.0-70.101.1.el9_0.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.0)
  • +139 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: To mitigate this issue, prevent module sch_hfsc from being loaded. Please see https://access.redhat.com/solutions/41278 for how to blacklist a kernel module to prevent it from loading automatically. 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 to skip loading the affected module "nftables" onto the system till we have a fix available, this can be done by a blacklist mechanism, this will ensure 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 ~~~ 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. Workaround: 1. This flaw can be mitigated by preventing the affected netfilter (nf_tables) kernel module from being loaded. For instructions on how to blacklist a kernel module, please see https://access.redhat.com/solutions/41278. 2. If the module cannot be disabled, on non-containerized deployments of Red Hat Enterprise Linux, the mitigation is to disable user namespaces: ``` # 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 the second mitigation (disabling user namespaces) as the functionality is needed to be enabled. The first mitigation (blacklisting nf_tables) is still viable for containerized deployments, providing the environment is not using netfilter. Workaround: 1. This flaw can be mitigated by preventing the affected netfilter (nf_tables) kernel module from being loaded. For instructions on how to blacklist a kernel module, please see https://access.redhat.com/solutions/41278. 2. If the module cannot be disabled, on non-containerized deployments of Red Hat Enterprise Linux, the mitigation is to disable user namespaces: ``` # 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 the second mitigation (disabling user namespaces) as the functionality is needed to be enabled. The first mitigation (blacklisting nf_tables) is still viable for containerized deployments, providing the environment is not using netfilter. Workaround: To mitigate this issue, prevent the mlxsw_spectrum module from being loaded. Please see https://access.redhat.com/solutions/41278 for information on blacklisting a kernel module to prevent it from loading automatically.

🔗 References (10)