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.
Metrics
Affected Vendors & Products
| Source | ID | Title |
|---|---|---|
Debian DLA |
DLA-4327-1 | linux security update |
Debian DLA |
DLA-4328-1 | linux-6.1 security update |
EUVD |
EUVD-2025-26085 | 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. |
Ubuntu USN |
USN-7791-1 | Linux kernel vulnerabilities |
Ubuntu USN |
USN-7792-1 | Linux kernel vulnerabilities |
Ubuntu USN |
USN-7793-1 | Linux kernel vulnerabilities |
Ubuntu USN |
USN-7795-1 | Linux kernel vulnerabilities |
Ubuntu USN |
USN-7796-1 | Linux kernel vulnerabilities |
Ubuntu USN |
USN-7797-1 | Linux kernel vulnerabilities |
Ubuntu USN |
USN-7791-2 | Linux kernel (Real-time) vulnerabilities |
Ubuntu USN |
USN-7798-1 | Linux kernel (Azure) vulnerabilities |
Ubuntu USN |
USN-7792-2 | Linux kernel (Raspberry Pi) vulnerabilities |
Ubuntu USN |
USN-7799-1 | Linux kernel (Real-time) vulnerabilities |
Ubuntu USN |
USN-7800-1 | Linux kernel (Raspberry Pi Real-time) vulnerabilities |
Ubuntu USN |
USN-7793-2 | Linux kernel (Oracle) vulnerabilities |
Ubuntu USN |
USN-7793-3 | Linux kernel (FIPS) vulnerabilities |
Ubuntu USN |
USN-7793-4 | Linux kernel (Real-time) vulnerabilities |
Ubuntu USN |
USN-7801-1 | Linux kernel (HWE) vulnerabilities |
Ubuntu USN |
USN-7795-2 | Linux kernel (FIPS) vulnerabilities |
Ubuntu USN |
USN-7796-2 | Linux kernel (FIPS) vulnerabilities |
Ubuntu USN |
USN-7796-3 | Linux kernel (Azure) vulnerabilities |
Ubuntu USN |
USN-7797-2 | Linux kernel vulnerabilities |
Ubuntu USN |
USN-7791-3 | Linux kernel vulnerabilities |
Ubuntu USN |
USN-7801-2 | Linux kernel (Oracle) vulnerabilities |
Ubuntu USN |
USN-7792-3 | Linux kernel (AWS) vulnerabilities |
Ubuntu USN |
USN-7808-1 | Linux kernel (Azure) vulnerabilities |
Ubuntu USN |
USN-7809-1 | Linux kernel (Azure, N-Series) vulnerabilities |
Ubuntu USN |
USN-7793-5 | Linux kernel (GKE) vulnerabilities |
Ubuntu USN |
USN-7810-1 | Linux kernel (Azure) vulnerabilities |
Ubuntu USN |
USN-7811-1 | Linux kernel (NVIDIA Tegra IGX) vulnerabilities |
Ubuntu USN |
USN-7795-3 | Linux kernel (AWS FIPS) vulnerabilities |
Ubuntu USN |
USN-7819-1 | Linux kernel (Azure) vulnerabilities |
Ubuntu USN |
USN-7796-4 | Linux kernel (Azure FIPS) kernel vulnerabilities |
Ubuntu USN |
USN-7820-1 | Linux kernel (Oracle) vulnerabilities |
Ubuntu USN |
USN-7791-4 | Linux kernel (Oracle) vulnerabilities |
Ubuntu USN |
USN-7821-1 | Linux kernel (Raspberry Pi) vulnerabilities |
Ubuntu USN |
USN-7808-2 | Linux kernel (Azure) vulnerabilities |
Ubuntu USN |
USN-7810-2 | Linux kernel (Azure) vulnerabilities |
Ubuntu USN |
USN-7810-3 | Linux kernel (Azure FIPS) vulnerabilities |
Ubuntu USN |
USN-7801-3 | Linux kernel (Oracle) vulnerabilities |
Ubuntu USN |
USN-7797-3 | Linux kernel (AWS) vulnerabilities |
Ubuntu USN |
USN-7819-2 | Linux kernel (Azure FIPS) vulnerabilities |
Ubuntu USN |
USN-7795-4 | Linux kernel (Oracle) vulnerabilities |
Ubuntu USN |
USN-7854-1 | Linux kernel (KVM) vulnerabilities |
Ubuntu USN |
USN-7795-5 | Linux kernel (Raspberry Pi) vulnerabilities |
Ubuntu USN |
USN-7865-1 | Linux kernel (FIPS) vulnerabilities |
Ubuntu USN |
USN-7875-1 | Linux kernel (Oracle) vulnerabilities |
Ubuntu USN |
USN-7933-1 | Linux kernel (KVM) vulnerabilities |
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Mon, 03 Nov 2025 18:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
Thu, 28 Aug 2025 15:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
Sat, 23 Aug 2025 11:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Linux
Linux linux Kernel |
|
| Vendors & Products |
Linux
Linux linux Kernel |
Sat, 23 Aug 2025 00:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
threat_severity
|
cvssV3_1
|
Fri, 22 Aug 2025 13:30:00 +0000
| Type | Values Removed | Values 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. | |
| Title | vsock: Do not allow binding to VMADDR_PORT_ANY | |
| References |
|
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: Linux
Published:
Updated: 2025-11-03T17:40:30.483Z
Reserved: 2025-04-16T04:51:24.029Z
Link: CVE-2025-38618
No data.
Status : Awaiting Analysis
Published: 2025-08-22T14:15:46.303
Modified: 2025-11-03T18:16:31.970
Link: CVE-2025-38618
OpenCVE Enrichment
Updated: 2025-08-23T10:55:31Z
No weakness.
Debian DLA
EUVD
Ubuntu USN