GPU VulnDB

Database/Container, Kubernetes & orchestration

Incus: rebuilt never-started unprivileged container boots without a user namespace, as host root

CVSS 9.3CVE-2026-130774Container, Kubernetes & orchestrationcurated

Impact

If an unprivileged container is rebuilt before it has ever been started, Incus boots it without a user namespace. Root inside that container is then uid 0 on the host, keeps capabilities such as sys_module, and has no device cgroup restriction. That is enough to load kernel modules and take over the host. On a shared node, one tenant controlling a container becomes host root, which puts every other workload and any GPU or device passed through on that host at risk.

Who can reach it

A user who can rebuild an unprivileged container that has never been started, then run as root inside it (CVSS PR:L, local). Authentication to Incus is needed to trigger the rebuild.

What to do

Upgrade Incus to 7.6.0 or later and restart the Incus daemon. Containers that were rebuilt and started on an affected version may already be running without a user namespace. Check them and restart them under the fixed version. If a host may have been compromised, treat it as untrusted: loaded kernel modules survive until reboot, so drain and reboot or reimage the node.

References

Related entries

All Container, Kubernetes & orchestration entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.