RHSA-2026:28887CriticalCVSS 8.8

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

Published
July 1, 2026
Last Modified
August 17, 2026

🔗 CVE IDs covered (10)

CVE-2026-46331 →CVE-2026-4878 →CVE-2026-35385 →CVE-2026-35535 →CVE-2026-39979 →CVE-2026-40164 →CVE-2026-41035 →CVE-2026-43037 →CVE-2026-46243 →CVE-2026-46300 →

📋 Description

CVE-2026-4878 — libcap: libcap: Privilege escalation via TOCTOU race condition in cap_set_file() CVE-2026-35385 — OpenSSH: OpenSSH: Privilege escalation via scp legacy protocol when not preserving file mode 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-43037 — kernel: ip6_tunnel: clear skb2->cb[] in ip4ip6_err() CVE-2026-46243 — kernel: Linux kernel: smb: client: reject userspace cifs.spnego descriptions 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-46331 — kernel: net/sched: act_pedit: extend the writable skb range per key

🎯 Affected products5

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

✅ Remediation

For OpenShift Container Platform 4.14 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.14/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:e042266bfafccf3f8f6afe39da6b9b91738fa836ba5159fa485e7eede34aefe3 (For s390x architecture) The image digest is sha256:8d95bf587d1e567ee1d8f0635da6dcc6f458d8de115bf7fff93719ea008d4f20 (For ppc64le architecture) The image digest is sha256:e5f2c65060d18b90639543de234f78356cefa2d77a8d4dbbaa00675171e7a2cd (For aarch64 architecture) The image digest is sha256:027ef407502543950504fd28ac3e4258594b52444fd471610bcc3da9656e816e All OpenShift Container Platform 4.14 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.14/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 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: 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: Mitigation for this issue is to skip loading the affected module `ip6_tunnel` onto the system till we have a fix available, this can be done by a blacklist mechanism, this will ensure the driver is not loaded at the boot time. ~~~ How do I blacklist a kernel module to prevent it from loading automatically? https://access.redhat.com/solutions/41278 ~~~ We may also want to detection and monitoring an affected system as below: ~~~ Monitor for exploitation attempts: # Enable kernel audit for IPv6 tunnel operations auditctl -a always,exit -F arch=b64 -S socket -F a0=10 -F a1=3 -k ipv6_tunnel # Monitor system logs for kernel panics/crashes journalctl -k -p err -f | grep -i "ip6_tunnel\|icmp\|stack" ~~~ Workaround: See the security bulletin for a detailed mitigation procedure.

🔗 References (13)