From 511e4db270e6de4732be90cf06924163f600505f Mon Sep 17 00:00:00 2001 From: Hyunwoo Kim Date: Mon, 25 Nov 2024 12:38:33 -0300 Subject: [PATCH] vsock/virtio: Initialization of the dangling pointer occurring in vsk->trans During loopback communication, a dangling pointer can be created in vsk->trans, potentially leading to a Use-After-Free condition. This issue is resolved by initializing vsk->trans to NULL. Cc: stable Fixes: 06a8fc78367d ("VSOCK: Introduce virtio_vsock_common.ko") Signed-off-by: Hyunwoo Kim Signed-off-by: Wongi Lee Signed-off-by: Greg Kroah-Hartman Message-Id: <2024102245-strive-crib-c8d3@gregkh> Signed-off-by: Michael S. Tsirkin (cherry picked from commit 6ca575374dd9a507cdd16dfa0e78c2e9e20bd05f) CVE-2024-50264 Signed-off-by: Magali Lemes Acked-by: Massimiliano Pellizzer Acked-by: Yuxuan Luo Signed-off-by: Roxana Nicolescu --- net/vmw_vsock/virtio_transport_common.c | 1 + 1 file changed, 1 insertion(+) diff --git a/net/vmw_vsock/virtio_transport_common.c b/net/vmw_vsock/virtio_transport_common.c index 16ff976a86e3..3b230d142ff3 100644 --- a/net/vmw_vsock/virtio_transport_common.c +++ b/net/vmw_vsock/virtio_transport_common.c @@ -1087,6 +1087,7 @@ void virtio_transport_destruct(struct vsock_sock *vsk) struct virtio_vsock_sock *vvs = vsk->trans; kfree(vvs); + vsk->trans = NULL; } EXPORT_SYMBOL_GPL(virtio_transport_destruct);