CVE-2025-38618: vsock: Do not allow binding to VMADDR_PORT_ANY

Severity: high (CVSS 7.8 v3.1)
Exploited in the wild: not listed in CISA KEV
EPSS: 0.2% probability of exploitation in the next 30 days
Public exploit or detection template: none known
Published: 2025-08-22 · updated 2026-07-30
Weakness: CWE-416

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.

Affected products

Debian Linux: 11.0
Linux kernel: from 3.9 before 5.4.297; from 5.5 before 5.10.241; from 5.11 before 5.15.190; from 5.16 before 6.1.148; from 6.2 before 6.6.102; from 6.7 before 6.12.42 — fixed in 5.10.241, 5.15.190, 5.4.297, 6.1.148, 6.12.42, 6.15.10

How to fix

Upgrade to a fixed version: Linux kernel 5.10.241, 5.15.190, 5.4.297, 6.1.148. Check the vendor advisory for mitigations.

References

Get alerted when CVE-2025-38618 or the next vulnerability affects your stack