Skip to main content

Linux Kernel CVE-2025-40051

HIGH
2025-10-28 416baaa9-dc9f-4396-8d5f-8c081fb06d67
7.8
CVSS 3.1 · Vendor: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Share

Severity by source

Vendor (416baaa9-dc9f-4396-8d5f-8c081fb06d67) PRIMARY
7.8 HIGH
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI
6.6 MEDIUM

Local access to an active vhost/vringh backend with low privilege (AV:L/PR:L); primary effect is kernel-memory disclosure (C:H) with only minor integrity/availability impact from mishandled short copies.

3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L
4.0 AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:L/SC:N/SI:N/SA:N
SUSE
5.5 MEDIUM
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Red Hat
5.5 MEDIUM
qualitative

Primary rating from Vendor (416baaa9-dc9f-4396-8d5f-8c081fb06d67).

CVSS VectorVendor: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

2
Analysis Generated
Jul 30, 2026 - 07:51 vuln.today
CVE Published
Oct 28, 2025 - 12:15 cve.org
HIGH 7.8

DescriptionCVE.org

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.

AnalysisAI

Improper return-value handling in the Linux kernel's vhost vringh host-side virtqueue library allows a local low-privileged actor (including a malicious or misbehaving guest driving a vhost/vDPA backend) to trigger processing of partially-copied descriptor data, potentially disclosing kernel memory. The vringh code checked copy_from_iter/copy_to_iter results for a negative error that these functions cannot return, so short (incomplete) copies were silently treated as success. No public exploit identified at time of analysis; EPSS is low at 0.20% (10th percentile) and the CVE is not in CISA KEV.

Technical ContextAI

vringh is the kernel's host-side implementation of the VirtIO vring (virtqueue) abstraction, used by vhost and vDPA to move descriptor and buffer data between host and guest memory via iov_iter helpers (copy_from_iter/copy_to_iter). Those helpers return the number of bytes actually copied and never return a negative value, so the original code's test for a negative return could never detect a short copy. The correct check is whether the copied length equals the requested length. The root-cause class is improper validation of a return value / incomplete data handling (no CWE was assigned in the input; conceptually akin to CWE-253 Incorrect Check of Function Return Value and downstream exposure of resource/uninitialized memory).

Affected ProductsAI

The affected component is the Linux kernel vhost vringh subsystem (drivers/vhost/vringh). Exact affected version ranges are not enumerated in the provided data (no CPE strings and no NVD-tagged version boundaries were supplied); the fix is distributed across multiple stable-tree commits referenced at git.kernel.org (78dc7362662fedaa1928fb8e4f27401c8322905d, 82a8d0fda55b35361ee7f35b54fa2b66d7847d2b, baa37b1c7e29546f79c39bef0d18c4edc9f39bb1, cfa0654402c06d086201a9ff167eb95da5844fc3, db042925a5ab7a550b710addeadbf6f72e3a8a4b), indicating backports to several stable branches. Consult your distribution's kernel advisory to map these commits to your kernel version.

RemediationAI

Upstream fix available (multiple stable-tree commits); a released patched tag is not independently confirmed from the provided data - update to the kernel build from your distribution that incorporates the vringh return-value fix (commits 78dc7362, 82a8d0fd, baa37b1c, cfa06544, db042925 at https://git.kernel.org/stable/c/). Because the fix is a small correctness change with no documented feature-level workaround, the primary compensating control until patching is to reduce exposure of the vulnerable code path: avoid loading/using vhost, vringh and vDPA backends on hosts that do not require them (e.g., do not attach untrusted guests to vDPA/vhost devices), and restrict which local users and guests can access /dev/vhost-* and vDPA management interfaces. The trade-off is that disabling vhost/vDPA degrades para-virtualized I/O performance for VMs, so it is only viable where those backends are unused.

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
Container suse/hpc/warewulf4-x86_64/sle-hpc-node:15.6.17.8.134 Image SLES15-SP6 Image SLES15-SP6-BYOS Image SLES15-SP6-BYOS-Azure Image SLES15-SP6-BYOS-EC2 Image SLES15-SP6-BYOS-GCE Image SLES15-SP6-CHOST-BYOS Image SLES15-SP6-CHOST-BYOS-Aliyun Image SLES15-SP6-CHOST-BYOS-Azure Image SLES15-SP6-CHOST-BYOS-EC2 Image SLES15-SP6-CHOST-BYOS-GCE Image SLES15-SP6-CHOST-BYOS-GDC Image SLES15-SP6-CHOST-BYOS-SAP-CCloud Image SLES15-SP6-EC2 Image SLES15-SP6-EC2-ECS-HVM Image SLES15-SP6-GCE Image SLES15-SP6-HPC-BYOS Image SLES15-SP6-HPC-BYOS-Azure Image SLES15-SP6-HPC-BYOS-EC2 Image SLES15-SP6-HPC-BYOS-GCE Image SLES15-SP6-HPC-EC2 Image SLES15-SP6-HPC-GCE Image SLES15-SP6-Hardened-BYOS Image SLES15-SP6-Hardened-BYOS-Azure Image SLES15-SP6-Hardened-BYOS-EC2 Image SLES15-SP6-Hardened-BYOS-GCE Image SLES15-SP6-SAP Image SLES15-SP6-SAP-Azure Image SLES15-SP6-SAP-EC2 Image SLES15-SP6-SAP-GCE Image SLES15-SP6-SAPCAL Image SLES15-SP6-SAPCAL-Azure Image SLES15-SP6-SAPCAL-EC2 Image SLES15-SP6-SAPCAL-GCE Affected
Container suse/sl-micro/6.0/baremetal-os-container:latest Container suse/sl-micro/6.0/toolbox:latest Affected
Container suse/sl-micro/6.0/base-os-container:2.1.3-7.65 Image SLE-Micro Image SLE-Micro-Azure Image SLE-Micro-BYOS Image SLE-Micro-BYOS-Azure Image SLE-Micro-BYOS-EC2 Image SLE-Micro-BYOS-GCE Image SLE-Micro-EC2 Image SLE-Micro-GCE Affected
Container suse/sl-micro/6.0/kvm-os-container:2.1.3-6.88 Affected
Container suse/sl-micro/6.0/rt-os-container:2.1.3-7.105 Affected

Share

CVE-2025-40051 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy