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

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.

Published: 2025-08-22 Last update: 2026-06-17 Assigner: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-38618 is rated Low Risk (33/100): CVSS High severity, with low exploitation likelihood (EPSS 0.15%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-38618

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.02% 0.15% +0.13%
2 2026-01-08 0.06% 0.02% -0.04%
3 2025-12-22 — 0.06% —

Full EPSS history (4 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-38618

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.8 3.1 HIGH
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.8 5.9 [email protected]

Weakness enumeration for CVE-2025-38618

OS Trackers for CVE-2025-38618

vendor priority summary link
debian not yet assigned CVE-2025-38618 not yet assigned priority: Debian including 2 source packages (linux, linux-6.1), 6 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 6. https://security-tracker.debian.org/tracker/CVE-2025-38618
redhat medium — https://access.redhat.com/security/cve/CVE-2025-38618
suse high CVE-2025-38618 severity important: SUSE including 675 source package names (13.2-9.1:libgcrypt20-1.10.3-slfo.1.1_2.1, 13.2-9.1:libip4tc2-1.8.9-4.1, …), 1645 product×package rows across 367 product lines (Container suse/sl-micro/6.0/baremetal-os-container, Container suse/sl-micro/6.0/base-os-container, … (367 product lines)): Fixed 1391, Known Affected 226, First Fixed 22, Known Not Affected 6. https://www.suse.com/security/cve/CVE-2025-38618/
ubuntu medium CVE-2025-38618 medium priority: Ubuntu including 158 source packages (linux, linux-allwinner-5.19, …), 1414 status rows across 9 suites (bionic, focal, jammy, noble, plucky, questing, trusty, upstream, xenial): DNE 1017, released 211, ignored 160, not-affected 23, needs-triage 2, needed 1. https://ubuntu.com/security/CVE-2025-38618

Affected software / configurations for CVE-2025-38618

Vendor Product Version Raw CPE
linux linux_kernel >= 3.9, < 5.4.297 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel >= 5.5, < 5.10.241 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel >= 5.11, < 5.15.190 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel >= 5.16, < 6.1.148 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel >= 6.2, < 6.6.102 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel >= 6.7, < 6.12.42 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel >= 6.13, < 6.15.10 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel >= 6.16, < 6.16.1 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel 6.17 cpe:2.3:o:linux:linux_kernel:6.17:rc1:*:*:*:*:*:*
debian debian_linux 11.0 cpe:2.3:o:debian:debian_linux:11.0:*:*:*:*:*:*:*

References for CVE-2025-38618

URL Tags
https://git.kernel.org/stable/c/32950b1907919be86a7a2697d6f93d57068b3865 Patch
https://git.kernel.org/stable/c/44bd006d5c93f6a8f28b106cbae2428c5d0275b7 Patch
https://git.kernel.org/stable/c/8f01093646b49f6330bb2d36761983fd829472b1 Patch
https://git.kernel.org/stable/c/aba0c94f61ec05315fa7815d21aefa4c87f6a9f4 Patch
https://git.kernel.org/stable/c/c04a2c1ca25b9b23104124d3b2d349d934e302de Patch
https://git.kernel.org/stable/c/cf86704798c1b9c46fa59dfc2d662f57d1394d79 Patch
https://git.kernel.org/stable/c/d1a5b1964cef42727668ac0d8532dae4f8c19386 Patch
https://git.kernel.org/stable/c/d73960f0cf03ef1dc9e96ec7a20e538accc26d87 Patch
https://git.kernel.org/stable/c/f138be5d7f301fddad4e65ec66dfc3ceebf79be3 Patch
https://lists.debian.org/debian-lts-announce/2025/10/msg00007.html Third Party Advisory
https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html Third Party Advisory
cvelogic Threat Intelligence