summaryrefslogtreecommitdiff
path: root/fs/lockd/svcshare.c
diff options
context:
space:
mode:
authorStefan Hajnoczi <stefanha@redhat.com>2018-11-05 10:35:47 +0000
committerMichael S. Tsirkin <mst@redhat.com>2018-12-06 14:28:38 -0500
commit834e772c8db0c6a275d75315d90aba4ebbb1e249 (patch)
tree9883c42fbb27228dacc9685f4e39f077016574a5 /fs/lockd/svcshare.c
parent78b1a52e05c9db11d293342e8d6d8a230a04b4e7 (diff)
vhost/vsock: fix use-after-free in network stack callers
If the network stack calls .send_pkt()/.cancel_pkt() during .release(), a struct vhost_vsock use-after-free is possible. This occurs because .release() does not wait for other CPUs to stop using struct vhost_vsock. Switch to an RCU-enabled hashtable (indexed by guest CID) so that .release() can wait for other CPUs by calling synchronize_rcu(). This also eliminates vhost_vsock_lock acquisition in the data path so it could have a positive effect on performance. This is CVE-2018-14625 "kernel: use-after-free Read in vhost_transport_send_pkt". Cc: stable@vger.kernel.org Reported-and-tested-by: syzbot+bd391451452fb0b93039@syzkaller.appspotmail.com Reported-by: syzbot+e3e074963495f92a89ed@syzkaller.appspotmail.com Reported-by: syzbot+d5a0a170c5069658b141@syzkaller.appspotmail.com Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com> Signed-off-by: Michael S. Tsirkin <mst@redhat.com> Acked-by: Jason Wang <jasowang@redhat.com>
Diffstat (limited to 'fs/lockd/svcshare.c')
0 files changed, 0 insertions, 0 deletions