CVE-2025-38618: vsock: Do not allow binding to VMADDR_PORT_ANY
In the Linux kernel, the following vulnerability has been resolved:
vsock: Do not allow binding to VMADDRPORTANY
It is possible for a vsock to autobind to VMADDRPORTANY. This can cause a use-after-free when a connection is made to the bound socket. The socket returned by accept() also has port VMADDRPORTANY 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 vsockbindconnectible() to also prevent binding to VMADDRPORTANY.
Affected Software
Remediation
Event History
Peer vulnerabilities
Found alongside the following vulnerabilities.
Frequently Asked Questions
What is the severity of CVE-2025-38618?
CVE-2025-38618 has a severity rating based on its potential impact, particularly related to use-after-free vulnerabilities in the Linux kernel.
How do I fix CVE-2025-38618?
To fix CVE-2025-38618, ensure your Linux kernel is updated to a version that addresses this vulnerability.
What systems are affected by CVE-2025-38618?
CVE-2025-38618 affects the Linux kernel and its associated operating systems.
What is the impact of CVE-2025-38618?
The impact of CVE-2025-38618 includes potential use-after-free issues leading to unexpected behavior in applications using vsock.
When was CVE-2025-38618 resolved?
CVE-2025-38618 was resolved in a recent update to the Linux kernel.