Red Hat Security Advisory: OpenShift Container Platform 4.12.102 bug fix and security update
🔗 CVE IDs covered (10)
📋 Description
CVE-2026-6893 — dracut: dracut: Root code execution via DHCP options command injection CVE-2026-15816 — dracut: dracut: root code execution via unescaped error message written to sourced emergency hook script in die() CVE-2026-16445 — dracut: dracut: Root code execution via DHCP options command injection in NetworkManager initrd module CVE-2026-54369 — acl: Symlink traversal privilege escalation via libacl functions CVE-2026-64564 — kernel: sctp: don't free the ASCONF's own transport in DEL-IP processing CVE-2026-68121 — kernel: pppoe: reload header pointer after dev_hard_header() CVE-2026-80863 — kernel: RDMA/rxe: Fix OOB in free_rd_atomic_resources() CVE-2026-80864 — kernel: RDMA/rxe: Fix responder UAF on IB_QP_MAX_DEST_RD_ATOMIC modify_qp CVE-2026-99999 — kernel: ipv4: validate checksum_start before completing checksum CVE-2026-114406 — ca-certificates: Distrust eMudhra intermediate CA certificates due to security concerns
🎯 Affected products2
- Red Hat OpenShift Container Platform 4.12
- rhcos-x86_64-412.86.202610250235-0 as a component of Red Hat OpenShift Container Platform 4.12
✅ Remediation
For OpenShift Container Platform 4.12 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.redhat.com/en/documentation/openshift_container_platform/4.12/html/release_notes You may download the oc tool and use it to inspect release image metadata for x86_64 architecture. The image digest may be found at https://quay.io/repository/openshift-release-dev/ocp-release?tab=tags. The sha value for the release is as follows: (For x86_64 architecture) The image digest is sha256:3c8e5084a9c3a8e2e8ff8ef2d5c653a003f8d25f5db569e0d2b865af5443f076 All OpenShift Container Platform 4.12 users are advised to upgrade to these updated packages and images when they are available in the appropriate release channel. To check for available updates, use the OpenShift CLI (oc) or web console. Instructions for upgrading a cluster are available at https://docs.redhat.com/en/documentation/openshift_container_platform/4.12/html-single/updating_clusters/index#updating-cluster-within-minor. Workaround: To mitigate this issue, ensure that systems configured to obtain network settings via DHCP in the initramfs are only booted on trusted networks. This vulnerability requires an attacker to control a DHCP server on the adjacent network segment. If network configuration via DHCP is not strictly necessary during the initramfs phase, consider using static network configuration. Workaround: Restrict DHCP server access on networks used for network boot (DHCP snooping, dedicated/trusted provisioning VLANs) until a fix is available. Workaround: Avoid using the root=dhcp/netroot=dhcp/root=dhcp6/netroot=dhcp6 kernel command-line options — these cause dracut to trust the DHCP server's root-path option to determine the boot target. Configuring the netroot target explicitly on the kernel/PXE command line instead (e.g. netroot=nfs:<server>:<path> or netroot=iscsi:... with a literal value). Workaround: Restrict unprivileged users from creating symlinks in directories that privileged processes operate on with ACL commands. Where possible, use the fs.protected_symlinks sysctl (enabled by default on RHEL 7+), which prevents symlink following in world-writable sticky directories unless the owner of the symlink matches the owner of the target file or directory. Workaround: To mitigate this issue, prevent the `sctp` kernel module from loading. Create a file named `/etc/modprobe.d/disable-sctp.conf` with the following content: ``` install sctp /bin/true blacklist sctp ``` After creating the file, regenerate the initramfs and reboot the system for the changes to take effect. Applications or services that rely on the SCTP protocol cannot use this mitigation and should prioritize applying the fix. Workaround: See the security bulletin for a detailed mitigation procedure. Workaround: To mitigate this issue, prevent module rdma_rxe 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, prevent the rdma_rxe kernel module from being loaded. 1. Create a configuration file in /etc/modprobe.d to disable loading of the module: # echo "install rdma_rxe /bin/true" > /etc/modprobe.d/disable-rdma_rxe.conf 2. If the module is currently loaded, attempt to unload it: # modprobe -r rdma_rxe Caveats: Disabling this module prevents the creation and operation of software RDMA over Converged Ethernet (Soft-RoCE) devices. Applications requiring rdma_rxe will fail to initialize. If the module is currently in active use and cannot be unloaded dynamically, a system reboot is required to ensure the module is fully disabled. 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.
🔗 References (13)
- selfhttps://access.redhat.com/errata/RHSA-2026:90272
- externalhttps://access.redhat.com/security/updates/classification/#critical
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2459963
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2490277
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2500889
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2503147
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2510890
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2513233
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2528646
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2528665
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2553429
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2556046
- selfhttps://security.access.redhat.com/data/csaf/v2/advisories/2026/rhsa-2026_90272.json