CVE-2025-38074 Details
Description
In the Linux kernel, the following vulnerability has been resolved: vhost-scsi: protect vq->log_used with vq->mutex The vhost-scsi completion path may access vq->log_base when vq->log_used is already set to false. vhost-thread QEMU-thread vhost_scsi_complete_cmd_work() -> vhost_add_used() -> vhost_add_used_n() if (unlikely(vq->log_used)) QEMU disables vq->log_used via VHOST_SET_VRING_ADDR. mutex_lock(&vq->mutex); vq->log_used = false now! mutex_unlock(&vq->mutex); QEMU gfree(vq->log_base) log_used() -> log_write(vq->log_base) Assuming the VMM is QEMU. The vq->log_base is from QEMU userpace and can be reclaimed via gfree(). As a result, this causes invalid memory writes to QEMU userspace. The control queue path has the same issue.
A vulnerability in the Linux kernel's vhost-scsi component has been addressed. The issue arose because the completion path could access the vq->log_base variable when vq->log_used was already set to false. This created a scenario where invalid memory writes could occur to QEMU userspace, potentially leading to memory corruption. The problem was caused by improper synchronization between the logging mechanism and the associated mutex, allowing for unsafe access to user-space memory.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/59614c5acf6688f7af3c245d359082c0e9e53117 | kernel.org | Patch |
| https://git.kernel.org/stable/c/80cf68489681c165ded460930e391b1eb37b5f6f | kernel.org | Patch |
| https://git.kernel.org/stable/c/8312a1ccff1566f375191a89b9ba71b6eb48a8cd | kernel.org | Patch |
| https://git.kernel.org/stable/c/bd8c9404e44adb9f6219c09b3409a61ab7ce3427 | kernel.org | Patch |
| https://git.kernel.org/stable/c/c0039e3afda29be469d29b3013d7f9bdee136834 | kernel.org | Patch |
| https://git.kernel.org/stable/c/ca85c2d0db5f8309832be45858b960d933c2131c | kernel.org | Patch |
| https://git.kernel.org/stable/c/f591cf9fce724e5075cc67488c43c6e39e8cbe27 | kernel.org | Patch |
| https://lists.debian.org/debian-lts-announce/2025/10/msg00007.html | CVE | Third Party Advisory |
| https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html | CVE | Third Party Advisory |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| NVD-CWE-noinfo | Insufficient Information to Classify Weakness | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | < 5.10.240 >= 5.11, < 5.15.189 >= 5.16, < 6.1.146 >= 6.2, < 6.6.93 >= 6.7, < 6.12.31 >= 6.13, < 6.14.9 6.15 rc1 6.15 rc2 6.15 rc3 |
CPE
Remediation
| |
| debian debian linux | 11.0 |
CPE
Remediation
| |
Change History
6 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jul 30, 2026 | CVE Modified | kernel.org |
| Jun 17, 2026 | CVE Modified | kernel.org |
| Dec 17, 2025 | Initial Analysis | [email protected] |
| Nov 3, 2025 | CVE Modified | CVE |
| Jul 17, 2025 | CVE Modified | kernel.org |
| Jun 18, 2025 | New CVE Received | kernel.org |