The vulnerability arises when a datagram socket is closed while the vsock vmci_transport_recv_dgram_cb() callback still holds packets on the backlog. The callback may add packets to the socket's backlog, and when the receive queue is cleared, __release_sock() moves packets from the backlog back to the receive queue, resulting in a memory leak. This loss of kernel memory can lead to resource exhaustion, potentially degrading kernel stability or enabling denial‑of‑service conditions. The weakness involved is a memory allocation flaw, manifested as an uncontrolled retention of kernel memory objects.

Linux kernels that include the vmci vsock driver are affected. Affected versions are not specified in the data; any kernel that implements vmci_transport_recv_dgram_cb() without the corrective changes may be vulnerable. The issue is present across all upstream Linux distributions until the patch is applied.

The vulnerability is a kernel-level memory leak that can increase kernel memory usage over time. Exploitation would require an attacker to cause frequent closures of datagram sockets that trigger the callback, such as by opening many vsock connections and closing them. The likely attack vector is inferred to be local or remote through the vsock interface, depending on system configuration. The CVSS score is 3.3, the EPSS score is <1%, and the vulnerability is not listed in the CISA KEV catalog. The risk level remains moderate, with potential for denial of service if the kernel memory is exhausted.