3 ms·
According to https://security-tracker.debian.org/tracker/CVE-2016-8655 https://security-tracker.debian.org/tracker/CVE-2016-8655 "Non-privileged user namespace
by ars 10y ago
According to https://security-tracker.debian.org/tracker/CVE-2016-8655 https://security-tracker.debian.org/tracker/CVE-2016-8655
"Non-privileged user namespaces disabled by default, only vulnerable with sysctl kernel.unprivileged_userns_clone=1"
But: ... on systems where unprivileged namespaces are enabled (Ubuntu, Fedora, etc).
Interesting that Ubuntu and Debian differ here.
As of right now it doesn't appear that any distribution has fixed this yet, which is odd since it was fixed upstream a week ago.
- burgerLife 10y agoIt has been fixed in Ubuntu and OpenVZ: https://www.ubuntu.com/usn/usn-3151-1/ https://www.ubuntu.com/usn/usn-3151-1/ https://virtuozzo.com/linux-kernel-security-exploit-fix/ https://virtuozzo.com/linux-kernel-security-exploit-fix/
- zoobab 10y agoIn Virtuozzo at least. They don't mention OpenVZ.
- etcet 10y agoAs many people found out with Dirty COW, the latest version of OpenVZ doesn't receive tested patched kernels in response to newly discovered bugs. Their options are to run a nightly kernel build or to pay for Virtuozzo for their 'ReadyKernel' patches: "Virtuozzo team uploads stable kernels for OpenVZ version 7, tested for our commercial customers, approximately once a quarter. In between, we do not test or release any kernels - all the intermediate updates are delivered to our commercial customers in rebootless (kpatch) format without building full kernel updates. Again, this is a part of our commercial offering. As for the contributions to the community product, we still build these kernels for the "factory" repository. However, we are not equipped to test them on regular basis, between these quarterly updates."
- fulafel 10y agoAlso, be careful about turning that off on Ubuntu if using Canonical's live patching - that is built on snaps and requires user namespaces.