CVE-2025-38618

Summary

In the Linux kernel, the following vulnerability has been resolved: vsock: Do not allow binding to VMADDR_PORT_ANY It is possible for a vsock to autobind to VMADDR_PORT_ANY. This can cause a use-after-free when a connection is made to the bound socket. The socket returned by accept() also has port VMADDR_PORT_ANY but is not on the list of unbound sockets. Binding it will result in an extra refcount decrement similar to the one fixed in fcdd2242c023 (vsock: Keep the binding until socket destruction). Modify the check in __vsock_bind_connectible() to also prevent binding to VMADDR_PORT_ANY.

Impact & exploitability

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected products we track (2)

Recommendation

Apply the vendor fix promptly. Open any affected product above for its exact safe version.

Official patch: https://git.kernel.org/stable/c/32950b1907919be86a7a2697d6f93d57068b3865 ↗

Additional information

• NVD record
• https://git.kernel.org/stable/c/32950b1907919be86a7a2697d6f93d57068b3865Patch
• https://git.kernel.org/stable/c/44bd006d5c93f6a8f28b106cbae2428c5d0275b7Patch
• https://git.kernel.org/stable/c/8f01093646b49f6330bb2d36761983fd829472b1Patch
• https://git.kernel.org/stable/c/aba0c94f61ec05315fa7815d21aefa4c87f6a9f4Patch
• https://git.kernel.org/stable/c/c04a2c1ca25b9b23104124d3b2d349d934e302dePatch
• https://git.kernel.org/stable/c/cf86704798c1b9c46fa59dfc2d662f57d1394d79Patch
• https://git.kernel.org/stable/c/d1a5b1964cef42727668ac0d8532dae4f8c19386Patch
• https://git.kernel.org/stable/c/d73960f0cf03ef1dc9e96ec7a20e538accc26d87Patch