In affected versions it was found that rootless runc makes /sys/fs/cgroup
writable in following conditons:
- when runc is executed inside the user namespace, and the
config.json
does not specify the cgroup namespace to be unshared (e.g.., (docker|podman|nerdctl) run --cgroupns=host
, with Rootless Docker/Podman/nerdctl)
- or, when runc is executed outside the user namespace, and
/sys
is mounted with rbind, ro
(e.g., runc spec --rootless
; this condition is very rare).
A container may gain the write access to user-owned cgroup hierarchy /sys/fs/cgroup/user.slice/...
on the host.
In affected versions it was found that rootless runc makes
/sys/fs/cgroup
writable in following conditons:config.json
does not specify the cgroup namespace to be unshared (e.g..,(docker|podman|nerdctl) run --cgroupns=host
, with Rootless Docker/Podman/nerdctl)/sys
is mounted withrbind, ro
(e.g.,runc spec --rootless
; this condition is very rare).A container may gain the write access to user-owned cgroup hierarchy
/sys/fs/cgroup/user.slice/...
on the host.