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 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.
Security readout for executives and security teams
Plain-English summary
A flaw in Linux virtual-socket handling can trigger use-after-free memory corruption when a connection reaches a socket improperly bound to the automatic-port value. A local, low-privileged attacker could potentially compromise confidentiality, integrity, and availability. The supplied evidence does not establish remote reachability.
Executive priority
Treat as a high-priority kernel update for multi-user, hosting, virtualization, and workload-isolation environments. It is not supported as an internet-remote or actively exploited emergency by the supplied evidence, but successful exploitation could cause complete system impact within the affected host context.
Technical view
Linux vsock allowed binding a connectible socket to VMADDR_PORT_ANY. An accepted socket could retain that port without appearing on the unbound-socket list; rebinding could then cause an extra reference-count decrement and use-after-free. The fix rejects VMADDR_PORT_ANY in __vsock_bind_connectible(). CVSS 3.1 is 7.8 with local attack vector.
Likely exposure
Exposure centers on affected Linux kernels where an attacker has low-privileged local access and can reach the relevant vsock behavior. Virtualized systems using vsock deserve particular review. The supplied version data mixes release numbers and commit identifiers, so administrators should confirm affected and fixed package versions with their Linux distributor.
Exploitation context
The CVSS vector requires local access, low privileges, low complexity, and no user interaction. The source bundle marks this CVE as absent from KEV and provides no evidence of active exploitation or a public exploit.
Researcher notes
The vulnerable lifecycle involves autobinding or binding to VMADDR_PORT_ANY, accepted-socket bookkeeping, and an erroneous additional reference decrement during rebinding. Review backports rather than relying solely on upstream version numbers. The bundle provides no CWE assignment, exploit evidence, or detailed configuration prerequisites.
Mitigation direction
Install a vendor-supported kernel update that includes the VMADDR_PORT_ANY binding fix.
Reboot into the updated kernel when required by the distribution.
Check Linux distributor advisories for exact affected and corrected package versions.
Prioritize updates on systems granting untrusted users or workloads local access.
Validation and detection
Record the running kernel version and compare it with distributor guidance for CVE-2025-38618.
Confirm the installed update contains the referenced upstream vsock fix.
Verify the system booted into the corrected kernel after maintenance.
Review whether local users or workloads can access vsock functionality.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2025-38618 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
2ADP providers
12Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.