CRI-O v1.23.4

The release notes have been generated for the commit range v1.23.3…2ff6a26 on Tue, 03 Jan 2023 20:17:48 UTC.

Downloads

Download one of our static release bundles via our Google Cloud Bucket:

CRI-O now logs the stage of container or pod creation under system load. This allows users to find why their creation requests are stalling. (#6303, @haircommander)

Fix CVE-2022-27652 by dropping and refusing to add any inheritable capabilities (#5770, @haircommander)
Fix a bug where ExecSync requests (exec probes) could use an arbitrary amount of memory and disk. Output from ExecSync requests is now limited to 16MB (the amount that exec output was limited to in the dockershim). Disk limiting requires conmon 2.1.2 to work. See https://github.com/cri-o/cri-o/security/advisories/GHSA-fcm2-6c3h-pg6j and CVE-2022-1708 for more information. (#5937, @haircommander)
Fix a bug where child processes of containers in the host’s PID namespace appear to leak after the child exits (#5977, @haircommander)
Fix a panic caused by using the improper Result structure version when setting up CNI plugins (#6320, @juanfresia)
Fixed bug to restore /var/lib/containers/storage/overlay/backingFsBlockDev on XFS file systems. (#6390, @saschagrunert)
Revert fix for CVE-2022-27652 by re-adding inheritable capabilities. While there is a workaround, we believe this causes regression mid cycle with is contrary to CRI-O’s backporting policy. The risk of the CVE is low, and so there is little risk in reverting here. (#6168, @haircommander)
Update cni_default_network to not be commented by default in the output of crio config (#5566, @haircommander)

Fix a bug about log container (#6409, @laxmanvallandas)
Fix a bug where a container is stuck in INIT because CRI-O believes it to be paused, and never updates the state (#6143, @openshift-cherrypick-robot)
Fix a bug where exit files were never cleaned up from /run/crio/exits (#6171, @openshift-cherrypick-robot)
Fix a rare deadlock while communicating to systemd (RHBZ 2082344) (#5961, @openshift-cherrypick-robot)
Use default umask 0o022 if CRI-O runs under a different umask value. (#6053, @openshift-cherrypick-robot)

Nothing has changed.