CVE-2025-64507: Incus vulnerable to local privilege escalation through custom storage volumes
Impact This affects any Incus user in an environment where an unprivileged user may have root access to a container with an attached custom storage volume that has the security.shifted property set to true as well as access to the host as an unprivileged user.
The most common case for this would be systems using incus-user with the less privileged incus group to provide unprivileged users with an isolated restricted access to Incus. Such users may be able to create a custom storage volume with the necessary property (depending on kernel and filesystem support) and can then write a setuid binary from within the container which can be executed as an unpriivleged user on the host to gain root privileges.
Patches A patch for this issue is available here: https://github.com/lxc/incus/pull/2642
The first commit changes the permissions for any new storage pool, the second commit applies it on startup to all existing storage pools.
Workarounds Permissions can be manually restricted until a patched version of Incus is deployed.
This is done with:
chmod 0700 /var/lib/incus/storage-pools// chmod 0711 /var/lib/incus/storage-pools//buckets chmod 0711 /var/lib/incus/storage-pools//container
Those are the same permissions which will be applied by the patched Incus for both new and existing storage pools.
References This was reported publicly on Github: https://github.com/lxc/incus/issues/2641
Other sources
Incus is a system container and virtual machine manager. An issue in versions prior to 6.0.6 and 6.19.0 affects any Incus user in an environment where an unprivileged user may have root access to a container with an attached custom storage volume that has the security.shifted property set to true as well as access to the host as an unprivileged user. The most common case for this would be systems using incus-user with the less privileged incus group to provide unprivileged users with an isolated restricted access to Incus. Such users may be able to create a custom storage volume with the necessary property (depending on kernel and filesystem support) and can then write a setuid binary from within the container which can be executed as an unprivileged user on the host to gain root privileges. A patch for this issue is expected in versions 6.0.6 and 6.19.0. As a workaround, permissions can be manually restricted until a patched version of Incus is deployed.
— NVD
Affected Software
Remediation
Patch Available
Patch Available
Event History
Frequently Asked Questions
What is the severity of CVE-2025-64507?
CVE-2025-64507 has been classified as a high-severity vulnerability.
How do I fix CVE-2025-64507?
To fix CVE-2025-64507, upgrade Incus to versions 6.0.6 or 6.19.0 and ensure proper permissions for container access.
Who is affected by CVE-2025-64507?
CVE-2025-64507 affects any Incus user who has unprivileged users with potential root access to containers with custom storage volumes.
What versions of Incus are vulnerable to CVE-2025-64507?
Incus versions prior to 6.0.6 and 6.19.0 are vulnerable to CVE-2025-64507.
What is the main risk associated with CVE-2025-64507?
The main risk of CVE-2025-64507 is that unprivileged users can potentially gain elevated permissions through the exploit.