ppp: require CAP_NET_ADMIN in target netns for unattached ioctls
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 273ec51dd7ceaa76e038875d85061ec856d8905e · < 5013be175c7ffd8b39efbc3c9c4db5b10b85fea8| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ppp: require CAP_NET_ADMIN in target netns for unattached ioctls
/dev/ppp open is currently authorized against file->f_cred->user_ns, while unattached administrative ioctls operate on current->nsproxy->net_ns.
As a result, a local unprivileged user can create a new user namespace with CLONE_NEWUSER, gain CAP_NET_ADMIN only in that new user namespace, and still issue PPPIOCNEWUNIT, PPPIOCATTACH, or PPPIOCATTCHAN against an inherited network namespace.
Require CAP_NET_ADMIN in the user namespace that owns the target network namespace before handling unattached PPP administrative ioctls.
This preserves normal pppd operation in the network namespace it is actually privileged in, while rejecting the userns-only inherited-netns case.
From the CVE record · Linux
The Linux kernel's PPP device checks /dev/ppp access against a different user namespace from the one used by unattached administrative ioctls. A local unprivileged user can create a new user namespace, gain CAP_NET_ADMIN there, and issue PPPIOCNEWUNIT, PPPIOCATTACH, or PPPIOCATTCHAN against an inherited network namespace without that capability in the namespace that owns it.
Engineers running Linux kernels with the affected PPP ioctl behavior should check their systems; affected versions are not specified.