RHSA-2025:4497HighCVSS 8.0

Red Hat Security Advisory: kpatch-patch-5_14_0-427_13_1, kpatch-patch-5_14_0-427_31_1, kpatch-patch-5_14_0-427_44_1, and kpatch-patch-5_14_0-427_55_1 security update

Published
May 6, 2025
Last Modified
October 21, 2026

🔗 CVE IDs covered (1)

CVE-2025-21927 →

📋 Description

CVE-2025-21927 — kernel: nvme-tcp: fix potential memory corruption in nvme_tcp_recv_pdu()

🎯 Affected products29

  • Red Hat Enterprise Linux BaseOS EUS (v.9.4)
  • kpatch-patch-5_14_0-427_13_1-0:1-8.el9_4.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.4)
  • kpatch-patch-5_14_0-427_13_1-0:1-8.el9_4.src as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.4)
  • kpatch-patch-5_14_0-427_13_1-0:1-8.el9_4.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.4)
  • kpatch-patch-5_14_0-427_13_1-debuginfo-0:1-8.el9_4.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.4)
  • kpatch-patch-5_14_0-427_13_1-debuginfo-0:1-8.el9_4.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.4)
  • kpatch-patch-5_14_0-427_13_1-debugsource-0:1-8.el9_4.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.4)
  • kpatch-patch-5_14_0-427_13_1-debugsource-0:1-8.el9_4.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.4)
  • kpatch-patch-5_14_0-427_31_1-0:1-6.el9_4.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.4)
  • kpatch-patch-5_14_0-427_31_1-0:1-6.el9_4.src as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.4)
  • kpatch-patch-5_14_0-427_31_1-0:1-6.el9_4.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.4)
  • kpatch-patch-5_14_0-427_31_1-debuginfo-0:1-6.el9_4.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.4)
  • kpatch-patch-5_14_0-427_31_1-debuginfo-0:1-6.el9_4.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.4)
  • kpatch-patch-5_14_0-427_31_1-debugsource-0:1-6.el9_4.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.4)
  • kpatch-patch-5_14_0-427_31_1-debugsource-0:1-6.el9_4.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.4)
  • kpatch-patch-5_14_0-427_44_1-0:1-4.el9_4.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.4)
  • kpatch-patch-5_14_0-427_44_1-0:1-4.el9_4.src as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.4)
  • kpatch-patch-5_14_0-427_44_1-0:1-4.el9_4.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.4)
  • kpatch-patch-5_14_0-427_44_1-debuginfo-0:1-4.el9_4.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.4)
  • kpatch-patch-5_14_0-427_44_1-debuginfo-0:1-4.el9_4.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.4)
  • kpatch-patch-5_14_0-427_44_1-debugsource-0:1-4.el9_4.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.4)
  • kpatch-patch-5_14_0-427_44_1-debugsource-0:1-4.el9_4.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.4)
  • kpatch-patch-5_14_0-427_55_1-0:1-2.el9_4.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.4)
  • kpatch-patch-5_14_0-427_55_1-0:1-2.el9_4.src as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.4)
  • kpatch-patch-5_14_0-427_55_1-0:1-2.el9_4.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.4)
  • kpatch-patch-5_14_0-427_55_1-debuginfo-0:1-2.el9_4.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.4)
  • kpatch-patch-5_14_0-427_55_1-debuginfo-0:1-2.el9_4.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.4)
  • kpatch-patch-5_14_0-427_55_1-debugsource-0:1-2.el9_4.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.4)
  • kpatch-patch-5_14_0-427_55_1-debugsource-0:1-2.el9_4.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.4)

✅ 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 (4)