Bug 2568099 - CVE-2026-100395 lxc: lxc: Arbitrary file overwrite via symbolic link following during container clone operations [fedora-all]
Summary: CVE-2026-100395 lxc: lxc: Arbitrary file overwrite via symbolic link followin...
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: lxc
Version: rawhide
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
Assignee: Thomas Moschny
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: {"flaws": ["1fc8d9ec-62b5-40d1-8b94-0...
Depends On:
Blocks: CVE-2026-100395
TreeView+ depends on / blocked
 
Reported: 2026-11-06 11:47 UTC by Vladimir Vasilev
Modified: 2026-11-06 11:47 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Vladimir Vasilev 2026-11-06 11:47:57 UTC
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.

LXC is a userspace interface for the Linux kernel containment features used to create and manage system containers. In LXC 7.0.0 and earlier, lxc-copy and the public liblxc clone() API can follow attacker-controlled symbolic links while updating /etc/hostname in a copied container root filesystem. The affected surfaces are lxc-copy and liblxc's public lxc_container::clone() API. The privileged cloning process must run as root. The source rootfs must be attacker-controlled or less trusted. A symlink can be placed at etc/hostname or in an intermediate component. The clone operation preserves the symlink before updating the hostname. The vulnerable write truncates and overwrites an existing file outside the destination rootfs. When root clones an untrusted container without LXC_CLONE_KEEPNAME, the copied symlink can resolve outside the destination rootfs and cause the privileged process to overwrite an existing host file with the destination container name. Unprivileged use and managers with independent cloning implementations are not affected. LXC_CLONE_KEEPNAME avoids the hostname update and therefore the affected write.


Note You need to log in before you can comment on or make changes to this bug.