RHSA-2026:23233HighCVSS 8.2

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

Published
June 11, 2026
Last Modified
August 17, 2026

🔗 CVE IDs covered (8)

CVE-2026-39979 →CVE-2026-40164 →CVE-2026-41035 →CVE-2026-43284 →CVE-2026-43503 →CVE-2026-46300 →CVE-2026-4878 →CVE-2026-35535 →

📋 Description

CVE-2026-4878 — libcap: libcap: Privilege escalation via TOCTOU race condition in cap_set_file() CVE-2026-35535 — sudo: Sudo: Privilege escalation due to failure in privilege drop calls CVE-2026-39979 — jq: out-of-bounds read in jv_parse_sized() on error formatting for non-NUL-terminated buffers CVE-2026-40164 — jq: jq: Denial of Service via crafted JSON object causing hash collisions CVE-2026-41035 — rsync: Rsync: Use-after-free vulnerability in extended attribute handling CVE-2026-43284 — kernel: "Dirty Frag" ESP XFRM variant is a new universal Local Privilege Escalation (LPE) vulnerability in the Linux kernel 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

🎯 Affected products5

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

✅ Remediation

For OpenShift Container Platform 4.15 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.15/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:5bc12d09997fd6b86a5d7ab2a5bf482474cb95b624c22a4d05607e3397302cac (For s390x architecture) The image digest is sha256:10bccfc41bb95736b0d6a1a91e3fb1c968771e3f023019abdb7480ac7de1a107 (For ppc64le architecture) The image digest is sha256:9adfb17a263640a6c55c11fdab9ae0ccb7ac73e421fb674318c17d616c4ae4ad (For aarch64 architecture) The image digest is sha256:9f35e9b44efc724d4e44a788808e0192d9710a993a4e0b2f2993a6444201f896 All OpenShift Container Platform 4.15 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.15/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: To mitigate this issue, manually ensure that every buffer is NUL-terminated before passing it to the 'jv_parse_sized' function. 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 vulnerability, avoid using the -X or --xattrs options with rsync if extended attribute handling is not essential for your operations. Disabling these options prevents the vulnerable code path from being exercised. This may impact functionality that relies on extended attributes. Workaround: See the security bulletin for a detailed mitigation procedure.

🔗 References (10)