CVE-2025-40051: vhost: vringh: Modify the return value check
In the Linux kernel, the following vulnerability has been resolved:
vhost: vringh: Modify the return value check
The return value of copy_from_iter and copy_to_iter can't be negative,
check whether the copied lengths are equal.
Security readout for executives and security teams
Plain-English summary
CVE-2025-40051 is a high-severity Linux kernel flaw in vhost vringh handling. A local, low-privileged user may trigger incorrect handling of incomplete data copies, potentially compromising confidentiality, integrity, and availability. Exposure depends on the running kernel and whether the affected functionality is reachable.
Executive priority
Treat as a high-priority kernel update, especially on multi-user or virtualization infrastructure. The vulnerability requires local low-privileged access, reducing internet-scale exposure, but the stated impact spans full confidentiality, integrity, and availability. Patch promptly after vendor applicability and operational testing.
Technical view
The vringh code incorrectly evaluated copy_from_iter and copy_to_iter results as potentially negative. These functions return copied lengths, so the correct condition is whether the copied length equals the requested length. The supplied kernel commits change that validation. The bundle does not describe the precise failure mode or demonstrate exploitability.
Likely exposure
Risk is primarily to Linux systems running an affected kernel where vhost vringh functionality is present and reachable by a local low-privileged user. The supplied affected-version data is ambiguous and includes versions from 6.0 through 6.18; confirm exact distribution kernel applicability with vendor guidance.
Exploitation context
The CVSS vector indicates local access, low complexity, low privileges, and no user interaction, with potentially high confidentiality, integrity, and availability impact. The bundle marks this CVE as absent from KEV and provides no evidence of active exploitation or a public exploit.
Researcher notes
The core defect is a return-value semantic mismatch: copied byte counts must be compared with requested lengths. The source bundle supplies five stable-kernel fix commits but no CWE, crash trace, proof of concept, affected configuration details, or exploitation evidence. Version boundaries should not be inferred solely from the flattened version list.
Mitigation direction
Apply the appropriate Linux distribution kernel security update containing the referenced upstream fix.
Check vendor advisories to map distribution kernel builds to the supplied affected versions and commits.
Restrict untrusted local access until affected systems are updated.
Prioritize shared virtualization hosts and other systems where vhost functionality is operationally important.
Validation and detection
Inventory running kernel versions across Linux systems.
Determine whether each kernel contains an applicable referenced fix commit or vendor backport.
Confirm whether vhost vringh functionality is configured, loaded, or reachable by local users.
Verify updated systems are running the new kernel after installation and reboot.
Monitor vendor advisories for clarified affected-version boundaries and exploitation information.
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-40051 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.
1CVSS vectors
3Timeline events
0ADP providers
6Source links
CVSS vector scores
1 official score
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.