RHSA-2024:5255HighCVSS 7.8

Red Hat Security Advisory: kernel security update

Published
August 13, 2024
Last Modified
October 16, 2026

🔗 CVE IDs covered (22)

CVE-2024-35910 →CVE-2024-36000 →CVE-2024-36971 →CVE-2022-48627 →CVE-2024-26733 →CVE-2024-26870 →CVE-2023-20569 →CVE-2023-52610 →CVE-2024-26640 →CVE-2024-35852 →CVE-2024-36020 →CVE-2023-52448 →CVE-2024-26583 →CVE-2024-26585 →CVE-2024-26704 →CVE-2024-36886 →CVE-2024-38538 →CVE-2024-38555 →CVE-2024-26584 →CVE-2024-26686 →CVE-2024-26773 →CVE-2024-26982 →

📋 Description

CVE-2022-48627 — kernel: vt: fix memory overlapping when deleting chars in the buffer CVE-2023-20569 — amd: Return Address Predictor vulnerability leading to information disclosure CVE-2023-52448 — kernel: gfs2: Fix kernel NULL pointer dereference in gfs2_rgrp_dump CVE-2023-52610 — kernel: net/sched: act_ct: fix skb leak and crash on ooo frags CVE-2024-26583 — kernel: tls: race between async notify and socket close CVE-2024-26584 — kernel: tls: handle backlogging of crypto requests CVE-2024-26585 — kernel: tls: race between tx work scheduling and socket close CVE-2024-26640 — kernel: tcp: add sanity checks to rx zerocopy CVE-2024-26686 — kernel: fs/proc: do_task_stat: use sig->stats_lock to gather the threads/children stats CVE-2024-26704 — kernel: ext4: fix double-free of blocks due to wrong extents moved_len CVE-2024-26733 — kernel: arp: Prevent overflow in arp_req_get(). CVE-2024-26773 — kernel: ext4: avoid allocating blocks from corrupted group in ext4_mb_try_best_found() CVE-2024-26870 — kernel: NFSv4.2: fix nfs4_listxattr kernel BUG at mm/usercopy.c:102 CVE-2024-26982 — kernel: Squashfs: check the inode number is not the invalid value of zero CVE-2024-35852 — kernel: mlxsw: spectrum_acl_tcam: Fix memory leak when canceling rehash work CVE-2024-35910 — kernel: tcp: properly terminate timers for kernel sockets CVE-2024-36000 — kernel: mm/hugetlb: fix missing hugetlb_lock for resv uncharge CVE-2024-36020 — kernel: i40e: fix vf may be used uninitialized in this function warning CVE-2024-36886 — kernel: TIPC message reassembly use-after-free remote code execution vulnerability CVE-2024-36971 — kernel: net: kernel: UAF in network route management CVE-2024-38538 — kernel: net: bridge: xmit: make sure we have at least eth header len bytes CVE-2024-38555 — kernel: net/mlx5: Discard command completions in internal error

🎯 Affected products130

  • Red Hat CodeReady Linux Builder EUS (v.8.8)
  • Red Hat Enterprise Linux BaseOS EUS (v.8.8)
  • bpftool-0:4.18.0-477.67.1.el8_8.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.8)
  • bpftool-0:4.18.0-477.67.1.el8_8.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.8)
  • bpftool-0:4.18.0-477.67.1.el8_8.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.8)
  • bpftool-0:4.18.0-477.67.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.67.1.el8_8.aarch64 as a component of Red Hat CodeReady Linux Builder EUS (v.8.8)
  • bpftool-debuginfo-0:4.18.0-477.67.1.el8_8.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.8)
  • bpftool-debuginfo-0:4.18.0-477.67.1.el8_8.ppc64le as a component of Red Hat CodeReady Linux Builder EUS (v.8.8)
  • bpftool-debuginfo-0:4.18.0-477.67.1.el8_8.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.8)
  • bpftool-debuginfo-0:4.18.0-477.67.1.el8_8.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.8)
  • bpftool-debuginfo-0:4.18.0-477.67.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.67.1.el8_8.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.8)
  • kernel-0:4.18.0-477.67.1.el8_8.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.8)
  • kernel-0:4.18.0-477.67.1.el8_8.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.8)
  • kernel-0:4.18.0-477.67.1.el8_8.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.8)
  • kernel-0:4.18.0-477.67.1.el8_8.src as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.8)
  • kernel-0:4.18.0-477.67.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.67.1.el8_8.noarch as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.8)
  • kernel-core-0:4.18.0-477.67.1.el8_8.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.8)
  • kernel-core-0:4.18.0-477.67.1.el8_8.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.8)
  • kernel-core-0:4.18.0-477.67.1.el8_8.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.8)
  • kernel-core-0:4.18.0-477.67.1.el8_8.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.8)
  • kernel-cross-headers-0:4.18.0-477.67.1.el8_8.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.8)
  • kernel-cross-headers-0:4.18.0-477.67.1.el8_8.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.8)
  • kernel-cross-headers-0:4.18.0-477.67.1.el8_8.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.8)
  • kernel-cross-headers-0:4.18.0-477.67.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.67.1.el8_8.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.8)
  • kernel-debug-0:4.18.0-477.67.1.el8_8.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.8)
  • kernel-debug-0:4.18.0-477.67.1.el8_8.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.8)
  • +100 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: Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible. Workaround: Mitigation, other than installed the updated packages, 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: No mitigation is currently available for this vulnerability. Make sure to perform the updates as they become available. Workaround: To mitigate this issue, prevent the Conntrack module 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: No current mitigation is available for this vulnerability. Please make sure to have kernel up-to-date as soon as the patches are available to make sure the flaw mitigated. Workaround: Mitigation for this issue is either not available or the currently available options do not 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 do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability. Workaround: To mitigate this issue, prevent the i40e module from being loaded. Please see https://access.redhat.com/solutions/41278 for information on how to prevent it from loading automatically. Workaround: The TIPC module is not automatically loaded in default configurations. When required, administrative privileges are required to explicitly load this module. To determine if the TIPC module is loaded, use the following command: # grep tipc /proc/modules Look for output similar to the following: tipc 479232 0 - Live 0xffffffffc1ba5000 ip6_udp_tunnel 16384 1 tipc, Live 0xffffffffc1b9b000 udp_tunnel 32768 1 tipc, Live 0xffffffffc1b8b000 Loading the module can be prevented with the following instructions: # echo "install tipc /bin/true" >> /etc/modprobe.d/disable-tipc.conf The system will need to be restarted if the module is loaded. In most circumstances, the TIPC kernel module will be unable to be unloaded while any network interfaces are active and the protocol is in use. If the system requires this module to work correctly, this mitigation may not be suitable.

🔗 References (25)