RHSA-2026:19521HighCVSS 8.1

Red Hat Security Advisory: kernel security update

Published
May 20, 2026
Last Modified
October 30, 2026

🔗 CVE IDs covered (9)

CVE-2026-23243 →CVE-2026-23401 →CVE-2026-31532 →CVE-2026-46333 →CVE-2025-38024 →CVE-2026-23191 →CVE-2026-31419 →CVE-2026-43503 →CVE-2026-46300 →

📋 Description

CVE-2025-38024 — kernel: Linux kernel: RDMA/rxe use-after-free vulnerability leading to potential arbitrary code execution CVE-2026-23191 — kernel: ALSA: aloop: Fix racy access at PCM trigger CVE-2026-23243 — kernel: Linux kernel: Denial of service and memory corruption in RDMA umad CVE-2026-23401 — kernel: Linux kernel KVM: Privilege escalation or denial of service due to improper shadow page table entry handling CVE-2026-31419 — kernel: Linux kernel: Use-after-free in bonding driver leads to denial of service CVE-2026-31532 — kernel: can: raw: fix ro->uniq use-after-free in raw_rcv() CVE-2026-43503 — kernel: net: skbuff: propagate shared-frag marker through frag-transfer helpers CVE-2026-46300 — kernel: "Fragnesia" is a variant of Dirty Frag vulnerability in the ESP/XFRM leading to Local Privilege Escalation (LPE) vulnerability in the Linux kernel CVE-2026-46333 — kernel: Read root-owned files as an unprivileged user

🎯 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.143.1.el8_8.ppc64le as a component of Red Hat Enterprise Linux BaseOS E4S (v.8.8)
  • bpftool-0:4.18.0-477.143.1.el8_8.x86_64 as a component of Red Hat Enterprise Linux BaseOS E4S (v.8.8)
  • bpftool-0:4.18.0-477.143.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.143.1.el8_8.ppc64le as a component of Red Hat Enterprise Linux BaseOS E4S (v.8.8)
  • bpftool-debuginfo-0:4.18.0-477.143.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.143.1.el8_8.x86_64 as a component of Red Hat Enterprise Linux BaseOS TUS (v.8.8)
  • kernel-0:4.18.0-477.143.1.el8_8.ppc64le as a component of Red Hat Enterprise Linux BaseOS E4S (v.8.8)
  • kernel-0:4.18.0-477.143.1.el8_8.src as a component of Red Hat Enterprise Linux BaseOS E4S (v.8.8)
  • kernel-0:4.18.0-477.143.1.el8_8.src as a component of Red Hat Enterprise Linux BaseOS TUS (v.8.8)
  • kernel-0:4.18.0-477.143.1.el8_8.x86_64 as a component of Red Hat Enterprise Linux BaseOS E4S (v.8.8)
  • kernel-0:4.18.0-477.143.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.143.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.143.1.el8_8.noarch as a component of Red Hat Enterprise Linux BaseOS TUS (v.8.8)
  • kernel-core-0:4.18.0-477.143.1.el8_8.ppc64le as a component of Red Hat Enterprise Linux BaseOS E4S (v.8.8)
  • kernel-core-0:4.18.0-477.143.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.143.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.143.1.el8_8.ppc64le as a component of Red Hat Enterprise Linux BaseOS E4S (v.8.8)
  • kernel-debug-0:4.18.0-477.143.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.143.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.143.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.143.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.143.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.143.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.143.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.143.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.143.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.143.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.143.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. Workaround: To mitigate this issue, prevent the `rxe` kernel module from loading. This can be achieved by creating a blacklist rule. 1. Create a file `/etc/modprobe.d/blacklist-rxe.conf` with the following content: ``` blacklist rxe install rxe /bin/true ``` 2. Rebuild the initial ramdisk: ```bash dracut -f -v ``` 3. Reboot the system for the changes to take effect. Warning: Blacklisting the `rxe` module may impact functionality that relies on Soft RoCE. Workaround: To mitigate this issue, prevent module ib_umad 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: 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 `can` kernel module from loading if CAN functionality is not required. This can be achieved by blacklisting the module. Create a file named `/etc/modprobe.d/blacklist-can.conf` with the following content: ``` blacklist can install can /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 may impact systems that rely on CAN interfaces for their operation. Workaround: See the security bulletin for a detailed mitigation procedure.

🔗 References (11)