Red Hat Security Advisory: kernel security, bug fix, and enhancement update
🔗 CVE IDs covered (25)
📋 Description
CVE-2024-57849 — kernel: s390/cpum_sf: Handle CPU hotplug remove during sampling CVE-2025-71066 — kernel: net/sched: ets: Always remove class from active list before deleting in ets_qdisc_change CVE-2026-43051 — kernel: HID: wacom: fix out-of-bounds read in wacom_intuos_bt_irq CVE-2026-43206 — kernel: drm/amdkfd: Fix out-of-bounds write in kfd_event_page_set() CVE-2026-52912 — kernel: netfilter: nf_queue: hold bridge skb->dev while queued CVE-2026-53136 — kernel: drm/amd/display: Clamp VBIOS HDMI retimer register count to array size CVE-2026-53329 — kernel: drm/amd/display: Use krealloc_array() in dal_vector_reserve() CVE-2026-53374 — kernel: drm/amdgpu: zero-initialize GART table on allocation CVE-2026-63829 — kernel: net: ip_gre: require CAP_NET_ADMIN in the device netns for changelink CVE-2026-63884 — kernel: drm/i915: Fix potential UAF in TTM object purge CVE-2026-63992 — kernel: tunnels: do not assume transport header in iptunnel_pmtud_check_icmp() CVE-2026-63994 — kernel: tunnels: load network headers after skb_cow() in iptunnel_pmtud_build_icmpv6 CVE-2026-64007 — kernel: netfilter: synproxy: refresh tcphdr after skb_ensure_writable CVE-2026-64219 — kernel: drm/amd/display: Validate payload length and link_index in dc_process_dmub_aux_transfer_async CVE-2026-68140 — kernel: net/iucv: fix use-after-free of a severed iucv_path CVE-2026-68432 — kernel: vxlan: require CAP_NET_ADMIN in the device netns for changelink CVE-2026-68476 — kernel: ipvs: reload ip header after head reallocation CVE-2026-72052 — kernel: net: ip6_gre: require CAP_NET_ADMIN in the device netns for changelink CVE-2026-72255 — kernel: netfilter: nf_queue: pin bridge device while NFQUEUE holds fake dst CVE-2026-74556 — kernel: scsi: libiscsi_tcp: Bound SCSI Response data segment to the connection buffer CVE-2026-74569 — kernel: netfilter: nf_conntrack_sip: widen NAT rewrite delta to s32 in sip_help_tcp() CVE-2026-74669 — kernel: ipvs: clear IPv4 options after rebasing tunnel ICMP errors CVE-2026-80714 — kernel: ipvs: do not propagate one-packet flag to synced conns CVE-2026-89481 — kernel: nvme-tcp: fix host memory disclosure on R2T for a read command CVE-2026-97417 — kernel: netfilter: nf_conntrack: use get_unaligned_be32() in tcp_sack()
🎯 Affected products74
- Red Hat Enterprise Linux BaseOS E4S (v.8.8)
- Red Hat Enterprise Linux BaseOS TUS (v.8.8)
- bpftool-0:4.18.0-477.179.1.el8_8.ppc64le as a component of Red Hat Enterprise Linux BaseOS E4S (v.8.8)
- bpftool-0:4.18.0-477.179.1.el8_8.x86_64 as a component of Red Hat Enterprise Linux BaseOS E4S (v.8.8)
- bpftool-0:4.18.0-477.179.1.el8_8.x86_64 as a component of Red Hat Enterprise Linux BaseOS TUS (v.8.8)
- bpftool-debuginfo-0:4.18.0-477.179.1.el8_8.ppc64le as a component of Red Hat Enterprise Linux BaseOS E4S (v.8.8)
- bpftool-debuginfo-0:4.18.0-477.179.1.el8_8.x86_64 as a component of Red Hat Enterprise Linux BaseOS E4S (v.8.8)
- bpftool-debuginfo-0:4.18.0-477.179.1.el8_8.x86_64 as a component of Red Hat Enterprise Linux BaseOS TUS (v.8.8)
- kernel-0:4.18.0-477.179.1.el8_8.ppc64le as a component of Red Hat Enterprise Linux BaseOS E4S (v.8.8)
- kernel-0:4.18.0-477.179.1.el8_8.src as a component of Red Hat Enterprise Linux BaseOS E4S (v.8.8)
- kernel-0:4.18.0-477.179.1.el8_8.src as a component of Red Hat Enterprise Linux BaseOS TUS (v.8.8)
- kernel-0:4.18.0-477.179.1.el8_8.x86_64 as a component of Red Hat Enterprise Linux BaseOS E4S (v.8.8)
- kernel-0:4.18.0-477.179.1.el8_8.x86_64 as a component of Red Hat Enterprise Linux BaseOS TUS (v.8.8)
- kernel-abi-stablelists-0:4.18.0-477.179.1.el8_8.noarch as a component of Red Hat Enterprise Linux BaseOS E4S (v.8.8)
- kernel-abi-stablelists-0:4.18.0-477.179.1.el8_8.noarch as a component of Red Hat Enterprise Linux BaseOS TUS (v.8.8)
- kernel-core-0:4.18.0-477.179.1.el8_8.ppc64le as a component of Red Hat Enterprise Linux BaseOS E4S (v.8.8)
- kernel-core-0:4.18.0-477.179.1.el8_8.x86_64 as a component of Red Hat Enterprise Linux BaseOS E4S (v.8.8)
- kernel-core-0:4.18.0-477.179.1.el8_8.x86_64 as a component of Red Hat Enterprise Linux BaseOS TUS (v.8.8)
- kernel-debug-0:4.18.0-477.179.1.el8_8.ppc64le as a component of Red Hat Enterprise Linux BaseOS E4S (v.8.8)
- kernel-debug-0:4.18.0-477.179.1.el8_8.x86_64 as a component of Red Hat Enterprise Linux BaseOS E4S (v.8.8)
- kernel-debug-0:4.18.0-477.179.1.el8_8.x86_64 as a component of Red Hat Enterprise Linux BaseOS TUS (v.8.8)
- kernel-debug-core-0:4.18.0-477.179.1.el8_8.ppc64le as a component of Red Hat Enterprise Linux BaseOS E4S (v.8.8)
- kernel-debug-core-0:4.18.0-477.179.1.el8_8.x86_64 as a component of Red Hat Enterprise Linux BaseOS E4S (v.8.8)
- kernel-debug-core-0:4.18.0-477.179.1.el8_8.x86_64 as a component of Red Hat Enterprise Linux BaseOS TUS (v.8.8)
- kernel-debug-debuginfo-0:4.18.0-477.179.1.el8_8.ppc64le as a component of Red Hat Enterprise Linux BaseOS E4S (v.8.8)
- kernel-debug-debuginfo-0:4.18.0-477.179.1.el8_8.x86_64 as a component of Red Hat Enterprise Linux BaseOS E4S (v.8.8)
- kernel-debug-debuginfo-0:4.18.0-477.179.1.el8_8.x86_64 as a component of Red Hat Enterprise Linux BaseOS TUS (v.8.8)
- kernel-debug-devel-0:4.18.0-477.179.1.el8_8.ppc64le as a component of Red Hat Enterprise Linux BaseOS E4S (v.8.8)
- kernel-debug-devel-0:4.18.0-477.179.1.el8_8.x86_64 as a component of Red Hat Enterprise Linux BaseOS E4S (v.8.8)
- kernel-debug-devel-0:4.18.0-477.179.1.el8_8.x86_64 as a component of Red Hat Enterprise Linux BaseOS TUS (v.8.8)
- +44 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: To mitigate this issue, prevent the `amdkfd` kernel module from loading if it is not required. This can be achieved by blacklisting the module. 1. Create a new file `/etc/modprobe.d/blacklist-amdkfd.conf` with the following content: `blacklist amdkfd` 2. Regenerate the initramfs to ensure the blacklist is applied during boot: `sudo dracut -f -v` (for RHEL 8/9) `sudo mkinitrd -f -v /boot/initramfs-$(uname -r).img $(uname -r)` (for RHEL 7) 3. Reboot the system for the changes to take effect. Note: Blacklisting the `amdkfd` module may impact functionality that relies on the AMD KFD driver, such as certain AMD GPU compute features. Evaluate the necessity of this module before applying the mitigation. 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: 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. The upstream Linux kernel community recommends updating to a stable kernel release containing the fix (6.6.148, 6.12.101, 6.18.42, or 7.1.6 depending on the stable series); for Red Hat products, apply the kernel updates provided for the affected product streams. Workaround: If IPv6 GRE or IP-ERSpan tunnels are not in use, their respective kernel modules (`ip6_gre` and `ip6erspan`) can be blacklisted to prevent exploitation. Create a file such as `/etc/modprobe.d/disable-ip6gre.conf` with the following content: ``` install ip6_gre /bin/true install ip6erspan /bin/true ``` After creating the file, regenerate the initramfs and reboot the system for the changes to take effect. This mitigation may impact network functionality if these tunnel types are actively used. Workaround: If iSCSI initiator functionality is not required, prevent the `libiscsi_tcp` kernel module from loading by blacklisting it. Create a file such as `/etc/modprobe.d/blacklist-iscsi.conf` with the content `blacklist libiscsi_tcp`. A system reboot is required for this change to take effect. This may impact systems relying on iSCSI storage. Workaround: To mitigate this issue, prevent the `ip_vs` kernel module from loading. This can be achieved by creating a blacklist rule. 1. Unload the module if currently loaded: `sudo modprobe -r ip_vs` 2. Create a blacklist configuration file: `echo "blacklist ip_vs" | sudo tee /etc/modprobe.d/disable-ip_vs.conf` 3. Rebuild the initial RAM disk to ensure the module is not loaded at boot: `sudo dracut -f` A system reboot is required for the changes to take full effect. Disabling this module will prevent the use of IP Virtual Server (IPVS) functionality. 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 is not required on the system. 1. Add an entry to /etc/modprobe.d to prevent the module from loading: # echo "install nvme-tcp /bin/true" >> /etc/modprobe.d/disable-nvme-tcp.conf 2. If the module is currently loaded and not in use by any storage target, unload it: # modprobe -r nvme-tcp Caveats: Disabling this module prevents the system from connecting to NVMe over TCP block storage devices. Warning: Do not attempt to unload this module if active NVMe over TCP storage is mounted or in use, as doing so will cause I/O failure and potential data loss. If the module cannot be cleanly unloaded, a system restart is required for the change to take full effect. Additionally, restrict NVMe-oF connections to verified, trusted storage targets over isolated or encrypted network fabrics. Workaround: Systems that do not require stateful firewall, NAT, or connection tracking can eliminate exposure by unloading the nf_conntrack kernel module. On systems where conntrack is required, exposure can be reduced by applying NOTRACK rules in the raw table to bypass connection tracking on untrusted or internet-facing interfaces, ensuring the vulnerable TCP SACK parsing code path in tcp_sack() is not reached for attacker-controlled traffic.
🔗 References (28)
- selfhttps://access.redhat.com/errata/RHSA-2026:100647
- externalhttps://access.redhat.com/security/updates/classification/#important
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2337144
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2429036
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2464462
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2467156
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2492105
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2492768
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2495941
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2502188
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2502230
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2502321
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2502361
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2502431
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2502444
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2506790
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2513293
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2514441
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2516251
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2516306
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2516717
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2517010
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2517052
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2521375
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2525436
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2532184
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2540479
- selfhttps://security.access.redhat.com/data/csaf/v2/advisories/2026/rhsa-2026_100647.json