The vulnerability involves a double‑free in the TIPC kernel module, where the tipc_msg_validate function can reallocate the socket buffer being validated and subsequently free the old one again during error handling. If validation fails after the reallocation, the original buffer is freed twice, corrupting kernel memory and potentially enabling an attacker to execute arbitrary code in kernel mode.

The flaw affects all Linux kernel builds that contain the unpatched TIPC code, including every distribution that uses a kernel version prior to the commit that resolves the double‑free. Exact affected kernel releases are not listed, but any system that has not applied the kernel patch in the provided commit references is vulnerable.

There is no CVSS score or EPSS data available, and the vulnerability is not in the CISA KEV catalog. Nevertheless, a double‑free in kernel space is a high‑severity issue that can lead to privilege escalation or remote code execution. The likely attack vector is via a crafted TIPC packet sent to a system that actively uses the TIPC protocol; therefore, remote exploitation is considered feasible if the attacker can reach the vulnerable interface.