RHSA-2024:1249HighCVSS 8.1

Red Hat Security Advisory: kernel security and bug fix update

Published
March 12, 2024
Last Modified
August 6, 2026

🔗 CVE IDs covered (6)

CVE-2023-45871 →CVE-2024-1086 →CVE-2024-26602 →CVE-2022-42896 →CVE-2023-4921 →CVE-2023-38409 →

📋 Description

CVE-2022-42896 — kernel: use-after-free in l2cap_connect and l2cap_le_connect_req in net/bluetooth/l2cap_core.c CVE-2023-4921 — kernel: use-after-free in sch_qfq network scheduler CVE-2023-38409 — kernel: fbcon: out-of-sync arrays in fbcon_mode_deleted due to wrong con2fb_map assignment CVE-2023-45871 — kernel: IGB driver inadequate buffer size for frames larger than MTU CVE-2024-1086 — kernel: nf_tables: use-after-free vulnerability in the nft_verdict_init() function CVE-2024-26602 — kernel: sched/membarrier: reduce the ability to hammer on sys_membarrier

🎯 Affected products162

  • Red Hat Enterprise Linux Client (v. 7)
  • Red Hat Enterprise Linux Client Optional (v. 7)
  • Red Hat Enterprise Linux ComputeNode Optional (v. 7)
  • Red Hat Enterprise Linux Server (v. 7)
  • Red Hat Enterprise Linux Server Optional (v. 7)
  • Red Hat Enterprise Linux Workstation (v. 7)
  • Red Hat Enterprise Linux Workstation Optional (v. 7)
  • bpftool-0:3.10.0-1160.114.2.el7.ppc64 as a component of Red Hat Enterprise Linux Server (v. 7)
  • bpftool-0:3.10.0-1160.114.2.el7.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7)
  • bpftool-0:3.10.0-1160.114.2.el7.s390x as a component of Red Hat Enterprise Linux Server (v. 7)
  • bpftool-0:3.10.0-1160.114.2.el7.x86_64 as a component of Red Hat Enterprise Linux Client (v. 7)
  • bpftool-0:3.10.0-1160.114.2.el7.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7)
  • bpftool-0:3.10.0-1160.114.2.el7.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 7)
  • bpftool-debuginfo-0:3.10.0-1160.114.2.el7.ppc64 as a component of Red Hat Enterprise Linux Server (v. 7)
  • bpftool-debuginfo-0:3.10.0-1160.114.2.el7.ppc64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)
  • bpftool-debuginfo-0:3.10.0-1160.114.2.el7.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7)
  • bpftool-debuginfo-0:3.10.0-1160.114.2.el7.ppc64le as a component of Red Hat Enterprise Linux Server Optional (v. 7)
  • bpftool-debuginfo-0:3.10.0-1160.114.2.el7.s390x as a component of Red Hat Enterprise Linux Server (v. 7)
  • bpftool-debuginfo-0:3.10.0-1160.114.2.el7.x86_64 as a component of Red Hat Enterprise Linux Client (v. 7)
  • bpftool-debuginfo-0:3.10.0-1160.114.2.el7.x86_64 as a component of Red Hat Enterprise Linux Client Optional (v. 7)
  • bpftool-debuginfo-0:3.10.0-1160.114.2.el7.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)
  • bpftool-debuginfo-0:3.10.0-1160.114.2.el7.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7)
  • bpftool-debuginfo-0:3.10.0-1160.114.2.el7.x86_64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)
  • bpftool-debuginfo-0:3.10.0-1160.114.2.el7.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 7)
  • bpftool-debuginfo-0:3.10.0-1160.114.2.el7.x86_64 as a component of Red Hat Enterprise Linux Workstation Optional (v. 7)
  • kernel-0:3.10.0-1160.114.2.el7.ppc64 as a component of Red Hat Enterprise Linux Server (v. 7)
  • kernel-0:3.10.0-1160.114.2.el7.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7)
  • kernel-0:3.10.0-1160.114.2.el7.s390x as a component of Red Hat Enterprise Linux Server (v. 7)
  • kernel-0:3.10.0-1160.114.2.el7.src as a component of Red Hat Enterprise Linux Client (v. 7)
  • kernel-0:3.10.0-1160.114.2.el7.src as a component of Red Hat Enterprise Linux Server (v. 7)
  • +132 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: This flaw can be mitigated by disabling Bluetooth on the operating system level. The kernel modules can be prevented from being loaded by using system-wide modprobe rules. For instructions on how to disable Bluetooth on RHEL please refer to https://access.redhat.com/solutions/2682931. Alternatively Bluetooth can be disabled within the hardware or at BIOS level which will also provide an effective mitigation as the kernel will not be able to detect that Bluetooth hardware is present on the system. Workaround: Mitigation for this issue is to skip loading the affected module sch_qfq onto the system until we have a fix available. This can be done by a blacklist mechanism and 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: Mitigation for this issue is to skip loading the affected module "fbcon" onto the system until we have a fix available. This can be done by a blacklist mechanism and will ensure the driver is not loaded at boot time. ~~~ How do I blacklist a kernel module to prevent it from loading automatically? https://access.redhat.com/solutions/41278 ~~~ 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: 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.

🔗 References (9)