RHSA-2024:0897HighCVSS 7.8

Red Hat Security Advisory: kernel security update

Published
February 20, 2024
Last Modified
August 6, 2026

🔗 CVE IDs covered (19)

CVE-2023-2176 →CVE-2023-45871 →CVE-2022-3545 →CVE-2023-1838 →CVE-2023-6536 →CVE-2023-6606 →CVE-2022-41858 →CVE-2023-2166 →CVE-2023-4623 →CVE-2023-5717 →CVE-2023-6817 →CVE-2023-40283 →CVE-2023-46813 →CVE-2024-0646 →CVE-2023-6610 →CVE-2023-1073 →CVE-2023-4921 →CVE-2023-6356 →CVE-2023-6535 →

📋 Description

CVE-2022-3545 — kernel: nfp: use-after-free in area_cache_get() CVE-2022-41858 — kernel: null-ptr-deref vulnerabilities in sl_tx_timeout in drivers/net/slip CVE-2023-1073 — kernel: HID: check empty report_list in hid_validate_values() CVE-2023-1838 — kernel: Possible use-after-free since the two fdget() during vhost_net_set_backend() 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-4623 — kernel: net/sched: sch_hfsc UAF CVE-2023-4921 — kernel: use-after-free in sch_qfq network scheduler CVE-2023-5717 — kernel: A heap out-of-bounds write when function perf_read_group is called and sibling_list is smaller than its child's sibling_list CVE-2023-6356 — kernel: NULL pointer dereference in nvmet_tcp_build_iovec CVE-2023-6535 — kernel: NULL pointer dereference in nvmet_tcp_execute_request CVE-2023-6536 — kernel: NULL pointer dereference in __nvmet_req_complete 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-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-2023-46813 — kernel: SEV-ES local priv escalation CVE-2024-0646 — kernel: ktls overwrites readonly memory pages when using function splice with a ktls socket as destination

🎯 Affected products122

  • Red Hat CodeReady Linux Builder (v. 8)
  • Red Hat Enterprise Linux BaseOS (v. 8)
  • bpftool-0:4.18.0-513.18.1.el8_9.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)
  • bpftool-0:4.18.0-513.18.1.el8_9.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8)
  • bpftool-0:4.18.0-513.18.1.el8_9.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8)
  • bpftool-0:4.18.0-513.18.1.el8_9.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)
  • bpftool-debuginfo-0:4.18.0-513.18.1.el8_9.aarch64 as a component of Red Hat CodeReady Linux Builder (v. 8)
  • bpftool-debuginfo-0:4.18.0-513.18.1.el8_9.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)
  • bpftool-debuginfo-0:4.18.0-513.18.1.el8_9.ppc64le as a component of Red Hat CodeReady Linux Builder (v. 8)
  • bpftool-debuginfo-0:4.18.0-513.18.1.el8_9.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8)
  • bpftool-debuginfo-0:4.18.0-513.18.1.el8_9.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8)
  • bpftool-debuginfo-0:4.18.0-513.18.1.el8_9.x86_64 as a component of Red Hat CodeReady Linux Builder (v. 8)
  • bpftool-debuginfo-0:4.18.0-513.18.1.el8_9.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)
  • kernel-0:4.18.0-513.18.1.el8_9.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)
  • kernel-0:4.18.0-513.18.1.el8_9.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8)
  • kernel-0:4.18.0-513.18.1.el8_9.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8)
  • kernel-0:4.18.0-513.18.1.el8_9.src as a component of Red Hat Enterprise Linux BaseOS (v. 8)
  • kernel-0:4.18.0-513.18.1.el8_9.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)
  • kernel-abi-stablelists-0:4.18.0-513.18.1.el8_9.noarch as a component of Red Hat Enterprise Linux BaseOS (v. 8)
  • kernel-core-0:4.18.0-513.18.1.el8_9.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)
  • kernel-core-0:4.18.0-513.18.1.el8_9.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8)
  • kernel-core-0:4.18.0-513.18.1.el8_9.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8)
  • kernel-core-0:4.18.0-513.18.1.el8_9.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)
  • kernel-debug-0:4.18.0-513.18.1.el8_9.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)
  • kernel-debug-0:4.18.0-513.18.1.el8_9.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8)
  • kernel-debug-0:4.18.0-513.18.1.el8_9.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8)
  • kernel-debug-0:4.18.0-513.18.1.el8_9.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)
  • kernel-debug-core-0:4.18.0-513.18.1.el8_9.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)
  • kernel-debug-core-0:4.18.0-513.18.1.el8_9.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8)
  • kernel-debug-core-0:4.18.0-513.18.1.el8_9.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 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: 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 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 flaw can be mitigated by preventing the affected Host kernel accelerator (vhost-net) 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: 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: 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 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: 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: To mitigate this issue, prevent module nvmet-tcp 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 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: 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 (22)