Skip to content

Commit 6ca5753

Browse files
ImV4belmstsirkin
authored andcommitted
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 <stable@kernel.org> Fixes: 06a8fc7 ("VSOCK: Introduce virtio_vsock_common.ko") Signed-off-by: Hyunwoo Kim <v4bel@theori.io> Signed-off-by: Wongi Lee <qwerty@theori.io> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> Message-Id: <2024102245-strive-crib-c8d3@gregkh> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
1 parent 59b723c commit 6ca5753

1 file changed

Lines changed: 1 addition & 0 deletions

File tree

net/vmw_vsock/virtio_transport_common.c

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1109,6 +1109,7 @@ void virtio_transport_destruct(struct vsock_sock *vsk)
11091109
struct virtio_vsock_sock *vvs = vsk->trans;
11101110

11111111
kfree(vvs);
1112+
vsk->trans = NULL;
11121113
}
11131114
EXPORT_SYMBOL_GPL(virtio_transport_destruct);
11141115

0 commit comments

Comments
 (0)