RHSA-2026:54581HighCVSS 8.8

Red Hat Security Advisory: OpenShift Container Platform 4.20.34 bug fix and security update

Published
August 18, 2026
Last Modified
August 19, 2026

🔗 CVE IDs covered (6)

CVE-2025-40026 →CVE-2026-1933 →CVE-2026-14474 →CVE-2026-14476 →CVE-2025-5222 →CVE-2025-10263 →

📋 Description

CVE-2025-5222 — icu: Stack buffer overflow in the SRBRoot::addTag function CVE-2025-10263 — kernel: Arm Processors: Privilege escalation or information disclosure via writes to higher exception level resources CVE-2025-40026 — kernel: KVM: x86: Don't (re)check L1 intercepts when completing userspace I/O CVE-2026-1933 — samba: Missing access check on reparse point operations CVE-2026-14474 — sssd: sssd: sudo LDAP provider searches entire directory tree for sudoRole objects by default, enabling privilege escalation CVE-2026-14476 — sssd: sssd: GPO cache path traversal via unsanitized gPCFileSysPath allows Kerberos authentication bypass

🎯 Affected products5

  • Red Hat OpenShift Container Platform 4.20
  • rhcos-aarch64-4.20.9.6.202608121719-0 as a component of Red Hat OpenShift Container Platform 4.20
  • rhcos-ppc64le-4.20.9.6.202608121719-0 as a component of Red Hat OpenShift Container Platform 4.20
  • rhcos-s390x-4.20.9.6.202608121719-0 as a component of Red Hat OpenShift Container Platform 4.20
  • rhcos-x86_64-4.20.9.6.202608121719-0 as a component of Red Hat OpenShift Container Platform 4.20

✅ Remediation

For OpenShift Container Platform 4.20 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.20/html/release_notes/ You may download the oc tool and use it to inspect release image metadata for x86_64, s390x, ppc64le, and aarch64 architectures. The image digests may be found at https://quay.io/repository/openshift-release-dev/ocp-release?tab=tags. The sha values for the release are as follows: (For x86_64 architecture) The image digest is sha256:a6182ea1e41a144d7bcd4bd93596851b907ff1ae7711c1c29b8b26baf3eb03f7 (For s390x architecture) The image digest is sha256:2dfe6dad7b9a4411e3280cf9a6e3136482221c28f6407ebd4867446ed08a1cbc (For ppc64le architecture) The image digest is sha256:bc0a8650a476f595596c60a554b6068ffe5e08ebe98addbf27de6d576c2f6dd1 (For aarch64 architecture) The image digest is sha256:f670213448b515446bcaf81fd580f5c17ac1bf6dd84e66ba94cdfcf5c3d4d5e0 All OpenShift Container Platform 4.20 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.20/html-single/updating_clusters/index#updating-cluster-cli. 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: This vulnerability can be mitigated by disabling nested virtualization. Create a file in `/etc/modprobe.d/` with a descriptive name, such as `cve-2026-53359-mitigation.conf`. In that file, disable nested virtualization for the `kvm_intel` and `kvm_amd` kernel modules: ``` options kvm-intel nested=0 options kvm-amd nested=0 ``` Use `lsmod` to determine if either module is already loaded. If so, remove loaded modules with `modprobe -r`. To validate that nested virtualization is disabled, read the files `/sys/module/kvm_intel/parameters/nested` and `/sys/module/kvm_amd/parameters/nested`. If these modules are loaded, those files should read `N` to indicate that the feature is disabled. In OpenShift 4, a MachineConfig can be utilized to create a modprobe configuration allowing control of the module on applicable nodes. See the following article for an example. https://access.redhat.com/solutions/6979679 Workaround: Administrators can mitigate this issue by ensuring users who access a read only = yes Samba share do not have filesystem-level write permission to the exported files. A server administrator may also monitor and remove unintended "user.SmbReparse" xattr (extended attributes) and the associated FILE_ATTRIBUTE_REPARSE_POINT "user.DosAttrib" bit metadata if exploitation is suspected. Workaround: Set ldap_sudo_search_base explicitly in /etc/sssd/sssd.conf to restrict the search to the designated sudoers container: [domain/example.com] ldap_sudo_search_base = ou=sudoers,dc=example,dc=com Additionally, restrict LDAP ACLs to prevent non-admin principals from creating sudoRole objects outside the designated sudoers container. Workaround: Set ad_gpo_access_control = disabled in /etc/sssd/sssd.conf to disable GPO fetching entirely. Note that this removes GPO-based login policy enforcement.

🔗 References (10)