Tracker / CVE-2025-38618
CVE-2025-38618
High 7.8
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 and versions
| debian | debian_linux |
|---|---|
| linux | linux_kernel |
| linux | linux_kernel · 3.9 → 5.4.297 |
| linux | linux_kernel · 5.11 → 5.15.190 |
| linux | linux_kernel · 5.16 → 6.1.148 |
| linux | linux_kernel · 5.5 → 5.10.241 |
| linux | linux_kernel · 6.13 → 6.15.10 |
| linux | linux_kernel · 6.16 → 6.16.1 |
| linux | linux_kernel · 6.2 → 6.6.102 |
| linux | linux_kernel · 6.7 → 6.12.42 |
Analysis
This page is not indexable yet.Until it carries original analysis — what it actually exposes, how to check in two minutes whether a system was touched, what to do if it was — the page stays noindex. The database decides that, not the template.