Hyunwoo Kim fd8ae34669 vsock/virtio: Initialization of the dangling pointer occurring in vsk->trans ...

commit 6ca575374d 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: 06a8fc7836 ("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>

2024-11-17 14:58:52 +01:00

..

af_vsock_tap.c

…

af_vsock.c

…

diag.c

…

hyperv_transport.c

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

2024-11-17 14:58:52 +01:00

Kconfig

…

Makefile

…

virtio_transport_common.c

vsock/virtio: Initialization of the dangling pointer occurring in vsk->trans

2024-11-17 14:58:52 +01:00

virtio_transport.c

…

vmci_transport_notify_qstate.c

…

vmci_transport_notify.c

…

vmci_transport_notify.h

…

vmci_transport.c

…

vmci_transport.h

…

vsock_addr.c

…