RHSA-2024:1404HighCVSS 7.8

Red Hat Security Advisory: kernel security and bug fix update

Published
March 19, 2024
Last Modified
August 10, 2026

🔗 CVE IDs covered (37)

CVE-2023-45862 →CVE-2023-51043 →CVE-2023-2166 →CVE-2022-3594 →CVE-2022-45869 →CVE-2023-6606 →CVE-2023-5633 →CVE-2023-6817 →CVE-2023-28772 →CVE-2023-30456 →CVE-2023-31084 →CVE-2024-0646 →CVE-2022-36402 →CVE-2023-2176 →CVE-2023-53421 →CVE-2021-43975 →CVE-2022-4744 →CVE-2022-38096 →CVE-2022-40133 →CVE-2022-45887 →CVE-2023-1382 →CVE-2023-51042 →CVE-2022-3545 →CVE-2022-50148 →CVE-2023-4921 →CVE-2023-33951 →CVE-2024-0565 →CVE-2024-1086 →CVE-2022-28388 →CVE-2022-41858 →CVE-2023-6610 →CVE-2023-6931 →CVE-2023-6932 →CVE-2023-40283 →CVE-2022-38457 →CVE-2023-7192 →CVE-2023-33952 →

📋 Description

CVE-2021-43975 — kernel: out-of-bounds write in hw_atl_utils_fw_rpc_wait() in drivers/net/ethernet/aquantia/atlantic/hw_atl/hw_atl_utils.c CVE-2022-3545 — kernel: nfp: use-after-free in area_cache_get() CVE-2022-3594 — kernel: Rate limit overflow messages in r8152 in intr_callback CVE-2022-4744 — kernel: tun: avoid double free in tun_free_netdev CVE-2022-28388 — kernel: double free in usb_8dev_start_xmit in drivers/net/can/usb/usb_8dev.c CVE-2022-36402 — kernel: vmwgfx: integer overflow in vmwgfx_execbuf.c CVE-2022-38096 — kernel: vmwgfx: NULL pointer dereference in vmw_cmd_dx_define_query CVE-2022-38457 — kernel: vmwgfx: use-after-free in vmw_cmd_res_check CVE-2022-40133 — kernel: vmwgfx: use-after-free in vmw_execbuf_tie_context CVE-2022-41858 — kernel: null-ptr-deref vulnerabilities in sl_tx_timeout in drivers/net/slip CVE-2022-45869 — kernel: KVM: x86/mmu: race condition in direct_page_fault() CVE-2022-45887 — kernel: memory leak in ttusb_dec_exit_dvb() in media/usb/ttusb-dec/ttusb_dec.c CVE-2022-50148 — kernel: kernfs: fix potential NULL dereference in __kernfs_remove CVE-2023-1382 — kernel: denial of service in tipc_conn_close CVE-2023-2166 — kernel: NULL pointer dereference in can_rcv_filter CVE-2023-2176 — kernel: Slab-out-of-bound read in compare_netdev_and_ip CVE-2023-4921 — kernel: use-after-free in sch_qfq network scheduler CVE-2023-5633 — kernel: vmwgfx: reference count issue leads to use-after-free in surface handling CVE-2023-6606 — kernel: Out-Of-Bounds Read vulnerability in smbCalcSize CVE-2023-6610 — kernel: OOB Access in smb2_dump_detail CVE-2023-6817 — kernel: inactive elements in nft_pipapo_walk CVE-2023-6931 — kernel: Out of boundary write in perf_read_group() as result of overflow a perf_event's read_size CVE-2023-6932 — kernel: use-after-free in IPv4 IGMP CVE-2023-7192 — kernel: refcount leak in ctnetlink_create_conntrack() CVE-2023-28772 — kernel: lib/seq_buf.c has a seq_buf_putmem_hex buffer overflow CVE-2023-30456 — kernel: KVM: nVMX: missing consistency checks for CR0 and CR4 CVE-2023-31084 — kernel: blocking operation in dvb_frontend_get_event and wait_event_interruptible CVE-2023-33951 — kernel: vmwgfx: race condition leading to information disclosure vulnerability CVE-2023-33952 — kernel: vmwgfx: double free within the handling of vmw_buffer_object objects CVE-2023-40283 — kernel: use-after-free in l2cap_sock_release in net/bluetooth/l2cap_sock.c CVE-2023-45862 — kernel: drivers/usb/storage/ene_ub6250.c CVE-2023-51042 — kernel: use-after-free in amdgpu_cs_wait_all_fences in drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c CVE-2023-51043 — kernel: use-after-free during a race condition between a nonblocking atomic commit and a driver unload in drivers/gpu/drm/drm_atomic.c CVE-2023-53421 — kernel: blk-cgroup: Reinit blkg_iostat_set after clearing in blkcg_reset_stats() CVE-2024-0565 — kernel: CIFS Filesystem Decryption Improper Input Validation Remote Code Execution Vulnerability in function receive_encrypted_standard of client CVE-2024-0646 — kernel: ktls overwrites readonly memory pages when using function splice with a ktls socket as destination CVE-2024-1086 — kernel: nf_tables: use-after-free vulnerability in the nft_verdict_init() function

🎯 Affected products122

  • Red Hat CodeReady Linux Builder EUS (v.8.8)
  • Red Hat Enterprise Linux BaseOS EUS (v.8.8)
  • bpftool-0:4.18.0-477.51.1.el8_8.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.8)
  • bpftool-0:4.18.0-477.51.1.el8_8.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.8)
  • bpftool-0:4.18.0-477.51.1.el8_8.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.8)
  • bpftool-0:4.18.0-477.51.1.el8_8.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.8)
  • bpftool-debuginfo-0:4.18.0-477.51.1.el8_8.aarch64 as a component of Red Hat CodeReady Linux Builder EUS (v.8.8)
  • bpftool-debuginfo-0:4.18.0-477.51.1.el8_8.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.8)
  • bpftool-debuginfo-0:4.18.0-477.51.1.el8_8.ppc64le as a component of Red Hat CodeReady Linux Builder EUS (v.8.8)
  • bpftool-debuginfo-0:4.18.0-477.51.1.el8_8.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.8)
  • bpftool-debuginfo-0:4.18.0-477.51.1.el8_8.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.8)
  • bpftool-debuginfo-0:4.18.0-477.51.1.el8_8.x86_64 as a component of Red Hat CodeReady Linux Builder EUS (v.8.8)
  • bpftool-debuginfo-0:4.18.0-477.51.1.el8_8.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.8)
  • kernel-0:4.18.0-477.51.1.el8_8.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.8)
  • kernel-0:4.18.0-477.51.1.el8_8.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.8)
  • kernel-0:4.18.0-477.51.1.el8_8.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.8)
  • kernel-0:4.18.0-477.51.1.el8_8.src as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.8)
  • kernel-0:4.18.0-477.51.1.el8_8.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.8)
  • kernel-abi-stablelists-0:4.18.0-477.51.1.el8_8.noarch as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.8)
  • kernel-core-0:4.18.0-477.51.1.el8_8.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.8)
  • kernel-core-0:4.18.0-477.51.1.el8_8.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.8)
  • kernel-core-0:4.18.0-477.51.1.el8_8.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.8)
  • kernel-core-0:4.18.0-477.51.1.el8_8.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.8)
  • kernel-debug-0:4.18.0-477.51.1.el8_8.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.8)
  • kernel-debug-0:4.18.0-477.51.1.el8_8.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.8)
  • kernel-debug-0:4.18.0-477.51.1.el8_8.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.8)
  • kernel-debug-0:4.18.0-477.51.1.el8_8.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.8)
  • kernel-debug-core-0:4.18.0-477.51.1.el8_8.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.8)
  • kernel-debug-core-0:4.18.0-477.51.1.el8_8.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.8)
  • kernel-debug-core-0:4.18.0-477.51.1.el8_8.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.8)
  • +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: To mitigate this issue, prevent the module atlantic 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: 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: This flaw can be mitigated by preventing the affected Realtek RTL8152/RTL8153 Based USB Ethernet Adapters (r8152) kernel module from loading during the boot time. Ensure the module is added into 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, prevent the tun module 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: To mitigate this issue, prevent module usb_8dev 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: 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: 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: This vulnerability can be mitigated by disabling the nested virtualization feature. For Intel: ``` # modprobe -r kvm_intel # modprobe kvm_intel nested=0 ``` For AMD: ``` # modprobe -r kvm_amd # modprobe kvm_amd nested=0 ``` Workaround: To mitigate this issue, it is possible to prevent the affected code from being loaded by blacklisting the `ttusb_dec` kernel module. For instructions on how to blacklist a kernel module, please see https://access.redhat.com/solutions/41278. Workaround: This flaw can be mitigated by preventing the affected transparent inter-process communication (TIPC) protocol kernel module from loading during the boot time. Ensure the module is added into 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 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 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: This flaw can be mitigated by turning off 3D acceleration in VMware (if possible) or preventing the affected `vmwgfx` kernel module from being loaded. For instructions on how to blacklist a kernel module, please see https://access.redhat.com/solutions/41278. Workaround: To mitigate this issue, prevent module cifs 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: 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: It is not possible to trigger this issue with the default kernel.perf_event_paranoid sysctl value 2. You may check it with: cat /proc/sys/kernel/perf_event_paranoid Workaround: Triggering this issue 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. Alternatively, skip loading the affected netfilter module (i.e., nf_conntrack_netlink) onto the system until we have a fix available. This can be done by a blacklist mechanism which 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: This vulnerability can be mitigated by disabling the nested virtualization feature: ``` # modprobe -r kvm_intel # modprobe kvm_intel nested=0 ``` Workaround: This flaw can be mitigated by preventing the affected `vmwgfx` kernel module from being loaded. For instructions on how to blacklist a kernel module, please see https://access.redhat.com/solutions/41278. Workaround: To mitigate this issue, prevent module ums-eneub6250 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: To mitigate this issue, prevent the amdgpu module from loading. Please see https://access.redhat.com/solutions/41278 for more information on how to prevent kernel modules from loading. Note that if a system has an AMD GPU, this may make certain features of that GPU unavailable. Workaround: To mitigate this issue, prevent module drm 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: 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. 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 (38)