diff options
author | 2024-11-06 04:36:04 -0500 | |
---|---|---|
committer | 2024-11-09 09:13:37 -0800 | |
commit | e629295bd60abf4da1db85b82819ca6a4f6c1e79 (patch) | |
tree | 69c941b200dbbe0fabb8aeb94b5c40a07a3e8d1f | |
parent | net: sfc: use ethtool string helpers (diff) | |
download | wireguard-linux-e629295bd60abf4da1db85b82819ca6a4f6c1e79.tar.xz wireguard-linux-e629295bd60abf4da1db85b82819ca6a4f6c1e79.zip |
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: Hyunwoo Kim <v4bel@theori.io>
Reviewed-by: Stefano Garzarella <sgarzare@redhat.com>
Acked-by: Michael S. Tsirkin <mst@redhat.com>
Link: https://patch.msgid.link/Zys4hCj61V+mQfX2@v4bel-B760M-AORUS-ELITE-AX
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
-rw-r--r-- | net/vmw_vsock/hyperv_transport.c | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/net/vmw_vsock/hyperv_transport.c b/net/vmw_vsock/hyperv_transport.c index e2157e387217..56c232cf5b0f 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) |