Based on the description, the vulnerability arises from a race condition in tcp_v6_syn_recv_sock() where the child socket becomes visible in the TCP ehash table before appropriate initialization. The timing issue may allow another CPU to access the socket with an incomplete IPv6 pointer, potentially causing memory corruption or a kernel panic. The primary impact is loss of confidentiality, integrity, and availability due to possible kernel faults.

The affected product is the Linux kernel in all releases that contain the unpatched implementation of tcp_v6_syn_recv_sock(). No specific version range is listed, so any active kernel signed by Linux:Linux is potentially vulnerable.

Based on the description, the likely attack vector involves network-based traffic that triggers a SYN packet to the affected socket, inducing the race condition. The exact exploitation vector is not detailed, and no EPSS or CVSS score is available, so the likelihood of exploitation remains uncertain. However, because the flaw can lead to kernel corruption, the risk of exploitation is considered high in terms of impact, while the likelihood remains uncertain due to lack of publicly reported cases.