runc is a CLI tool for spawning and running containers on Linux according to the OCI specification. In runc 1.1.11 and earlier, due to an internal file descriptor leak, an attacker could cause a newly-spawned container process (from runc exec) to have a working directory in the host filesystem namespace, allowing for a container escape by giving access to the host filesystem ("attack 2"). The same attack could be used by a malicious image to allow a container process to gain access to the host filesystem through runc run ("attack 1"). Variants of attacks 1 and 2 could be also be used to overwrite semi-arbitrary host binaries, allowing for complete container escapes ("attack 3a" and "attack 3b"). runc 1.1.12 includes patches for this issue.
https://securelist.com/vulnerability-report-q1-2024/112554/
https://www.wiz.io/blog/leaky-vessels-container-escape-vulnerabilities
https://www.alibabacloud.com/en/notice/cve_2024_21626?_p_lc=1
https://www.darkreading.com/cloud-security/leaky-vessel-cloud-bugs-container-escapes-globally
https://snyk.io/blog/leaky-vessels-docker-runc-container-breakout-vulnerabilities/
https://lists.debian.org/debian-lts-announce/2024/02/msg00005.html
https://github.com/opencontainers/runc/security/advisories/GHSA-xr7r-f8xq-vfvv
https://github.com/opencontainers/runc/releases/tag/v1.1.12
https://github.com/opencontainers/runc/commit/02120488a4c0fc487d1ed2867e901eeed7ce8ecf
http://www.openwall.com/lists/oss-security/2024/02/02/3