Red Hat Security Advisory: kernel security, bug fix, and enhancement update
🔗 CVE IDs covered (39)
📋 Description
CVE-2025-22063 — kernel: netlabel: Fix NULL pointer exception caused by CALIPSO on IPv4 sockets CVE-2025-38004 — kernel: can: bcm: add locking for bcm_op runtime updates CVE-2025-38147 — kernel: calipso: Don't call calipso functions for AF_INET sk. CVE-2026-43332 — kernel: thermal: core: Fix thermal zone device registration error path CVE-2026-53365 — kernel: vsock/virtio: fix zerocopy completion for multi-skb sends CVE-2026-63899 — kernel: USB: serial: mxuport: fix memory corruption with small endpoint CVE-2026-63962 — kernel: usb: typec: tcpm: bound altmode_desc[] per iteration in svdm_consume_modes() CVE-2026-63970 — kernel: vsock/virtio: bind uarg before filling zerocopy skb CVE-2026-64018 — kernel: net: mana: validate rx_req_idx to prevent out-of-bounds array access CVE-2026-64034 — kernel: net: mana: Fix TOCTOU double-fetch of hwc_msg_id from DMA buffer CVE-2026-64035 — kernel: igc: set tx buffer type for SMD frames CVE-2026-64162 — kernel: idpf: fix read_dev_clk_lock spinlock init in idpf_ptp_init() CVE-2026-64266 — kernel: fuse: re-lock request before returning from fuse_ref_folio() CVE-2026-64268 — kernel: Kernel: Remote out-of-bounds write in RDMA/siw CVE-2026-64378 — kernel: writeback: fix race between cgroup_writeback_umount() and inode_switch_wbs() CVE-2026-64481 — kernel: ALSA: hda/cs35l41: Fix firmware load work teardown CVE-2026-68202 — kernel: ALSA: seq: close a re-opened queue timer in the destructor CVE-2026-68236 — kernel: drm/amd/display: set new_stream to NULL after release CVE-2026-68245 — kernel: drm/amdgpu: fix lifetime issue of amdgpu_vm_get_task_info_pasid() CVE-2026-68278 — kernel: drm/dp/mst: fix buffer overflows in sideband chunk accumulation CVE-2026-68293 — kernel: net/mlx5: Fix MCIA register buffer overflow on 32 dword reads CVE-2026-68299 — kernel: vmxnet3: fix BUG_ON in vmxnet3_get_hdr_len() for Geneve packets CVE-2026-72083 — kernel: scsi: target: core: Fix iSCSI ISID use-after-free in REGISTER AND MOVE CVE-2026-72289 — kernel: KVM: arm64: vgic: Check the interrupt is still ours before migrating it CVE-2026-72319 — kernel: ipvs: ensure inner headers in ICMP errors are in headroom CVE-2026-74705 — kernel: udp: fix potential use-after-free in tunnel segmentation CVE-2026-80536 — kernel: xfs: bounds-check buffer log item's dirty bitmap CVE-2026-80887 — kernel: drm/vmwgfx: use check_add_overflow for shader size+offset bound CVE-2026-80985 — kernel: net/smc: carry oversized SMC-Rv2 LLC messages in the queue entry CVE-2026-89631 — kernel: smb: client: reject a tree connect response whose byte count is too small CVE-2026-89777 — kernel: vfio/pci: clear vdev->msi_perm after freeing it on init failure CVE-2026-89811 — kernel: drm/amdkfd: Add TLB flush after MES queue eviction/suspension CVE-2026-90011 — kernel: scsi: target: iscsi: Reserve a terminator byte for the login payload CVE-2026-93817 — kernel: perf: Fix addr_filter_ranges lifetime CVE-2026-93827 — kernel: virtio-fs: avoid double-free on failed queue setup CVE-2026-98260 — kernel: exec: Cleanup POSIX timers right after de_thread() CVE-2026-98320 — kernel: netfilter: flowtable: hold reference on ct until flow is released CVE-2026-98466 — kernel: KVM: arm64: Transfer the hyp stack pages out of the host stage-2 CVE-2026-98725 — kernel: nvmet-auth: fix out-of-bounds write in nvmet_auth_challenge()
🎯 Affected products200
- Red Hat Enterprise Linux AppStream (v. 9)
- Red Hat Enterprise Linux BaseOS (v. 9)
- Red Hat Enterprise Linux CodeReady Linux Builder (v. 9)
- Red Hat Enterprise Linux Real Time (v. 9)
- Red Hat Enterprise Linux Real Time for NFV (v. 9)
- kernel-0:5.14.0-741.20.1.el9_9.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 9)
- kernel-0:5.14.0-741.20.1.el9_9.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 9)
- kernel-0:5.14.0-741.20.1.el9_9.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 9)
- kernel-0:5.14.0-741.20.1.el9_9.src as a component of Red Hat Enterprise Linux BaseOS (v. 9)
- kernel-0:5.14.0-741.20.1.el9_9.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 9)
- kernel-64k-0:5.14.0-741.20.1.el9_9.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 9)
- kernel-64k-core-0:5.14.0-741.20.1.el9_9.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 9)
- kernel-64k-debug-0:5.14.0-741.20.1.el9_9.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 9)
- kernel-64k-debug-core-0:5.14.0-741.20.1.el9_9.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 9)
- kernel-64k-debug-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9)
- kernel-64k-debug-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 9)
- kernel-64k-debug-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 as a component of Red Hat Enterprise Linux CodeReady Linux Builder (v. 9)
- kernel-64k-debug-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 as a component of Red Hat Enterprise Linux Real Time (v. 9)
- kernel-64k-debug-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 as a component of Red Hat Enterprise Linux Real Time for NFV (v. 9)
- kernel-64k-debug-devel-0:5.14.0-741.20.1.el9_9.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9)
- kernel-64k-debug-devel-matched-0:5.14.0-741.20.1.el9_9.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9)
- kernel-64k-debug-modules-0:5.14.0-741.20.1.el9_9.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 9)
- kernel-64k-debug-modules-core-0:5.14.0-741.20.1.el9_9.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 9)
- kernel-64k-debug-modules-extra-0:5.14.0-741.20.1.el9_9.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 9)
- kernel-64k-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9)
- kernel-64k-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 9)
- kernel-64k-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 as a component of Red Hat Enterprise Linux CodeReady Linux Builder (v. 9)
- kernel-64k-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 as a component of Red Hat Enterprise Linux Real Time (v. 9)
- kernel-64k-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 as a component of Red Hat Enterprise Linux Real Time for NFV (v. 9)
- kernel-64k-devel-0:5.14.0-741.20.1.el9_9.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9)
- +170 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: The vulnerable code path is only reachable when using virtio-vsock with zerocopy transmit on virtual machines using the vhost-vsock or virtio-vsock transport. Systems that do not use VM socket communication (AF_VSOCK) are not affected. To prevent the vulnerable code path from being reached, the vhost_vsock kernel module can be unloaded and blacklisted if vsock functionality is not required: ``` modprobe -r vhost_vsock echo "blacklist vhost_vsock" > /etc/modprobe.d/vsock-blacklist.conf ``` Systems that rely on VM-to-host socket communication (e.g., QEMU guest agent communication) cannot use this mitigation and should prioritize applying the kernel fix. Workaround: To mitigate this issue, prevent the 'mana' kernel module from loading if it is not required for your system's operation, especially in Confidential VM environments. 1. Create a file named `/etc/modprobe.d/disable-mana.conf` with the following content: `blacklist mana` 2. Rebuild the initramfs: `dracut -f -v` 3. Reboot the system for the changes to take effect. Warning: This action may impact network functionality if the 'mana' driver is essential for the system's network operations. A system reboot is required for the changes to be applied. Workaround: Prevent the MANA driver module from loading if Microsoft Azure Network Adapter hardware is not required. Create the file `/etc/modprobe.d/mana.conf` with the following entry: ``` install mana /bin/true ``` If the `mana` module is currently loaded, the system must be rebooted for this configuration to take effect. Warning: Disabling this driver will incapacitate network interfaces that depend on Microsoft Azure Network Adapter hardware, which may result in a total loss of network connectivity if it is the primary interface. System reboots will interrupt running services and network connections. Workaround: Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability. Workaround: If the Intel Ethernet PTP functionality is not required, the `idpf` kernel module can be blacklisted to prevent it from loading. This can be achieved by creating a modprobe configuration file. 1. Create a file named `/etc/modprobe.d/blacklist-idpf.conf` with the following content: ``` blacklist idpf install idpf /bin/true ``` 2. Regenerate the initramfs to ensure the blacklist is applied during boot: - For systems using Dracut: `dracut -f -v` - For systems using mkinitcpio: `mkinitcpio -P` 3. Reboot the system for the changes to take effect. This mitigation may impact systems that rely on Intel Ethernet PTP for time synchronization. Workaround: To mitigate this issue, prevent the `siw` kernel module from loading. Create a file `/etc/modprobe.d/blacklist-siw.conf` with the following content: ``` blacklist siw install siw /bin/true ``` After creating the file, regenerate the initramfs and reboot the system for the changes to take effect: ```bash dracut -f -v reboot ``` This mitigation will disable the Soft iWARP functionality, which may impact applications relying on it. A system reboot is required for the changes to be fully applied. Workaround: To mitigate this issue, prevent module snd_seq from being loaded. Please see https://access.redhat.com/solutions/41278 for how to blacklist a kernel module to prevent it from loading automatically. Workaround: To mitigate this issue on systems that do not require AMD graphics hardware, prevent the amdgpu module from loading: 1. Create a configuration file in /etc/modprobe.d to disable the driver: # echo "install amdgpu /bin/true" > /etc/modprobe.d/disable-amdgpu.conf 2. If the amdgpu module is already loaded in the running kernel, a system reboot is required for the configuration to take effect. Warning: Disabling this module prevents the initialization of AMD graphics adapters, which disables graphical desktop environments, display output, and GPU acceleration on systems relying on AMD hardware. Workaround: Prevent the 'drm_dp_mst' kernel module from loading to mitigate this vulnerability. This will disable DisplayPort Multi-Stream Transport functionality, which may affect multi-monitor setups using DisplayPort. To blacklist the module, create a file named `/etc/modprobe.d/blacklist-drm_dp_mst.conf` with the following content: ``` blacklist drm_dp_mst ``` Then, regenerate the initramfs and reboot the system for the changes to take effect: ```bash drancut --force --kver $(uname -r) reboot ``` A system reboot is required for the module to be unloaded and the mitigation to be active. This may impact display functionality if DP MST is in use. Workaround: To mitigate this flaw on hosts that do not operate as storage target servers, prevent the LIO target kernel modules from loading: 1. Create a configuration file to prevent loading the target modules: # echo "install iscsi_target_mod /bin/true" > /etc/modprobe.d/disable-iscsi_target.conf # echo "install target_core_mod /bin/true" > /etc/modprobe.d/disable-target_core.conf 2. Stop the SCSI target daemon if active: # systemctl stop target.service Warning: Modifying kernel module loading or stopping target.service requires a service restart or system reboot, and will immediately interrupt active storage connections on systems acting as storage targets. If the machine must function as an iSCSI target, use network firewall rules to restrict access to the iSCSI target port (TCP port 3260) strictly to authorized initiator hosts. Workaround: To mitigate this vulnerability, prevent the IP Virtual Server kernel module from loading if IPVS load balancing services are not required: 1. Create a configuration file to disable module loading: # echo "install ip_vs /bin/true" > /etc/modprobe.d/ip_vs.conf 2. If the module is already loaded, remove it: # modprobe -r ip_vs Caveats: Disabling this module will disrupt systems actively utilizing IPVS for network load balancing, clustering (such as Keepalived), or container ingress proxies. If the module is currently in use and cannot be unloaded with modprobe, a system restart will be required for the configuration to take effect. Workaround: To mitigate this issue, prevent module xfs from being loaded. Please see https://access.redhat.com/solutions/41278 for how to blacklist a kernel module to prevent it from loading automatically. Workaround: To mitigate this vulnerability, prevent the vmwgfx kernel module from loading if VMware virtual graphics acceleration is not needed: 1. Create a configuration file to prevent the module from being loaded: # echo "install vmwgfx /bin/true" > /etc/modprobe.d/disable-vmwgfx.conf 2. If the module is currently loaded, reboot the system for the change to take effect: # re…
🔗 References (60)
- selfhttps://access.redhat.com/errata/RHSA-2026:97873
- externalhttps://access.redhat.com/security/updates/classification/#important
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2360273
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2370992
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2376106
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2468043
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2492108
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2492741
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2492851
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2499742
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2502325
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2502332
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2502356
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2502394
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2502411
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2502421
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2502476
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2502521
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2502593
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2507038
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2507089
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2507098
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2507222
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2507296
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2513148
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2513150
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2513245
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2513277
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2513287
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2513356
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2513430
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2516579
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2516657
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2516935
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2516967
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2516970
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2517006
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2521498
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2524492
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2524501
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2528788
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2532089
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2532279
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2532407
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2532493
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2535066
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2535227
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2535309
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2536264
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2540391
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2540396
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2540872
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2546487
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2546491
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2546494
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2553390
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2554835
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2555068
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2559811
- selfhttps://security.access.redhat.com/data/csaf/v2/advisories/2026/rhsa-2026_97873.json