CVE-2026-39402 lxc lxc-user-nic insufficient ownership validation allows cross-tenant OVS port deletion
- Published
- Updated
- Exploit status
- No public exploit known
- CISA SSVC
- Proof of concept public · automatable: no · technical impact: partial
- Technology
- UbuntuDebian
Description
lxc is a Linux container runtime. In the setuid helper lxc-user-nic, the delete path contains a logic flaw in the find_line() function that allows an unprivileged user to delete OVS-attached network interfaces belonging to other users. When lxc-user-nic delete scans its NIC database to authorize a deletion request, the interface name comparison can set the authorization flag based on a name match alone, even when the ownership, type, and link fields in that database entry belong to a different user. The vulnerable check sits after the goto next label handling, meaning it is reachable on lines where earlier ownership checks failed or were skipped. Because nothing downstream of this authorization signal re-verifies that the matched database line actually belongs to the caller, an unprivileged attacker with a valid lxc-usernet policy entry can trigger deletion of another user's OVS port on the same bridge.
This is limited to multi-tenant environments using lxc-user-nic with OpenVSwitch bridges. The impact is denial of service - one tenant can repeatedly disconnect networking from containers run by another tenant on shared infrastructure. This is patched in version 7.0.0.
Upgrade path
8 packages: 7 fixed.
| Package | Affected | Fixed in | Status |
|---|---|---|---|
| debian/lxc(Debian 12) | < 1:5.0.2-1+deb12u4; = 1:5.0.2-1; = 1:5.0.2-1+deb12u1; = 1:5.0.2-1+deb12u2 +1 more | 1:5.0.2-1+deb12u4 | Fixed |
| debian/lxc(Debian 13) | < 1:6.0.4-4+deb13u3; = 1:6.0.4-4; = 1:6.0.4-4+deb13u1; = 1:6.0.4-4+deb13u2 | 1:6.0.4-4+deb13u3 | Fixed |
| debian/lxc(Debian 14) | < 1:7.0.0-1; = 1:6.0.4-4; = 1:6.0.5-1; = 1:6.0.5-2 +3 more | 1:7.0.0-1 | Fixed |
| linuxcontainers lxc | < 7.0.0 | 7.0.0 | Fixed |
| ubuntu/lxc(Ubuntu 22.04) | < 1:5.0.0~git2209-g5a7b9ce67-0ubuntu1.1+esm1 | 1:5.0.0~git2209-g5a7b9ce67-0ubuntu1.1+esm1 | Fixed |
| ubuntu/lxc(Ubuntu 24.04) | < 1:5.0.3-2ubuntu7.3+esm1 | 1:5.0.3-2ubuntu7.3+esm1 | Fixed |
| ubuntu/lxc(Ubuntu 26.04) | < 1:6.0.6-1ubuntu1+esm1 | 1:6.0.6-1ubuntu1+esm1 | Fixed |
| lxc | = < 7.0.0 | No fix listed | Versions listed |
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| lxc | = < 7.0.0 | No fix listed |
| debian/lxc(Debian:12) | < 1:5.0.2-1+deb12u4 | 1:5.0.2-1+deb12u4 |
| debian/lxc(Debian:12) | = 1:5.0.2-1 | No fix listed |
| debian/lxc(Debian:12) | = 1:5.0.2-1+deb12u1 | No fix listed |
| debian/lxc(Debian:12) | = 1:5.0.2-1+deb12u2 | No fix listed |
| debian/lxc(Debian:12) | = 1:5.0.2-1+deb12u3 | No fix listed |
| debian/lxc(Debian:13) | < 1:6.0.4-4+deb13u3 | 1:6.0.4-4+deb13u3 |
| debian/lxc(Debian:13) | = 1:6.0.4-4 | No fix listed |
| debian/lxc(Debian:13) | = 1:6.0.4-4+deb13u1 | No fix listed |
| debian/lxc(Debian:13) | = 1:6.0.4-4+deb13u2 | No fix listed |
| debian/lxc(Debian:14) | < 1:7.0.0-1 | 1:7.0.0-1 |
| debian/lxc(Debian:14) | = 1:6.0.4-4 | No fix listed |
| debian/lxc(Debian:14) | = 1:6.0.5-1 | No fix listed |
| debian/lxc(Debian:14) | = 1:6.0.5-2 | No fix listed |
| debian/lxc(Debian:14) | = 1:6.0.6-1 | No fix listed |
| debian/lxc(Debian:14) | = 1:6.0.6-2 | No fix listed |
| debian/lxc(Debian:14) | = 1:6.0.6-3 | No fix listed |
| ubuntu/lxc(Ubuntu:22.04) | < 1:5.0.0~git2209-g5a7b9ce67-0ubuntu1.1+esm1 | 1:5.0.0~git2209-g5a7b9ce67-0ubuntu1.1+esm1 |
| ubuntu/lxc(Ubuntu:24.04) | < 1:5.0.3-2ubuntu7.3+esm1 | 1:5.0.3-2ubuntu7.3+esm1 |
| ubuntu/lxc(Ubuntu:26.04) | < 1:6.0.6-1ubuntu1+esm1 | 1:6.0.6-1ubuntu1+esm1 |
| linuxcontainers lxc | < 7.0.0 | 7.0.0 |
References
- https://github.com/lxc/lxc/security/advisories/GHSA-3m9j-g9gc-vcvq exploit vendor-advisory
- Debian Security Tracker CVE-2026-39402 vendor-advisory
- Ubuntu CVE tracker vendor-advisory
- USN-8826-1 vendor-advisory
- www.cve.org