93e47c9b35
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> |
||
---|---|---|
.. | ||
af_vsock.c | ||
af_vsock_tap.c | ||
diag.c | ||
hyperv_transport.c | ||
Kconfig | ||
Makefile | ||
virtio_transport.c | ||
virtio_transport_common.c | ||
vmci_transport.c | ||
vmci_transport.h | ||
vmci_transport_notify.c | ||
vmci_transport_notify.h | ||
vmci_transport_notify_qstate.c | ||
vsock_addr.c | ||
vsock_loopback.c |