First published: Sun Aug 06 2023(Updated: )
A flaw 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. The original fix for the <a href="https://access.redhat.com/security/cve/CVE-2023-1076">CVE-2023-1076</a> was incorrect. The problem is that the following upstream commits (that were fix for the <a href="https://access.redhat.com/security/cve/CVE-2023-1076">CVE-2023-1076</a>) - a096ccca6e50 ("tun: tun_chr_open(): correctly initialize socket uid"), - 66b2c338adce ("tap: tap_open(): correctly initialize socket uid"), pass "inode->i_uid" to sock_init_data_uid() as the last parameter and that turns out to be entirely bogus. References: <a href="https://lore.kernel.org/all/20230731164237.48365-1-lersek@redhat.com/">https://lore.kernel.org/all/20230731164237.48365-1-lersek@redhat.com/</a> <a href="https://lore.kernel.org/all/20230731164237.48365-2-lersek@redhat.com/">https://lore.kernel.org/all/20230731164237.48365-2-lersek@redhat.com/</a> <a href="https://lore.kernel.org/all/20230731164237.48365-3-lersek@redhat.com/">https://lore.kernel.org/all/20230731164237.48365-3-lersek@redhat.com/</a>
Credit: secalert@redhat.com secalert@redhat.com secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
Linux Linux kernel | <=6.4 | |
Linux Linux kernel | =6.5-rc1 | |
Linux Linux kernel | =6.5-rc2 | |
Linux Linux kernel | =6.5-rc3 | |
Linux Linux kernel | =6.5-rc4 | |
Redhat Enterprise Linux | =8.0 | |
Redhat Enterprise Linux | =9.0 | |
Fedoraproject Fedora | =37 | |
Fedoraproject Fedora | =38 | |
redhat/kernel | <6.5 | 6.5 |
Debian Debian Linux | =10.0 | |
Debian Debian Linux | =11.0 | |
Debian Debian Linux | =12.0 | |
debian/linux | 5.10.223-1 5.10.226-1 6.1.115-1 6.1.119-1 6.12.5-1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.