RATATOSK
← All releases

CRI-Ov1.36.9

Security 1Breaking changes 1Dependency updates 1

Get CRI-O alerts

Email is sent weekly only when there are changes to check; critical security advisories are sent immediately.

Security1high1

CRI-O linked log volume write vulnerability fixed

high
AffectsNot stated in the release notes

A container could influence CRI-O or conmon writes to host files outside its log directory, compromising host-side integrity and potentially enabling root command execution if a targeted file was later executed. After the fix, containers see linked log volumes as read-only, including through kubelet subPath bind aliases, while CRI-O can still write from its host-side view; log collectors must keep offsets and buffers elsewhere.

Show release-note lines
Security advisory
When a container uses the opt-in `link-logs.crio.io` annotation, CRI-O exposes the pod's log directory through a pod-owned emptyDir and intends that view to be read-only. That isolation was not effective, so a container could alter host-side log state that CRI-O and conmon depend on. This gave the container a way to influence writes made by a privileged component against host files outside its own log directory, crossing the container-to-host integrity boundary; where such a file is later executed by the host, it can amount to command execution as root.
The flaw exists since the feature's introduction in 1.28.0 and is reachable only when the annotation is enabled for the runtime handler; deployments that do not enable it are unaffected. Exploitation depends on pre-existing host state and remains subject to mandatory access control (MAC) policy, which places the attack complexity at high.
The linked log volume is now mounted read-only in containers even when the container requests write access, including when the volume is reached through kubelet subPath bind aliases. The host-side view stays writable to CRI-O itself so that log linking and SELinux labeling keep working. Users should upgrade to one of:
This is a behaviour change: log collectors must keep writable state such as offsets and buffers in a separate volume.
- Do not enable `link-logs.crio.io` for any runtime handler. Deployments that leave it out of `allowed_annotations` are not reachable through a pod.
- Run the containers of affected pods as an unprivileged UID that cannot become uid 0 (`runAsNonRoot`, no `setuid` escalation, no user-namespace mapping to host root). Kubelet creates the pod and container log directories under `/var/log/pods` as root-owned and not writable by group or other (0755), so such a container cannot create entries in the linked tree. This is conditional hardening: pods whose containers run as root, whether requested or inherited from the image, remain exposed.
github.com/cri-o/cri-o/security/advisories/GHSA-pw8r-75cr-c993

Breaking changes1

CRI-O shutdown deadlock fixed

AffectsCNI readiness handling

During node shutdown, in-flight RPCs waiting for CNI readiness could cause CRI-O to ignore SIGTERM and deadlock. The CNI manager now shuts down before the gRPC server; waiting RPCs return an error, and the server is forcibly stopped if graceful shutdown has not finished after 30 seconds.

Show release-note lines
 - Fixed a deadlock where CRI-O ignored SIGTERM when in-flight RPCs were blocked waiting for CNI readiness during node shutdown. The CNI manager is now shut down before the gRPC server stops, and a forced stop is scheduled as a fallback after 30 seconds. (#10516, @openshift-cherrypick-robot)
github.com/cri-o/cri-o/releases/tag/v1.36.9

Dependency updates1

    1 more, none mentioning security
    • #### Dependency-Change - CRI-O's minimum Go version and static-build compiler are now Go 1.26.10. (#10492, @bitoku)

    Summaries are produced by AI, so they can be wrong, and they are provided without warranty.