| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <2025072507-CVE-2025-38461-33b1@gregkh> Date: Fri, 25 Jul 2025 17:28:23 +0200 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: linux-cve-announce@...r.kernel.org Cc: Greg Kroah-Hartman <gregkh@...nel.org> Subject: CVE-2025-38461: vsock: Fix transport_* TOCTOU From: Greg Kroah-Hartman <gregkh@...nel.org> Description =========== In the Linux kernel, the following vulnerability has been resolved: vsock: Fix transport_* TOCTOU Transport assignment may race with module unload. Protect new_transport from becoming a stale pointer. This also takes care of an insecure call in vsock_use_local_transport(); add a lockdep assert. BUG: unable to handle page fault for address: fffffbfff8056000 Oops: Oops: 0000 [#1] SMP KASAN RIP: 0010:vsock_assign_transport+0x366/0x600 Call Trace: vsock_connect+0x59c/0xc40 __sys_connect+0xe8/0x100 __x64_sys_connect+0x6e/0xc0 do_syscall_64+0x92/0x1c0 entry_SYSCALL_64_after_hwframe+0x4b/0x53 The Linux kernel CVE team has assigned CVE-2025-38461 to this issue. Affected and fixed versions =========================== Issue introduced in 5.5 with commit c0cfa2d8a788fcf45df5bf4070ab2474c88d543a and fixed in 5.10.240 with commit 8667e8d0eb46bc54fdae30ba2f4786407d3d88eb Issue introduced in 5.5 with commit c0cfa2d8a788fcf45df5bf4070ab2474c88d543a and fixed in 5.15.189 with commit 36a439049b34cca0b3661276049b84a1f76cc21a Issue introduced in 5.5 with commit c0cfa2d8a788fcf45df5bf4070ab2474c88d543a and fixed in 6.1.146 with commit 9ce53e744f18e73059d3124070e960f3aa9902bf Issue introduced in 5.5 with commit c0cfa2d8a788fcf45df5bf4070ab2474c88d543a and fixed in 6.6.99 with commit 9d24bb6780282b0255b9929abe5e8f98007e2c6e Issue introduced in 5.5 with commit c0cfa2d8a788fcf45df5bf4070ab2474c88d543a and fixed in 6.12.39 with commit ae2c712ba39c7007de63cb0c75b51ce1caaf1da5 Issue introduced in 5.5 with commit c0cfa2d8a788fcf45df5bf4070ab2474c88d543a and fixed in 6.15.7 with commit 7b73bddf54777fb62d4d8c7729d0affe6df04477 Issue introduced in 5.5 with commit c0cfa2d8a788fcf45df5bf4070ab2474c88d543a and fixed in 6.16-rc6 with commit 687aa0c5581b8d4aa87fd92973e4ee576b550cdf Please see https://www.kernel.org for a full list of currently supported kernel versions by the kernel community. Unaffected versions might change over time as fixes are backported to older supported kernel versions. The official CVE entry at https://cve.org/CVERecord/?id=CVE-2025-38461 will be updated if fixes are backported, please check that for the most up to date information about this issue. Affected files ============== The file(s) affected by this issue are: net/vmw_vsock/af_vsock.c Mitigation ========== The Linux kernel CVE team recommends that you update to the latest stable kernel version for this, and many other bugfixes. Individual changes are never tested alone, but rather are part of a larger kernel release. Cherry-picking individual commits is not recommended or supported by the Linux kernel community at all. If however, updating to the latest release is impossible, the individual changes to resolve this issue can be found at these commits: https://git.kernel.org/stable/c/8667e8d0eb46bc54fdae30ba2f4786407d3d88eb https://git.kernel.org/stable/c/36a439049b34cca0b3661276049b84a1f76cc21a https://git.kernel.org/stable/c/9ce53e744f18e73059d3124070e960f3aa9902bf https://git.kernel.org/stable/c/9d24bb6780282b0255b9929abe5e8f98007e2c6e https://git.kernel.org/stable/c/ae2c712ba39c7007de63cb0c75b51ce1caaf1da5 https://git.kernel.org/stable/c/7b73bddf54777fb62d4d8c7729d0affe6df04477 https://git.kernel.org/stable/c/687aa0c5581b8d4aa87fd92973e4ee576b550cdf
Powered by blists - more mailing lists