Security update for runc SUSE Patch security@suse.de SUSE Security Team SUSE-SU-2025:20353-1 Final 1 1 2025-05-21T11:12:02Z current 2025-05-21T11:12:02Z 2025-05-21T11:12:02Z cve-database/bin/generate-cvrf.pl 2017-02-24T01:00:00Z Security update for runc This update for runc fixes the following issues: Update to runc v1.2.6. Upstream changelog is available from <https://github.com/opencontainers/runc/releases/tag/v1.2.6>. Update to runc v1.2.0~rc3. Upstream changelog is available from <https://github.com/opencontainers/runc/releases/tag/v1.2.0-rc.3>. - CVE-2024-45310: Fixed that runc can be tricked into creating empty files/directories on host (bsc#1230092) The CVRF data is provided by SUSE under the Creative Commons License 4.0 with Attribution (CC-BY-4.0). SUSE-SLE-Micro-6.1-115 Copyright SUSE LLC under the Creative Commons License 4.0 with Attribution (CC-BY-4.0) https://www.suse.com/support/update/announcement/2025/suse-su-202520353-1/ Link for SUSE-SU-2025:20353-1 https://lists.suse.com/pipermail/sle-updates/2025-June/039506.html E-Mail link for SUSE-SU-2025:20353-1 https://www.suse.com/support/security/rating/ SUSE Security Ratings https://bugzilla.suse.com/1214960 SUSE Bug 1214960 https://bugzilla.suse.com/1230092 SUSE Bug 1230092 https://www.suse.com/security/cve/CVE-2024-45310/ SUSE CVE CVE-2024-45310 page SUSE Linux Micro 6.1 runc-1.2.6-slfo.1.1_1.1 runc-1.2.6-slfo.1.1_1.1 as a component of SUSE Linux Micro 6.1 runc is a CLI tool for spawning and running containers according to the OCI specification. runc 1.1.13 and earlier, as well as 1.2.0-rc2 and earlier, can be tricked into creating empty files or directories in arbitrary locations in the host filesystem by sharing a volume between two containers and exploiting a race with `os.MkdirAll`. While this could be used to create empty files, existing files would not be truncated. An attacker must have the ability to start containers using some kind of custom volume configuration. Containers using user namespaces are still affected, but the scope of places an attacker can create inodes can be significantly reduced. Sufficiently strict LSM policies (SELinux/Apparmor) can also in principle block this attack -- we suspect the industry standard SELinux policy may restrict this attack's scope but the exact scope of protection hasn't been analysed. This is exploitable using runc directly as well as through Docker and Kubernetes. The issue is fixed in runc v1.1.14 and v1.2.0-rc3. Some workarounds are available. Using user namespaces restricts this attack fairly significantly such that the attacker can only create inodes in directories that the remapped root user/group has write access to. Unless the root user is remapped to an actual user on the host (such as with rootless containers that don't use `/etc/sub[ug]id`), this in practice means that an attacker would only be able to create inodes in world-writable directories. A strict enough SELinux or AppArmor policy could in principle also restrict the scope if a specific label is applied to the runc runtime, though neither the extent to which the standard existing policies block this attack nor what exact policies are needed to sufficiently restrict this attack have been thoroughly tested. CVE-2024-45310 SUSE Linux Micro 6.1:runc-1.2.6-slfo.1.1_1.1 moderate To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520353-1/ https://www.suse.com/security/cve/CVE-2024-45310.html CVE-2024-45310 https://bugzilla.suse.com/1230092 SUSE Bug 1230092