diff options
author | Stefano Garzarella <sgarzare@redhat.com> | 2022-02-22 10:47:42 +0100 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2022-02-23 12:32:33 +0000 |
commit | a58da53ffd70294ebea8ecd0eb45fd0d74add9f9 (patch) | |
tree | 674e148b37fbe2fba93917635ed65ad26470ec23 /net | |
parent | 277f2bb14361790a70e4b3c649e794b75a91a597 (diff) | |
download | linux-stable-a58da53ffd70294ebea8ecd0eb45fd0d74add9f9.tar.gz linux-stable-a58da53ffd70294ebea8ecd0eb45fd0d74add9f9.tar.bz2 linux-stable-a58da53ffd70294ebea8ecd0eb45fd0d74add9f9.zip |
vhost/vsock: don't check owner in vhost_vsock_stop() while releasing
vhost_vsock_stop() calls vhost_dev_check_owner() to check the device
ownership. It expects current->mm to be valid.
vhost_vsock_stop() is also called by vhost_vsock_dev_release() when
the user has not done close(), so when we are in do_exit(). In this
case current->mm is invalid and we're releasing the device, so we
should clean it anyway.
Let's check the owner only when vhost_vsock_stop() is called
by an ioctl.
When invoked from release we can not fail so we don't check return
code of vhost_vsock_stop(). We need to stop vsock even if it's not
the owner.
Fixes: 433fc58e6bf2 ("VSOCK: Introduce vhost_vsock.ko")
Cc: stable@vger.kernel.org
Reported-by: syzbot+1e3ea63db39f2b4440e0@syzkaller.appspotmail.com
Reported-and-tested-by: syzbot+3140b17cb44a7b174008@syzkaller.appspotmail.com
Signed-off-by: Stefano Garzarella <sgarzare@redhat.com>
Acked-by: Jason Wang <jasowang@redhat.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net')
0 files changed, 0 insertions, 0 deletions