logo_clicknbuy.png

CVE-2025-38618 – “vsock: VMADDR_PORT_ANY Binding Vulnerability”

The following table lists the changes that have been made to the
CVE-2025-38618 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution
of a vulnerability, and for identifying the most recent changes that may
impact the vulnerability’s severity, exploitability, or other characteristics.

  • New CVE Received
    by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    Aug. 22, 2025

    Action Type Old Value New Value
    Added Description 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.
    Added Reference https://git.kernel.org/stable/c/32950b1907919be86a7a2697d6f93d57068b3865
    Added Reference https://git.kernel.org/stable/c/44bd006d5c93f6a8f28b106cbae2428c5d0275b7
    Added Reference https://git.kernel.org/stable/c/8f01093646b49f6330bb2d36761983fd829472b1
    Added Reference https://git.kernel.org/stable/c/aba0c94f61ec05315fa7815d21aefa4c87f6a9f4
    Added Reference https://git.kernel.org/stable/c/d73960f0cf03ef1dc9e96ec7a20e538accc26d87
    Added Reference https://git.kernel.org/stable/c/f138be5d7f301fddad4e65ec66dfc3ceebf79be3
Share the Post:

Related Posts