Review reviewHigh

CVE-2025-38618

Linux Linux, linux kernel, debian linux

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.

CVSS
7.8
EPSS
0.16%
5.95% percentile
CISA KEV
Not listed
Published
2025.08.22
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.16%
Technical severityCVSS 7.8

Vulnerability overview

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 product and versions

Product
Linux Linux, linux kernel, debian linux
Affected versions
>= d021c344051af91f42c5ba9fdedc176740cbd238 < c04a2c1ca25b9b23104124d3b2d349d934e302de, >= d021c344051af91f42c5ba9fdedc176740cbd238 < d1a5b1964cef42727668ac0d8532dae4f8c19386, >= d021c344051af91f42c5ba9fdedc176740cbd238 < cf86704798c1b9c46fa59dfc2d662f57d1394d79, >= d021c344051af91f42c5ba9fdedc176740cbd238 < f138be5d7f301fddad4e65ec66dfc3ceebf79be3, >= d021c344051af91f42c5ba9fdedc176740cbd238 < 44bd006d5c93f6a8f28b106cbae2428c5d0275b7, >= d021c344051af91f42c5ba9fdedc176740cbd238 < 32950b1907919be86a7a2697d6f93d57068b3865, >= d021c344051af91f42c5ba9fdedc176740cbd238 < 8f01093646b49f6330bb2d36761983fd829472b1, >= d021c344051af91f42c5ba9fdedc176740cbd238 < d73960f0cf03ef1dc9e96ec7a20e538accc26d87, >= d021c344051af91f42c5ba9fdedc176740cbd238 < aba0c94f61ec05315fa7815d21aefa4c87f6a9f4, >= 3.9, >= 3.9 < 5.4.297, >= 5.5 < 5.10.241, >= 5.11 < 5.15.190, >= 5.16 < 6.1.148, >= 6.2 < 6.6.102, >= 6.7 < 6.12.42, >= 6.13 < 6.15.10, >= 6.16 < 6.16.1, 6.17, 11.0
Fixed versions
5.4.297, 5.10.241, 5.15.190, 6.1.148, 6.6.102, 6.12.42, 6.15.10, 6.16.1

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, linux kernel, debian linux and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
CWE-416