[SRU][O/N/J][PATCH 1/1] hv_sock: Initializing vsk->trans to NULL to prevent a dangling pointer

[Bethany Jamison]

From: Hyunwoo Kim <v4bel at theori.io>

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: Hyunwoo Kim <v4bel at theori.io>
Reviewed-by: Stefano Garzarella <sgarzare at redhat.com>
Acked-by: Michael S. Tsirkin <mst at redhat.com>
Link: https://patch.msgid.link/Zys4hCj61V+mQfX2@v4bel-B760M-AORUS-ELITE-AX
Signed-off-by: Jakub Kicinski <kuba at kernel.org>
(cherry picked from commit e629295bd60abf4da1db85b82819ca6a4f6c1e79)
CVE-2024-53103
Signed-off-by: Bethany Jamison <bethany.jamison at canonical.com>
---
 net/vmw_vsock/hyperv_transport.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/net/vmw_vsock/hyperv_transport.c b/net/vmw_vsock/hyperv_transport.c
index e2157e3872177..56c232cf5b0f4 100644
--- a/net/vmw_vsock/hyperv_transport.c
+++ b/net/vmw_vsock/hyperv_transport.c
@@ -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)
-- 
2.43.0