In the Linux kernel, the following vulnerability has been resolved:
vsock: Fix transport_* TOCTOU
Transport assignment may race with module unload. Protect new_transport
from becoming a stale pointer.
This also takes care of an insecure call in vsock_use_local_transport();
add a lockdep assert.
BUG: unable to handle page fault for address: fffffbfff8056000
Oops: Oops: 0000 [#1] SMP KASAN
RIP: 0010:vsock_assign_transport+0x366/0x600
Call Trace:
vsock_connect+0x59c/0xc40
__sys_connect+0xe8/0x100
__x64_sys_connect+0x6e/0xc0
do_syscall_64+0x92/0x1c0
entry_SYSCALL_64_after_hwframe+0x4b/0x53
Security readout for executives and security teams
Plain-English summary
A race condition in the Linux kernel's virtual-socket transport handling can leave the kernel using an invalid pointer while a transport module unloads. A local, low-privileged user may be able to trigger memory corruption affecting confidentiality, integrity, or availability, although exploitation requires difficult timing and no active exploitation is established.
Executive priority
Treat as a high-priority kernel maintenance issue on shared or untrusted-compute systems. Internet exposure alone does not make it remotely exploitable. Patch through normal emergency change controls, prioritizing hosts offering local access or tenant workloads; broader fleet remediation can follow risk-based scheduling.
Technical view
CVE-2025-38461 is a time-of-check/time-of-use race in Linux vsock transport assignment. Concurrent module unloading can make new_transport stale before use, producing a KASAN-observed page fault in vsock_assign_transport during connect. The correction protects transport selection and adds a lock-state assertion around local-transport use.
Likely exposure
Exposure is limited to Linux systems running an affected kernel where vsock transports are available and a low-privileged local user can reach the vulnerable path. The supplied version list is ambiguous, so determine status using distribution advisories, kernel changelogs, or presence of the cited stable fix.
Exploitation context
The CVSS vector is local, high-complexity, low-privilege, and requires no user interaction. Successful abuse depends on racing transport assignment against module unloading. The bundle marks KEV false and provides no evidence of public or active exploitation; demonstrated evidence is a kernel crash under KASAN.
Researcher notes
The supplied crash trace supports a stale-pointer failure in vsock_assign_transport, but does not demonstrate controlled exploitation. Assess reachability through socket creation and transport availability without attempting weaponization. The flattened affected-version data is insufficient for precise branch boundaries; use stable commits and distribution package advisories for authoritative backport status.
Mitigation direction
Install the vendor-supported kernel update containing the applicable cited stable fix.
Prioritize multi-user, virtualization, and container hosts where untrusted local workloads can access vsock.
If updating is delayed, consult vendor guidance for supported exposure-reduction measures.
Reboot into the updated kernel and remove superseded vulnerable kernels where operationally appropriate.
Validation and detection
Record the running kernel release and distribution package version on each potentially exposed host.
Compare package status with the applicable distribution advisory and cited stable kernel fix.
Confirm whether vsock transports are enabled, loaded, and accessible to untrusted local users or workloads.
After remediation, verify the updated kernel is running following reboot.
Monitor kernel logs for vsock-related faults, KASAN reports, or unexpected module-unload crashes.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2025-38461 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.