Technical impact
This vulnerability is a race condition (CWE-366) in the Linux kernel versus socket (vsock) subsystem that allows a TCP socket to transition from ESTABLISHED to CLOSING while the connect loop remains active. When an OP_RST arrives concurrently, the socket may be inserted twice into the internal connected_table list, causing a list_add that violates list invariants. This triggers a kernel BUG and results in a crash, effectively rebooting the system. Resetting a socket that is still present in connected_table can lead to memory corruption, as noted in the reported crashes caused by re‑insertion into connected_table.
Affected Systems
All Linux kernel builds that lack the commit(s) referenced in the provided links are vulnerable. Systems using unmodified kernels before the fix are at risk, regardless of distribution, because the issue resides in core kernel code.
Risk and Exploitability
The CVSS score is 7.8, and EPSS score is < 1%; however, the kernel panic is a severe impact. The description indicates that the bug arises during an internal vsock transition triggered by a kernel-space event. Based on this, it is inferred that the vulnerability requires local or privileged execution. The lack of a KEV listing suggests it has not yet been widely exploited, but the potential for catastrophic crash warrants high risk. The potential attack vector is inferred to involve manipulation of versus socket connections to induce the race condition, which would be possible for an attacker with sufficient local control or for an application developer using vsock APIs.
Debian DLA