Commit e629295b authored by Hyunwoo Kim's avatar Hyunwoo Kim Committed by Jakub Kicinski
Browse files

hv_sock: Initializing vsk->trans to NULL to prevent a dangling pointer 



When hvs is released, there is a possibility that vsk->trans may not
be initialized to NULL, which could lead to a dangling pointer.
This issue is resolved by initializing vsk->trans to NULL.

Signed-off-by: default avatarHyunwoo Kim <v4bel@theori.io>
Reviewed-by: default avatarStefano Garzarella <sgarzare@redhat.com>
Acked-by: default avatarMichael S. Tsirkin <mst@redhat.com>
Link: https://patch.msgid.link/Zys4hCj61V+mQfX2@v4bel-B760M-AORUS-ELITE-AX


Signed-off-by: default avatarJakub Kicinski <kuba@kernel.org>
parent 9dae5921

net/vmw_vsock/hyperv_transport.c

+1 −0
Original line number Diff line number Diff line
@@ -549,6 +549,7 @@ static void hvs_destruct(struct vsock_sock *vsk) 
		vmbus_hvsock_device_unregister(chan);



	kfree(hvs);

	vsk->trans = NULL;

}



static int hvs_dgram_bind(struct vsock_sock *vsk, struct sockaddr_vm *addr)