|Description||A flaw was found in the Linux Kernel. The tun/tap sockets have their socket UID hardcoded to 0 due to a type confusion in their initialization function. While it will be often correct, as tuntap devices require CAP_NET_ADMIN, it may not always be the case, e.g., a non-root user only having that capability. This would make tun/tap sockets being incorrectly treated in filtering/routing decisions, possibly bypassing network filters.|
|Source||CVE (at NVD; CERT, LWN, oss-sec, fulldisc, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, GitHub advisories/code/issues, web search, more)|
Vulnerable and fixed packages
The table below lists information on source packages.
|linux (PTS)||jessie, jessie (lts)||3.16.84-1||vulnerable|
|stretch (lts), stretch||4.9.320-3||vulnerable|
|linux-5.10 (PTS)||stretch (lts), stretch||5.10.179-5~deb9u1||fixed|
The information below is based on the following data on fixed versions.