RHSA-2025:4341HighCVSS 8.0

Red Hat Security Advisory: kernel security update

Published
April 30, 2025
Last Modified
August 19, 2026

🔗 CVE IDs covered (5)

CVE-2024-42292 →CVE-2024-42322 →CVE-2024-44990 →CVE-2024-46826 →CVE-2025-21927 →

📋 Description

CVE-2024-42292 — kernel: kobject_uevent: Fix OOB access within zap_modalias_env() CVE-2024-42322 — kernel: ipvs: properly dereference pe in ip_vs_add_service CVE-2024-44990 — kernel: bonding: fix null pointer deref in bond_ipsec_offload_ok CVE-2024-46826 — kernel: ELF: fix kernel.randomize_va_space double read CVE-2025-21927 — kernel: nvme-tcp: fix potential memory corruption in nvme_tcp_recv_pdu()

🎯 Affected products200

  • Red Hat CodeReady Linux Builder (v. 9)
  • Red Hat Enterprise Linux AppStream (v. 9)
  • Red Hat Enterprise Linux BaseOS (v. 9)
  • Red Hat Enterprise Linux Real Time (v. 9)
  • Red Hat Enterprise Linux Real Time for NFV (v. 9)
  • bpftool-0:7.4.0-503.40.1.el9_5.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 9)
  • bpftool-0:7.4.0-503.40.1.el9_5.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 9)
  • bpftool-0:7.4.0-503.40.1.el9_5.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 9)
  • bpftool-0:7.4.0-503.40.1.el9_5.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 9)
  • bpftool-debuginfo-0:7.4.0-503.40.1.el9_5.aarch64 as a component of Red Hat CodeReady Linux Builder (v. 9)
  • bpftool-debuginfo-0:7.4.0-503.40.1.el9_5.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • bpftool-debuginfo-0:7.4.0-503.40.1.el9_5.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 9)
  • bpftool-debuginfo-0:7.4.0-503.40.1.el9_5.ppc64le as a component of Red Hat CodeReady Linux Builder (v. 9)
  • bpftool-debuginfo-0:7.4.0-503.40.1.el9_5.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • bpftool-debuginfo-0:7.4.0-503.40.1.el9_5.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 9)
  • bpftool-debuginfo-0:7.4.0-503.40.1.el9_5.s390x as a component of Red Hat CodeReady Linux Builder (v. 9)
  • bpftool-debuginfo-0:7.4.0-503.40.1.el9_5.s390x as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • bpftool-debuginfo-0:7.4.0-503.40.1.el9_5.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 9)
  • bpftool-debuginfo-0:7.4.0-503.40.1.el9_5.x86_64 as a component of Red Hat CodeReady Linux Builder (v. 9)
  • bpftool-debuginfo-0:7.4.0-503.40.1.el9_5.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • bpftool-debuginfo-0:7.4.0-503.40.1.el9_5.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 9)
  • bpftool-debuginfo-0:7.4.0-503.40.1.el9_5.x86_64 as a component of Red Hat Enterprise Linux Real Time (v. 9)
  • bpftool-debuginfo-0:7.4.0-503.40.1.el9_5.x86_64 as a component of Red Hat Enterprise Linux Real Time for NFV (v. 9)
  • kernel-0:5.14.0-503.40.1.el9_5.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 9)
  • kernel-0:5.14.0-503.40.1.el9_5.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 9)
  • kernel-0:5.14.0-503.40.1.el9_5.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 9)
  • kernel-0:5.14.0-503.40.1.el9_5.src as a component of Red Hat Enterprise Linux BaseOS (v. 9)
  • kernel-0:5.14.0-503.40.1.el9_5.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 9)
  • kernel-64k-0:5.14.0-503.40.1.el9_5.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 9)
  • kernel-64k-core-0:5.14.0-503.40.1.el9_5.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 9)
  • +170 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 `nvme_tcp` 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. Note that this will make NVMe over TCP fabrics unavailable, and as such is not a suitable mitigation for systems relying on that technology.

🔗 References (6)