Red Hat Security Advisory: kpatch-patch-5_14_0-284_134_1, kpatch-patch-5_14_0-284_148_1, kpatch-patch-5_14_0-284_158_1, kpatch-patch-5_14_0-284_172_1, and kpatch-patch-5_14_0-284_188_1 security update
🔗 CVE IDs covered (3)
📋 Description
CVE-2026-64534 — kernel: nvmet-tcp: check INIT_FAILED before nvmet_req_uninit in digest error path CVE-2026-98432 — kernel: ipv4: free inet_opt and ireq_opt after an RCU grace period CVE-2026-99999 — kernel: ipv4: validate checksum_start before completing checksum
🎯 Affected products36
- Red Hat Enterprise Linux BaseOS E4S (v.9.2)
- kpatch-patch-5_14_0-284_134_1-0:1-20.el9_2.ppc64le as a component of Red Hat Enterprise Linux BaseOS E4S (v.9.2)
- kpatch-patch-5_14_0-284_134_1-0:1-20.el9_2.src as a component of Red Hat Enterprise Linux BaseOS E4S (v.9.2)
- kpatch-patch-5_14_0-284_134_1-0:1-20.el9_2.x86_64 as a component of Red Hat Enterprise Linux BaseOS E4S (v.9.2)
- kpatch-patch-5_14_0-284_134_1-debuginfo-0:1-20.el9_2.ppc64le as a component of Red Hat Enterprise Linux BaseOS E4S (v.9.2)
- kpatch-patch-5_14_0-284_134_1-debuginfo-0:1-20.el9_2.x86_64 as a component of Red Hat Enterprise Linux BaseOS E4S (v.9.2)
- kpatch-patch-5_14_0-284_134_1-debugsource-0:1-20.el9_2.ppc64le as a component of Red Hat Enterprise Linux BaseOS E4S (v.9.2)
- kpatch-patch-5_14_0-284_134_1-debugsource-0:1-20.el9_2.x86_64 as a component of Red Hat Enterprise Linux BaseOS E4S (v.9.2)
- kpatch-patch-5_14_0-284_148_1-0:1-18.el9_2.ppc64le as a component of Red Hat Enterprise Linux BaseOS E4S (v.9.2)
- kpatch-patch-5_14_0-284_148_1-0:1-18.el9_2.src as a component of Red Hat Enterprise Linux BaseOS E4S (v.9.2)
- kpatch-patch-5_14_0-284_148_1-0:1-18.el9_2.x86_64 as a component of Red Hat Enterprise Linux BaseOS E4S (v.9.2)
- kpatch-patch-5_14_0-284_148_1-debuginfo-0:1-18.el9_2.ppc64le as a component of Red Hat Enterprise Linux BaseOS E4S (v.9.2)
- kpatch-patch-5_14_0-284_148_1-debuginfo-0:1-18.el9_2.x86_64 as a component of Red Hat Enterprise Linux BaseOS E4S (v.9.2)
- kpatch-patch-5_14_0-284_148_1-debugsource-0:1-18.el9_2.ppc64le as a component of Red Hat Enterprise Linux BaseOS E4S (v.9.2)
- kpatch-patch-5_14_0-284_148_1-debugsource-0:1-18.el9_2.x86_64 as a component of Red Hat Enterprise Linux BaseOS E4S (v.9.2)
- kpatch-patch-5_14_0-284_158_1-0:1-16.el9_2.ppc64le as a component of Red Hat Enterprise Linux BaseOS E4S (v.9.2)
- kpatch-patch-5_14_0-284_158_1-0:1-16.el9_2.src as a component of Red Hat Enterprise Linux BaseOS E4S (v.9.2)
- kpatch-patch-5_14_0-284_158_1-0:1-16.el9_2.x86_64 as a component of Red Hat Enterprise Linux BaseOS E4S (v.9.2)
- kpatch-patch-5_14_0-284_158_1-debuginfo-0:1-16.el9_2.ppc64le as a component of Red Hat Enterprise Linux BaseOS E4S (v.9.2)
- kpatch-patch-5_14_0-284_158_1-debuginfo-0:1-16.el9_2.x86_64 as a component of Red Hat Enterprise Linux BaseOS E4S (v.9.2)
- kpatch-patch-5_14_0-284_158_1-debugsource-0:1-16.el9_2.ppc64le as a component of Red Hat Enterprise Linux BaseOS E4S (v.9.2)
- kpatch-patch-5_14_0-284_158_1-debugsource-0:1-16.el9_2.x86_64 as a component of Red Hat Enterprise Linux BaseOS E4S (v.9.2)
- kpatch-patch-5_14_0-284_172_1-0:1-13.el9_2.ppc64le as a component of Red Hat Enterprise Linux BaseOS E4S (v.9.2)
- kpatch-patch-5_14_0-284_172_1-0:1-13.el9_2.src as a component of Red Hat Enterprise Linux BaseOS E4S (v.9.2)
- kpatch-patch-5_14_0-284_172_1-0:1-13.el9_2.x86_64 as a component of Red Hat Enterprise Linux BaseOS E4S (v.9.2)
- kpatch-patch-5_14_0-284_172_1-debuginfo-0:1-13.el9_2.ppc64le as a component of Red Hat Enterprise Linux BaseOS E4S (v.9.2)
- kpatch-patch-5_14_0-284_172_1-debuginfo-0:1-13.el9_2.x86_64 as a component of Red Hat Enterprise Linux BaseOS E4S (v.9.2)
- kpatch-patch-5_14_0-284_172_1-debugsource-0:1-13.el9_2.ppc64le as a component of Red Hat Enterprise Linux BaseOS E4S (v.9.2)
- kpatch-patch-5_14_0-284_172_1-debugsource-0:1-13.el9_2.x86_64 as a component of Red Hat Enterprise Linux BaseOS E4S (v.9.2)
- kpatch-patch-5_14_0-284_188_1-0:1-5.el9_2.ppc64le as a component of Red Hat Enterprise Linux BaseOS E4S (v.9.2)
- +6 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 Workaround: If NVMe over TCP target functionality is not required, the vulnerable code path can be avoided by not loading or by blacklisting the nvmet-tcp kernel module. For systems where NVMe/TCP targets are needed, restrict access to trusted initiators via host NQN allowlists and network segmentation to reduce the attack surface. Workaround: See the security bulletin for a detailed mitigation procedure. Workaround: Check the virtio-net device name with monitor command "info network": ~~~ (qemu) info network net0: index=0,type=nic,model=virtio-net-pci,macaddr=52:54:00:12:34:57 \ vhost0: index=0,type=tap,ifname=tap-vm0,script=no,downscript=no ~~~ Remove the device and re-add it with csum=off: ~~~ (qemu) device_del net0 (qemu) device_add virtio-net-pci,netdev=vhost0,id=net0,mac=52:54:00:12:34:57,csum=off ~~~
🔗 References (6)
- selfhttps://access.redhat.com/errata/RHSA-2026:100521
- externalhttps://access.redhat.com/security/updates/classification/#critical
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2507399
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2553390
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2553429
- selfhttps://security.access.redhat.com/data/csaf/v2/advisories/2026/rhsa-2026_100521.json