CVE-2025-38618

See a problem?
Please try reporting it to the source first.
Source
https://cve.org/CVERecord?id=CVE-2025-38618
Import Source
https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2025-38618.json
JSON Data
https://api.test.osv.dev/v1/vulns/CVE-2025-38618
Downstream
Related
Published
2025-08-22T13:01:24.678Z
Modified
2026-03-11T07:46:32.862239460Z
Summary
vsock: Do not allow binding to VMADDR_PORT_ANY
Details

In the Linux kernel, the following vulnerability has been resolved:

vsock: Do not allow binding to VMADDRPORTANY

It is possible for a vsock to autobind to VMADDRPORTANY. This can cause a use-after-free when a connection is made to the bound socket. The socket returned by accept() also has port VMADDRPORTANY 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 __vsockbindconnectible() to also prevent binding to VMADDRPORTANY.

Database specific 
{
    "cna_assigner": "Linux",
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/38xxx/CVE-2025-38618.json"
}
References

Affected packages

Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

Affected ranges

Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
d021c344051af91f42c5ba9fdedc176740cbd238
Fixed
c04a2c1ca25b9b23104124d3b2d349d934e302de
Fixed
d1a5b1964cef42727668ac0d8532dae4f8c19386
Fixed
cf86704798c1b9c46fa59dfc2d662f57d1394d79
Fixed
f138be5d7f301fddad4e65ec66dfc3ceebf79be3
Fixed
44bd006d5c93f6a8f28b106cbae2428c5d0275b7
Fixed
32950b1907919be86a7a2697d6f93d57068b3865
Fixed
8f01093646b49f6330bb2d36761983fd829472b1
Fixed
d73960f0cf03ef1dc9e96ec7a20e538accc26d87
Fixed
aba0c94f61ec05315fa7815d21aefa4c87f6a9f4

Database specific

source 
"https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2025-38618.json"