Skip to content

Commit 8b89afe

Browse files
vsock: fix lock inversion in vsock_assign_transport()
jira VULN-80686 cve-bf CVE-2025-38461 commit-author Stefano Garzarella <[email protected]> commit f7c877e Syzbot reported a potential lock inversion deadlock between vsock_register_mutex and sk_lock-AF_VSOCK when vsock_linger() is called. The issue was introduced by commit 687aa0c ("vsock: Fix transport_* TOCTOU") which added vsock_register_mutex locking in vsock_assign_transport() around the transport->release() call, that can call vsock_linger(). vsock_assign_transport() can be called with sk_lock held. vsock_linger() calls sk_wait_event() that temporarily releases and re-acquires sk_lock. During this window, if another thread hold vsock_register_mutex while trying to acquire sk_lock, a circular dependency is created. Fix this by releasing vsock_register_mutex before calling transport->release() and vsock_deassign_transport(). This is safe because we don't need to hold vsock_register_mutex while releasing the old transport, and we ensure the new transport won't disappear by obtaining a module reference first via try_module_get(). Reported-by: [email protected] Tested-by: [email protected] Fixes: 687aa0c ("vsock: Fix transport_* TOCTOU") Cc: [email protected] Cc: [email protected] Signed-off-by: Stefano Garzarella <[email protected]> Link: https://patch.msgid.link/[email protected] Signed-off-by: Paolo Abeni <[email protected]> (cherry picked from commit f7c877e) Signed-off-by: Shreeya Patel <[email protected]>
1 parent 134b9e7 commit 8b89afe

File tree

1 file changed

+14
-14
lines changed

1 file changed

+14
-14
lines changed

net/vmw_vsock/af_vsock.c

Lines changed: 14 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -479,20 +479,9 @@ int vsock_assign_transport(struct vsock_sock *vsk, struct vsock_sock *psk)
479479
goto err;
480480
}
481481

482-
if (vsk->transport) {
483-
if (vsk->transport == new_transport) {
484-
ret = 0;
485-
goto err;
486-
}
487-
488-
/* transport->release() must be called with sock lock acquired.
489-
* This path can only be taken during vsock_connect(), where we
490-
* have already held the sock lock. In the other cases, this
491-
* function is called on a new socket which is not assigned to
492-
* any transport.
493-
*/
494-
vsk->transport->release(vsk);
495-
vsock_deassign_transport(vsk);
482+
if (vsk->transport && vsk->transport == new_transport) {
483+
ret = 0;
484+
goto err;
496485
}
497486

498487
/* We increase the module refcnt to prevent the transport unloading
@@ -509,6 +498,17 @@ int vsock_assign_transport(struct vsock_sock *vsk, struct vsock_sock *psk)
509498
*/
510499
mutex_unlock(&vsock_register_mutex);
511500

501+
if (vsk->transport) {
502+
/* transport->release() must be called with sock lock acquired.
503+
* This path can only be taken during vsock_connect(), where we
504+
* have already held the sock lock. In the other cases, this
505+
* function is called on a new socket which is not assigned to
506+
* any transport.
507+
*/
508+
vsk->transport->release(vsk);
509+
vsock_deassign_transport(vsk);
510+
}
511+
512512
if (sk->sk_type == SOCK_SEQPACKET) {
513513
if (!new_transport->seqpacket_allow ||
514514
!new_transport->seqpacket_allow(remote_cid)) {

0 commit comments

Comments
 (0)