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 CVE-2023-1076 was incorrect. The problem is that the following upstream commits (that were fix for the CVE-2023-1076) - 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:https://lore.kernel.org/all/20230731164237.48365-1-lersek@redhat.com/https://lore.kernel.org/all/20230731164237.48365-2-lersek@redhat.com/https://lore.kernel.org/all/20230731164237.48365-3-lersek@redhat.com/
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 CVE-2023-1076 was incorrect. The problem is that the following upstream commits (that were fix for the CVE-2023-1076) - 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:https://lore.kernel.org/all/20230731164237.48365-1-lersek@redhat.com/https://lore.kernel.org/all/20230731164237.48365-2-lersek@redhat.com/https://lore.kernel.org/all/20230731164237.48365-3-lersek@redhat.com/
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 CVE-2023-1076 was incorrect. The problem is that the following upstream commits (that were fix for the CVE-2023-1076) - 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:https://lore.kernel.org/all/20230731164237.48365-1-lersek@redhat.com/https://lore.kernel.org/all/20230731164237.48365-2-lersek@redhat.com/https://lore.kernel.org/all/20230731164237.48365-3-lersek@redhat.com/
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 CVE-2023-1076 was incorrect. The problem is that the following upstream commits (that were fix for the CVE-2023-1076) - 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:https://lore.kernel.org/all/20230731164237.48365-1-lersek@redhat.com/https://lore.kernel.org/all/20230731164237.48365-2-lersek@redhat.com/https://lore.kernel.org/all/20230731164237.48365-3-lersek@redhat.com/
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 CVE-2023-1076 was incorrect. The problem is that the following upstream commits (that were fix for the CVE-2023-1076) - 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:https://lore.kernel.org/all/20230731164237.48365-1-lersek@redhat.com/https://lore.kernel.org/all/20230731164237.48365-2-lersek@redhat.com/https://lore.kernel.org/all/20230731164237.48365-3-lersek@redhat.com/
A flaw found in theLinux Kernel. The tun/tap sockets have their socket UID hardcoded to 0 due toa type confusion in theirinitialization function.While it will be often correct, as tuntap devices require CAP_NET_ADMIN, it maynot always be the case, e.g.,a non-root user only havingthat capability.This would make tun/tap sockets being incorrectly treatedin filtering/routing decisions, possiblybypassingnetwork filters.The original fix for the CVE-2023-1076 was incorrect. The problem is that the following upstreamcommits (that were fix for the CVE-2023-1076) - 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:https://lore.kernel.org/all/20230731164237.48365-1-lersek@redhat.com/https://lore.kernel.org/all/20230731164237.48365-2-lersek@redhat.com/https://lore.kernel.org/all/20230731164237.48365-3-lersek@redhat.com/
A flaw was found inthe Linux kernel s TUN/TAP functionality. This issue could allow a local userto bypass network filtersand gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrector incomplete. The problem isthat the following upstreamcommits - a096ccca6e50 ( tun: tun_chr_open(): correctly initialize socketuid ), - 66b2c338adce ( tap: tap_open():correctlyinitialize socket uid ), pass inode->i_uid to sock_init_data_uid() as the last parameter and that turns out tonot be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
AflawwasfoundintheLinuxkernelsTUN/TAPfunctionality.Thisissuecouldallow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
Aflaw was found in the Linux kernel sTUN/TAP functionality. This issue could allow alocal user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits -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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernels TUN/TAP functionality. This issue could allowa local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits- 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
Aflaw was found in the Linux kernel sTUN/TAP functionality. This issue could allow alocal user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits -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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernels TUN/TAP functionality. This issue could allowa local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits- 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
Aflaw was found in the Linux kernel sTUN/TAP functionality. This issue could allow alocal user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits -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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernels TUN/TAP functionality. This issue could allowa local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits- 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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
Aflaw was found in the Linux kernel sTUN/TAP functionality. This issue could allow alocal user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits -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 not be accurate.
A flaw was found in the Linux kernel s TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - 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 not be accurate.
A flaw was found in the Linux kernels TUN/TAP functionality. This issue could allowa local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits- 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 not be accurate.
