Skip to content
Fencer Intel
low 3.3

CVE-2017-5985 json

lxc-user-nic in Linux Containers (LXC) allows local users with a lxc-usernet allocation to create network interfaces on the host and choose…

published 2017-03-14 9 y ago modified 2026-06-17 4 mo ago also EUVD-2017-15054

cvss
3.3
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 27%
public exploits
0
none known

Summary

lxc-user-nic in Linux Containers (LXC) allows local users with a lxc-usernet allocation to create network interfaces on the host and choose the name of those interfaces by leveraging lack of netns ownership check.

Patch / fix

  • lxc Debian 14, Debian 13, Debian 12 1:2.0.7-2

debian advisories DEBIAN-CVE-2017-5985

  • lxc Ubuntu 14.04 LTS 1.0.9-0ubuntu3
  • lxc Ubuntu 16.04 LTS 2.0.7-0ubuntu1~16.04.2

ubuntu advisories UBUNTU-CVE-2017-5985

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • lxc openSUSE Tumbleweed 4.0.9-1.1

opensuse advisories openSUSE-SU-2024:11030-1

  • lxc Arch Linux 1:2.0.8-1

arch linux advisories AVG-204

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2017-5985 updated cvss 3.3

lxc: lxc-user-nic didn't verify network namespace ownership

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.34% chance of exploitation in the next 30 days, higher than 27% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 3.3 CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
NVD 2.0 2.1 AV:L/AC:L/Au:N/C:N/I:P/A:N

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.