RHSA-2024:1268HighCVSS 8.8

Red Hat Security Advisory: kernel security and bug fix update

Published
March 12, 2024
Last Modified
August 6, 2026

🔗 CVE IDs covered (16)

CVE-2022-3545 →CVE-2023-4623 →CVE-2023-5178 →CVE-2023-6817 →CVE-2023-31436 →CVE-2023-45871 →CVE-2022-38096 →CVE-2022-41858 →CVE-2023-3390 →CVE-2023-3611 →CVE-2023-35001 →CVE-2023-4921 →CVE-2023-38409 →CVE-2023-40283 →CVE-2024-0646 →CVE-2022-40982 →

📋 Description

CVE-2022-3545 — kernel: nfp: use-after-free in area_cache_get() CVE-2022-38096 — kernel: vmwgfx: NULL pointer dereference in vmw_cmd_dx_define_query CVE-2022-40982 — hw: Intel: Gather Data Sampling (GDS) side channel vulnerability CVE-2022-41858 — kernel: null-ptr-deref vulnerabilities in sl_tx_timeout in drivers/net/slip CVE-2023-3390 — kernel: UAF in nftables when nft_set_lookup_global triggered after handling named and anonymous sets in batch requests CVE-2023-3611 — kernel: net/sched: sch_qfq component can be exploited if in qfq_change_agg function happens qfq_enqueue overhead CVE-2023-4623 — kernel: net/sched: sch_hfsc UAF CVE-2023-4921 — kernel: use-after-free in sch_qfq network scheduler CVE-2023-5178 — kernel: use after free in nvmet_tcp_free_crypto in NVMe CVE-2023-6817 — kernel: inactive elements in nft_pipapo_walk CVE-2023-31436 — kernel: out-of-bounds write in qfq_change_class function CVE-2023-35001 — kernel: nf_tables: stack-out-of-bounds-read in nft_byteorder_eval() CVE-2023-38409 — kernel: fbcon: out-of-sync arrays in fbcon_mode_deleted due to wrong con2fb_map assignment CVE-2023-40283 — kernel: use-after-free in l2cap_sock_release in net/bluetooth/l2cap_sock.c CVE-2023-45871 — kernel: IGB driver inadequate buffer size for frames larger than MTU CVE-2024-0646 — kernel: ktls overwrites readonly memory pages when using function splice with a ktls socket as destination

🎯 Affected products100

  • Red Hat Enterprise Linux BaseOS AUS (v. 8.2)
  • Red Hat Enterprise Linux BaseOS E4S (v. 8.2)
  • Red Hat Enterprise Linux BaseOS TUS (v. 8.2)
  • bpftool-0:4.18.0-193.128.1.el8_2.ppc64le as a component of Red Hat Enterprise Linux BaseOS E4S (v. 8.2)
  • bpftool-0:4.18.0-193.128.1.el8_2.x86_64 as a component of Red Hat Enterprise Linux BaseOS AUS (v. 8.2)
  • bpftool-0:4.18.0-193.128.1.el8_2.x86_64 as a component of Red Hat Enterprise Linux BaseOS E4S (v. 8.2)
  • bpftool-0:4.18.0-193.128.1.el8_2.x86_64 as a component of Red Hat Enterprise Linux BaseOS TUS (v. 8.2)
  • bpftool-debuginfo-0:4.18.0-193.128.1.el8_2.ppc64le as a component of Red Hat Enterprise Linux BaseOS E4S (v. 8.2)
  • bpftool-debuginfo-0:4.18.0-193.128.1.el8_2.x86_64 as a component of Red Hat Enterprise Linux BaseOS AUS (v. 8.2)
  • bpftool-debuginfo-0:4.18.0-193.128.1.el8_2.x86_64 as a component of Red Hat Enterprise Linux BaseOS E4S (v. 8.2)
  • bpftool-debuginfo-0:4.18.0-193.128.1.el8_2.x86_64 as a component of Red Hat Enterprise Linux BaseOS TUS (v. 8.2)
  • kernel-0:4.18.0-193.128.1.el8_2.ppc64le as a component of Red Hat Enterprise Linux BaseOS E4S (v. 8.2)
  • kernel-0:4.18.0-193.128.1.el8_2.src as a component of Red Hat Enterprise Linux BaseOS AUS (v. 8.2)
  • kernel-0:4.18.0-193.128.1.el8_2.src as a component of Red Hat Enterprise Linux BaseOS E4S (v. 8.2)
  • kernel-0:4.18.0-193.128.1.el8_2.src as a component of Red Hat Enterprise Linux BaseOS TUS (v. 8.2)
  • kernel-0:4.18.0-193.128.1.el8_2.x86_64 as a component of Red Hat Enterprise Linux BaseOS AUS (v. 8.2)
  • kernel-0:4.18.0-193.128.1.el8_2.x86_64 as a component of Red Hat Enterprise Linux BaseOS E4S (v. 8.2)
  • kernel-0:4.18.0-193.128.1.el8_2.x86_64 as a component of Red Hat Enterprise Linux BaseOS TUS (v. 8.2)
  • kernel-abi-whitelists-0:4.18.0-193.128.1.el8_2.noarch as a component of Red Hat Enterprise Linux BaseOS AUS (v. 8.2)
  • kernel-abi-whitelists-0:4.18.0-193.128.1.el8_2.noarch as a component of Red Hat Enterprise Linux BaseOS E4S (v. 8.2)
  • kernel-abi-whitelists-0:4.18.0-193.128.1.el8_2.noarch as a component of Red Hat Enterprise Linux BaseOS TUS (v. 8.2)
  • kernel-core-0:4.18.0-193.128.1.el8_2.ppc64le as a component of Red Hat Enterprise Linux BaseOS E4S (v. 8.2)
  • kernel-core-0:4.18.0-193.128.1.el8_2.x86_64 as a component of Red Hat Enterprise Linux BaseOS AUS (v. 8.2)
  • kernel-core-0:4.18.0-193.128.1.el8_2.x86_64 as a component of Red Hat Enterprise Linux BaseOS E4S (v. 8.2)
  • kernel-core-0:4.18.0-193.128.1.el8_2.x86_64 as a component of Red Hat Enterprise Linux BaseOS TUS (v. 8.2)
  • kernel-debug-0:4.18.0-193.128.1.el8_2.ppc64le as a component of Red Hat Enterprise Linux BaseOS E4S (v. 8.2)
  • kernel-debug-0:4.18.0-193.128.1.el8_2.x86_64 as a component of Red Hat Enterprise Linux BaseOS AUS (v. 8.2)
  • kernel-debug-0:4.18.0-193.128.1.el8_2.x86_64 as a component of Red Hat Enterprise Linux BaseOS E4S (v. 8.2)
  • kernel-debug-0:4.18.0-193.128.1.el8_2.x86_64 as a component of Red Hat Enterprise Linux BaseOS TUS (v. 8.2)
  • kernel-debug-core-0:4.18.0-193.128.1.el8_2.ppc64le as a component of Red Hat Enterprise Linux BaseOS E4S (v. 8.2)
  • +70 more not shown

✅ Remediation

Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, 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 preventing the affected Netronome Flow Processor (NFP) kernel module from loading during the boot time; ensure the module is added to the blacklist file. ~~~ Refer: How do I blacklist a kernel module to prevent it from loading automatically? https://access.redhat.com/solutions/41278 ~~~ Workaround: To mitigate this issue, it is possible to prevent the affected code from being loaded by blacklisting the vmwgfx kernel module. For instructions relating to blacklisting a kernel module, please see https://access.redhat.com/solutions/41278. Workaround: The vulnerability can be mitigated by installing the CPU microcode package microcode_ctl version 20230808. Workaround: This flaw can be mitigated by preventing the affected slip driver from loading during the boot time, and ensuring the module is added to the blacklist file. ~~~ Refer: 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 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: To mitigate this issue, prevent the module sch_hfsc from being loaded by blacklisting the 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: 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: To mitigate this issue, prevent the module, sch_qfq from being loaded. Please see https://access.redhat.com/solutions/41278 for information on how to blacklist a kernel module to prevent it from loading automatically. Workaround: To mitigate this issue, it is possible to prevent the affected code from being loaded by blacklisting the kernel netfilter module. For instructions relating to how to blacklist a kernel module refer to: 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: To mitigate this issue, prevent module tls from being loaded. Please see https://access.redhat.com/solutions/41278 for how to blacklist a kernel module to prevent it from loading automatically.

🔗 References (19)