Red Hat Security Advisory: kernel-rt security update
🔗 CVE IDs covered (5)
📋 Description
CVE-2026-31566 — kernel: drm/amdgpu: Fix fence put before wait in amdgpu_amdkfd_submit_ib CVE-2026-52912 — kernel: netfilter: nf_queue: hold bridge skb->dev while queued CVE-2026-68121 — kernel: pppoe: reload header pointer after dev_hard_header() CVE-2026-80714 — kernel: ipvs: do not propagate one-packet flag to synced conns CVE-2026-89480 — kernel: nvme-tcp: reject a read that transferred too few bytes
🎯 Affected products32
- Red Hat Enterprise Linux NFV (v. 8)
- Red Hat Enterprise Linux RT (v. 8)
- kernel-rt-0:4.18.0-553.168.1.rt7.509.el8_10.src as a component of Red Hat Enterprise Linux NFV (v. 8)
- kernel-rt-0:4.18.0-553.168.1.rt7.509.el8_10.src as a component of Red Hat Enterprise Linux RT (v. 8)
- kernel-rt-0:4.18.0-553.168.1.rt7.509.el8_10.x86_64 as a component of Red Hat Enterprise Linux NFV (v. 8)
- kernel-rt-0:4.18.0-553.168.1.rt7.509.el8_10.x86_64 as a component of Red Hat Enterprise Linux RT (v. 8)
- kernel-rt-core-0:4.18.0-553.168.1.rt7.509.el8_10.x86_64 as a component of Red Hat Enterprise Linux NFV (v. 8)
- kernel-rt-core-0:4.18.0-553.168.1.rt7.509.el8_10.x86_64 as a component of Red Hat Enterprise Linux RT (v. 8)
- kernel-rt-debug-0:4.18.0-553.168.1.rt7.509.el8_10.x86_64 as a component of Red Hat Enterprise Linux NFV (v. 8)
- kernel-rt-debug-0:4.18.0-553.168.1.rt7.509.el8_10.x86_64 as a component of Red Hat Enterprise Linux RT (v. 8)
- kernel-rt-debug-core-0:4.18.0-553.168.1.rt7.509.el8_10.x86_64 as a component of Red Hat Enterprise Linux NFV (v. 8)
- kernel-rt-debug-core-0:4.18.0-553.168.1.rt7.509.el8_10.x86_64 as a component of Red Hat Enterprise Linux RT (v. 8)
- kernel-rt-debug-debuginfo-0:4.18.0-553.168.1.rt7.509.el8_10.x86_64 as a component of Red Hat Enterprise Linux NFV (v. 8)
- kernel-rt-debug-debuginfo-0:4.18.0-553.168.1.rt7.509.el8_10.x86_64 as a component of Red Hat Enterprise Linux RT (v. 8)
- kernel-rt-debug-devel-0:4.18.0-553.168.1.rt7.509.el8_10.x86_64 as a component of Red Hat Enterprise Linux NFV (v. 8)
- kernel-rt-debug-devel-0:4.18.0-553.168.1.rt7.509.el8_10.x86_64 as a component of Red Hat Enterprise Linux RT (v. 8)
- kernel-rt-debug-kvm-0:4.18.0-553.168.1.rt7.509.el8_10.x86_64 as a component of Red Hat Enterprise Linux NFV (v. 8)
- kernel-rt-debug-modules-0:4.18.0-553.168.1.rt7.509.el8_10.x86_64 as a component of Red Hat Enterprise Linux NFV (v. 8)
- kernel-rt-debug-modules-0:4.18.0-553.168.1.rt7.509.el8_10.x86_64 as a component of Red Hat Enterprise Linux RT (v. 8)
- kernel-rt-debug-modules-extra-0:4.18.0-553.168.1.rt7.509.el8_10.x86_64 as a component of Red Hat Enterprise Linux NFV (v. 8)
- kernel-rt-debug-modules-extra-0:4.18.0-553.168.1.rt7.509.el8_10.x86_64 as a component of Red Hat Enterprise Linux RT (v. 8)
- kernel-rt-debuginfo-0:4.18.0-553.168.1.rt7.509.el8_10.x86_64 as a component of Red Hat Enterprise Linux NFV (v. 8)
- kernel-rt-debuginfo-0:4.18.0-553.168.1.rt7.509.el8_10.x86_64 as a component of Red Hat Enterprise Linux RT (v. 8)
- kernel-rt-debuginfo-common-x86_64-0:4.18.0-553.168.1.rt7.509.el8_10.x86_64 as a component of Red Hat Enterprise Linux NFV (v. 8)
- kernel-rt-debuginfo-common-x86_64-0:4.18.0-553.168.1.rt7.509.el8_10.x86_64 as a component of Red Hat Enterprise Linux RT (v. 8)
- kernel-rt-devel-0:4.18.0-553.168.1.rt7.509.el8_10.x86_64 as a component of Red Hat Enterprise Linux NFV (v. 8)
- kernel-rt-devel-0:4.18.0-553.168.1.rt7.509.el8_10.x86_64 as a component of Red Hat Enterprise Linux RT (v. 8)
- kernel-rt-kvm-0:4.18.0-553.168.1.rt7.509.el8_10.x86_64 as a component of Red Hat Enterprise Linux NFV (v. 8)
- kernel-rt-modules-0:4.18.0-553.168.1.rt7.509.el8_10.x86_64 as a component of Red Hat Enterprise Linux NFV (v. 8)
- kernel-rt-modules-0:4.18.0-553.168.1.rt7.509.el8_10.x86_64 as a component of Red Hat Enterprise Linux RT (v. 8)
- +2 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. Red Hat recommends treating all kernel errata as security-relevant. Given the kernel's fundamental role, any bug has a higher chance of impacting system security, even if that impact only becomes clear after a fix is published. Therefore, Red Hat prioritizes delivering fixes that improve our customers' overall security posture. Because of this proactive approach, a patch may be associated with a CVE assignment at a future date. Retroactive CVE assignments are always documented in the corresponding errata and on Red Hat's CVE pages. We strongly advise against delaying updates, as doing so may leave your system exposed when protections are already available. Workaround: Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability. Workaround: See the security bulletin for a detailed mitigation procedure. Workaround: To mitigate this issue, prevent the `ip_vs` kernel module from loading. This can be achieved by creating a blacklist rule. Note that this may impact systems utilizing IPVS for load balancing. 1. Create a configuration file to blacklist the module: `echo "blacklist ip_vs" > /etc/modprobe.d/disable-ip_vs.conf` 2. Regenerate the initramfs to ensure the blacklist is applied at boot: `dracut -f -v` 3. Reboot the system for the changes to take effect: `reboot` Alternatively, if the module is currently loaded, it can be unloaded (if no dependencies exist): `rmmod ip_vs` However, a system reboot is recommended to ensure the module is not loaded on subsequent boots. Workaround: Prevent the nvme-tcp kernel module from loading if NVMe-over-TCP storage connectivity is not required on the host: 1. Create a configuration file to blacklist the driver and prevent it from loading: # echo "install nvme-tcp /bin/true" > /etc/modprobe.d/nvme-tcp.conf # echo "blacklist nvme-tcp" >> /etc/modprobe.d/nvme-tcp.conf 2. If the module is currently loaded, unload it: # modprobe -r nvme-tcp Caveats: Applying this operational workaround disables all NVMe-over-TCP initiator functionality and prevents connections to NVMe-oF network storage fabrics. If the module is actively in use by mounted file systems or active block devices, it cannot be safely unloaded at runtime without first unmounting those targets, and a system reboot may be required to cleanly unload the driver.
🔗 References (7)
- selfhttps://access.redhat.com/errata/RHSA-2026:71330
- externalhttps://access.redhat.com/security/updates/classification/#important
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2461451
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2492105
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2513233
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2532095
- selfhttps://security.access.redhat.com/data/csaf/v2/advisories/2026/rhsa-2026_71330.json