CVE-2025-64507: Incus vulnerable to local privilege escalation through custom storage volumes

Published Nov 10, 2025
·
Updated

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

6 affected components
Incus Incus<6.0.6, <6.19.0
go/github.com/lxc/incus<=0.7.0
go/github.com/lxc/incus/v6<=6.0.6
go/github.com/lxc/incus/v6>=6.1.0<=6.18.0
linuxcontainers Incus<6.0.6
linuxcontainers Incus>=6.1.0<6.19.0

Event History

Nov 10, 2025
CVE Published
via MITRE·09:56 PM
Data Sourced
via MITRE·09:56 PM
DescriptionWeakness
Data Sourced
via NVD·10:15 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·10:15 PM
RemedyAffected Software
Nov 13, 2025
Advisory Published
via GitHub·04:04 PM
Data Sourced
via GitHub·04:04 PM
DescriptionWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-64507?

CVE-2025-64507 has been classified as a high-severity vulnerability.

2

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.

3

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.

4

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.

5

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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203