RHSA-2026:44231HighCVSS 7.8

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

Published
July 29, 2026
Last Modified
August 18, 2026

🔗 CVE IDs covered (6)

📋 Description

CVE-2026-31790 — openssl: openssl: Information Disclosure from Uninitialized Memory via Invalid RSA Public Key CVE-2026-43329 — kernel: netfilter: flowtable: strictly check for maximum number of actions CVE-2026-46242 — kernel: eventpoll: fix ep_remove struct eventpoll / struct file UAF CVE-2026-46316 — kernel: KVM: arm64: vgic-its: Drop the translation cache reference only for the erased entry CVE-2026-46323 — kernel: Linux kernel: Use-After-Free in net/gro due to improper handling of zerocopy skbs CVE-2026-53359 — kernel: KVM: x86: Fix shadow paging use-after-free due to unexpected role

🎯 Affected products5

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

✅ Remediation

For OpenShift Container Platform 4.19 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.19/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:800712da0a4fa8353d0f94a06efa9e6a1479726b653b0d8ad1243f014d40f1bf (For s390x architecture) The image digest is sha256:4d0acc69187a33b0b10a3eeebbe7d60a7538e3c7a70e37054370f7b24b649349 (For ppc64le architecture) The image digest is sha256:310602fabcd047776ecc3c52f82b03a56f4fbe79c1b052a5a6163a271f350227 (For aarch64 architecture) The image digest is sha256:feeb5daa474f243df61a0e7043c8242bfdfbaa445ca5a22565bc8dcbe42aae93 All OpenShift Container Platform 4.19 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.19/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: 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: 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

🔗 References (9)