RHSA-2026:16208HighCVSS 7.8
Red Hat Security Advisory: kpatch-patch-5_14_0-284_104_1, kpatch-patch-5_14_0-284_117_1, kpatch-patch-5_14_0-284_134_1, kpatch-patch-5_14_0-284_148_1, and kpatch-patch-5_14_0-284_158_1 security update
🔗 CVE IDs covered (1)
📋 Description
CVE-2026-31431 — kernel: crypto: algif_aead - Revert to operating out-of-place
🎯 Affected products36
- Red Hat Enterprise Linux BaseOS E4S (v.9.2)
- kpatch-patch-5_14_0-284_104_1-0:1-14.el9_2.ppc64le as a component of Red Hat Enterprise Linux BaseOS E4S (v.9.2)
- kpatch-patch-5_14_0-284_104_1-0:1-14.el9_2.src as a component of Red Hat Enterprise Linux BaseOS E4S (v.9.2)
- kpatch-patch-5_14_0-284_104_1-0:1-14.el9_2.x86_64 as a component of Red Hat Enterprise Linux BaseOS E4S (v.9.2)
- kpatch-patch-5_14_0-284_104_1-debuginfo-0:1-14.el9_2.ppc64le as a component of Red Hat Enterprise Linux BaseOS E4S (v.9.2)
- kpatch-patch-5_14_0-284_104_1-debuginfo-0:1-14.el9_2.x86_64 as a component of Red Hat Enterprise Linux BaseOS E4S (v.9.2)
- kpatch-patch-5_14_0-284_104_1-debugsource-0:1-14.el9_2.ppc64le as a component of Red Hat Enterprise Linux BaseOS E4S (v.9.2)
- kpatch-patch-5_14_0-284_104_1-debugsource-0:1-14.el9_2.x86_64 as a component of Red Hat Enterprise Linux BaseOS E4S (v.9.2)
- kpatch-patch-5_14_0-284_117_1-0:1-11.el9_2.ppc64le as a component of Red Hat Enterprise Linux BaseOS E4S (v.9.2)
- kpatch-patch-5_14_0-284_117_1-0:1-11.el9_2.src as a component of Red Hat Enterprise Linux BaseOS E4S (v.9.2)
- kpatch-patch-5_14_0-284_117_1-0:1-11.el9_2.x86_64 as a component of Red Hat Enterprise Linux BaseOS E4S (v.9.2)
- kpatch-patch-5_14_0-284_117_1-debuginfo-0:1-11.el9_2.ppc64le as a component of Red Hat Enterprise Linux BaseOS E4S (v.9.2)
- kpatch-patch-5_14_0-284_117_1-debuginfo-0:1-11.el9_2.x86_64 as a component of Red Hat Enterprise Linux BaseOS E4S (v.9.2)
- kpatch-patch-5_14_0-284_117_1-debugsource-0:1-11.el9_2.ppc64le as a component of Red Hat Enterprise Linux BaseOS E4S (v.9.2)
- kpatch-patch-5_14_0-284_117_1-debugsource-0:1-11.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-0:1-5.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-5.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-5.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-5.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-5.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-5.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-5.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-3.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-3.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-3.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-3.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-3.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-3.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-3.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-1.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 The system must be rebooted for this update to take effect. Workaround: See the security bulletin for a detailed mitigation procedure.