Linux
vsock: Keep the binding until socket destruction
In the Linux kernel, the following vulnerability has been resolved: vsock: Keep the binding until socket destruction Preserve sockets bindings; this includes both resulting from an explicit bind() and those implicitly bound through autobind during connect(). Prevents socket unbinding during a transport reassignment, which fixes a use-after-free: 1. vsock_create() (refcnt=1) calls vsock_insert_unbound() (refcnt=2) 2. transport->release() calls vsock_remove_bound() without checking if sk was bound and moved to bound list (refcnt=1) 3. vsock_bind() assumes sk is in unbound list and before __vsock_insert_bound(vsock_bound_sockets()) calls __vsock_remove_bound() which does: list_del_init(&vsk->bound_table); // nop sock_put(&vsk->sk); // refcnt=0 BUG: KASAN: slab-use-after-free in __vsock_bind+0x62e/0x730 Read of size 4 at addr ffff88816b46a74c by task a.out/2057 dump_stack_lvl+0x68/0x90 print_report+0x174/0x4f6 kasan_report+0xb9/0x190 __vsock_bind+0x62e/0x730 vsock_bind+0x97/0xe0 __sys_bind+0x154/0x1f0 __x64_sys_bind+0x6e/0xb0 do_syscall_64+0x93/0x1b0 entry_SYSCALL_64_after_hwframe+0x76/0x7e Allocated by task 2057: kasan_save_stack+0x1e/0x40 kasan_save_track+0x10/0x30 __kasan_slab_alloc+0x85/0x90 kmem_cache_alloc_noprof+0x131/0x450 sk_prot_alloc+0x5b/0x220 sk_alloc+0x2c/0x870 __vsock_create.constprop.0+0x2e/0xb60 vsock_create+0xe4/0x420 __sock_create+0x241/0x650 __sys_socket+0xf2/0x1a0 __x64_sys_socket+0x6e/0xb0 do_syscall_64+0x93/0x1b0 entry_SYSCALL_64_after_hwframe+0x76/0x7e Freed by task 2057: kasan_save_stack+0x1e/0x40 kasan_save_track+0x10/0x30 kasan_save_free_info+0x37/0x60 __kasan_slab_free+0x4b/0x70 kmem_cache_free+0x1a1/0x590 __sk_destruct+0x388/0x5a0 __vsock_bind+0x5e1/0x730 vsock_bind+0x97/0xe0 __sys_bind+0x154/0x1f0 __x64_sys_bind+0x6e/0xb0 do_syscall_64+0x93/0x1b0 entry_SYSCALL_64_after_hwframe+0x76/0x7e refcount_t: addition on 0; use-after-free. WARNING: CPU: 7 PID: 2057 at lib/refcount.c:25 refcount_warn_saturate+0xce/0x150 RIP: 0010:refcount_warn_saturate+0xce/0x150 __vsock_bind+0x66d/0x730 vsock_bind+0x97/0xe0 __sys_bind+0x154/0x1f0 __x64_sys_bind+0x6e/0xb0 do_syscall_64+0x93/0x1b0 entry_SYSCALL_64_after_hwframe+0x76/0x7e refcount_t: underflow; use-after-free. WARNING: CPU: 7 PID: 2057 at lib/refcount.c:28 refcount_warn_saturate+0xee/0x150 RIP: 0010:refcount_warn_saturate+0xee/0x150 vsock_remove_bound+0x187/0x1e0 __vsock_release+0x383/0x4a0 vsock_release+0x90/0x120 __sock_release+0xa3/0x250 sock_close+0x14/0x20 __fput+0x359/0xa80 task_work_run+0x107/0x1d0 do_exit+0x847/0x2560 do_group_exit+0xb8/0x250 __x64_sys_exit_group+0x3a/0x50 x64_sys_call+0xfec/0x14f0 do_syscall_64+0x93/0x1b0 entry_SYSCALL_64_after_hwframe+0x76/0x7e
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= c0cfa2d8a788fcf45df5bf4070ab2474c88d543a, < e7754d564579a5db9c5c9f74228df5d6dd6f1173
- >= c0cfa2d8a788fcf45df5bf4070ab2474c88d543a, < e48fcb403c2d0e574c19683f09399ab4cf67809c
- >= c0cfa2d8a788fcf45df5bf4070ab2474c88d543a, < 42b33381e5e1f2b967dc4fb4221ddb9aaf10d197
- >= c0cfa2d8a788fcf45df5bf4070ab2474c88d543a, < 3f43540166128951cc1be7ab1ce6b7f05c670d8b
- >= c0cfa2d8a788fcf45df5bf4070ab2474c88d543a, < 645ce25aa0e67895b11d89f27bb86c9d444c40f8
- >= c0cfa2d8a788fcf45df5bf4070ab2474c88d543a, < b1afd40321f1c243cffbcf40ea7ca41aca87fa5e
- >= c0cfa2d8a788fcf45df5bf4070ab2474c88d543a, < fcdd2242c0231032fc84e1404315c245ae56322a
Fixed in e7754d564579a5db9c5c9f74228df5d6dd6f1173, e48fcb403c2d0e574c19683f09399ab4cf67809c, 42b33381e5e1f2b967dc4fb4221ddb9aaf10d197, 3f43540166128951cc1be7ab1ce6b7f05c670d8b, 645ce25aa0e67895b11d89f27bb86c9d444c40f8, b1afd40321f1c243cffbcf40ea7ca41aca87fa5e, fcdd2242c0231032fc84e1404315c245ae56322a
- 5.5
Fixed in 0, 5.10.235, 5.15.179, 6.1.131, 6.6.79, 6.12.16, 6.13.4, 6.14
Mitigation
Upgrade Linux to e7754d564579a5db9c5c9f74228df5d6dd6f1173 or e48fcb403c2d0e574c19683f09399ab4cf67809c or 42b33381e5e1f2b967dc4fb4221ddb9aaf10d197 or 3f43540166128951cc1be7ab1ce6b7f05c670d8b or 645ce25aa0e67895b11d89f27bb86c9d444c40f8 or b1afd40321f1c243cffbcf40ea7ca41aca87fa5e or fcdd2242c0231032fc84e1404315c245ae56322a or later.
Upgrade Linux to 0 or 5.10.235 or 5.15.179 or 6.1.131 or 6.6.79 or 6.12.16 or 6.13.4 or 6.14 or later.
Timeline
Days relative to CVE publicationFirst public PoC 51 days after publication; not in CISA KEV. First PoC: hoefler02/CVE-2025-21756 (created 18 Apr 2025, found by us: backfilled).
PoC repositories
Found on GitHub.2 PoCs · 1 pending · 1 informational · 1 not a PoC
PoCs 2
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| hoefler02/CVE-2025-21756 | 18 Apr 2025 +51 d | 159 | PoC |
| khoatran107/cve-2025-21756 | 26 Jun 2025 +119 d | 9 | PoC |
Pending 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| KuanKuanQAQ/cve-testing | 19 Jun 2025 +112 d | 0 | Pending · repository exceeds size limit |
Informational 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| h3raklez/CVE-2025-21756 | 22 Mar 2026 +1.1 y | 1 | Informational · write-up |
Not a PoC 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| volticks/CVE-2025-21692-poc | 13 Sep 2025 +199 d | 40 | Not a PoC · unrelated |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.