Security readout for executives and security teams
Plain-English summary
This is a Linux kernel availability flaw in the VMware VMCI path. A local user or process could trigger a kernel deadlock condition, causing service disruption. The sources do not indicate data theft, privilege escalation, or active exploitation.
Executive priority
Treat as a moderate-priority availability risk. Patch through normal kernel maintenance, with faster handling for critical VMware-hosted Linux workloads that rely on VMCI or vsock.
Technical view
vmci_dispatch_dgs ran as a tasklet and called vmci_read_data, which can sleep through wait_event. Sleeping in atomic context is invalid and may deadlock. The kernel fix replaces tasklet handling with threaded IRQs.
Likely exposure
Exposure is most relevant to Linux systems running affected kernels with the VMCI/vmw_vmci path in use, such as VMware guest environments using VMCI or vsock-related functionality. The CVSS vector requires local privileges.
Exploitation context
The provided sources list KEV as false and provide no evidence of active exploitation. Impact is availability-only under the CVSS vector, with no confidentiality or integrity impact stated.
Researcher notes
Evidence supports a local denial-of-service class issue caused by invalid sleeping in atomic context. The supplied record does not establish remote reachability, privilege escalation, public exploit availability, or a non-patch mitigation.
Mitigation direction
Apply a vendor kernel update containing the referenced VMCI threaded IRQ fix.
Check distro or appliance vendor guidance for exact affected package versions.
Prioritize VMware guest workloads where VMCI or vsock functionality is enabled.
If patching is delayed, request vendor-supported workaround guidance.
Validation and detection
Inventory Linux kernel versions against the affected ranges in the CVE record.
Identify systems loading or using the vmw_vmci driver or VMCI functionality.
Confirm patched kernels include the referenced stable kernel commits.
Review kernel logs for VMCI sleep-in-atomic or deadlock warnings.
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.
cwe · low confidence lookup
CWE-667: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-667 · source CWE mapping
Improper Locking
Improper Locking represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.