CVE-2025-38618
Last modified
CVE-2025-38618 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. 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. EPSS estimates a 0.16% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 3.9, < 5.4.297 | — |
| Linux | Linux Kernel | >= 5.5, < 5.10.241 | — |
| Linux | Linux Kernel | >= 5.11, < 5.15.190 | — |
| Linux | Linux Kernel | >= 5.16, < 6.1.148 | — |
| Linux | Linux Kernel | >= 6.2, < 6.6.102 | — |
| Linux | Linux Kernel | >= 6.7, < 6.12.42 | — |
| Linux | Linux Kernel | >= 6.13, < 6.15.10 | — |
| Linux | Linux Kernel | >= 6.16, < 6.16.1 | — |
| Linux | Linux Kernel | 6.17 | Rc1 |
| Debian | Debian Linux | 11.0 | — |
References
- https://lists.debian.org/debian-lts-announce/2025/10/msg00007.htmlThird Party Advisory
- https://lists.debian.org/debian-lts-announce/2025/10/msg00008.htmlThird Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2025-38618?
How severe is CVE-2025-38618?
How do I fix CVE-2025-38618?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2025
- CVE-2025-38612In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38613In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38614In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38615In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38616In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2025-38617In the Linux kernel, the following vulnerability has been re…4.7
- CVE-2025-38619In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-3862Contest Gallery plugin for WordPress is vulnerable to Stored…5.4
- CVE-2025-38620In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-38621In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38622In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38623In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2025-38618?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST