Zhenchen Wang

When proxy networking with CA injection is enabled, a build can modify its CA bundle before cleanup. This may lead to the cleanup process blocking, operating outside the build rootfs (the root file system of the build environment), or failing without triggering a build failure.

In the `lxc-copy` utility and the public `lxc container::clone()` API, a flaw exists where the process can follow attacker-controlled symbolic links when updating the `/etc/hostname` file in a copied container root filesystem. This occurs when a privileged cloning process running as root clones a source rootfs that is attacker-controlled or less trusted. If a symlink is placed at `etc/hostname` or within an intermediate component, the clone operation preserves this symlink. When the process attempts to update the hostname without the `LXC CLONE KEEPNAME` flag, the write operation can resolve outside the destination rootfs, allowing the privileged process to truncate and overwrite an existing host file with the destination container name.

A bug in the CRI plugin allows the restoration of `container.log` from a checkpoint image without validating a symlinked path. This can lead to an arbitrary file read on the host system when using `kubectl logs`.