vsock/virtio: Initialization of the dangling pointer occurring in vsk->trans
commit 6ca575374dd9a507cdd16dfa0e78c2e9e20bd05f upstream. 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: 06a8fc78367d ("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> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
This commit is contained in:
parent
f899a82bdb
commit
93e47c9b35
1 changed files with 1 additions and 0 deletions
|
@ -691,6 +691,7 @@ void virtio_transport_destruct(struct vsock_sock *vsk)
|
||||||
struct virtio_vsock_sock *vvs = vsk->trans;
|
struct virtio_vsock_sock *vvs = vsk->trans;
|
||||||
|
|
||||||
kfree(vvs);
|
kfree(vvs);
|
||||||
|
vsk->trans = NULL;
|
||||||
}
|
}
|
||||||
EXPORT_SYMBOL_GPL(virtio_transport_destruct);
|
EXPORT_SYMBOL_GPL(virtio_transport_destruct);
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue