CVE-2025-38074

  1. Yack CVE
  2. Vulnerabilities (CVE)
  3. CVE-2025-38074

5.5 /10

CVSS v3 : MEDIUM

V3 Legend

Vector :

Exploitability : 1.8 / Impact : 3.6

Attack Vector LOCAL

Attack Complexity LOW

Privileges Required LOW

User Interaction NONE

Confidentiality Impact NONE

Integrity Impact NONE

Availability Impact HIGH

Scope UNCHANGED

I

n 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.

References
Link Resource
https://git.kernel.org/stable/c/59614c5acf6688f7af3c245d359082c0e9e53117 Patch
https://git.kernel.org/stable/c/80cf68489681c165ded460930e391b1eb37b5f6f Patch
https://git.kernel.org/stable/c/8312a1ccff1566f375191a89b9ba71b6eb48a8cd Patch
https://git.kernel.org/stable/c/bd8c9404e44adb9f6219c09b3409a61ab7ce3427 Patch
https://git.kernel.org/stable/c/c0039e3afda29be469d29b3013d7f9bdee136834 Patch
https://git.kernel.org/stable/c/ca85c2d0db5f8309832be45858b960d933c2131c Patch
https://git.kernel.org/stable/c/f591cf9fce724e5075cc67488c43c6e39e8cbe27 Patch
https://lists.debian.org/debian-lts-announce/2025/10/msg00007.html Third Party Advisory
https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html Third Party Advisory
Configurations

Configuration 1 (hide)

OR cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.15:rc1:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.15:rc2:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.15:rc3:*:*:*:*:*:*

Configuration 2 (hide)

cpe:2.3:o:debian:debian_linux:11.0:*:*:*:*:*:*:*
History

17 Dec 2025, 18:54

Type Values Removed Values Added
References () https://git.kernel.org/stable/c/59614c5acf6688f7af3c245d359082c0e9e53117 - () https://git.kernel.org/stable/c/59614c5acf6688f7af3c245d359082c0e9e53117 - Patch
References () https://git.kernel.org/stable/c/80cf68489681c165ded460930e391b1eb37b5f6f - () https://git.kernel.org/stable/c/80cf68489681c165ded460930e391b1eb37b5f6f - Patch
References () https://git.kernel.org/stable/c/8312a1ccff1566f375191a89b9ba71b6eb48a8cd - () https://git.kernel.org/stable/c/8312a1ccff1566f375191a89b9ba71b6eb48a8cd - Patch
References () https://git.kernel.org/stable/c/bd8c9404e44adb9f6219c09b3409a61ab7ce3427 - () https://git.kernel.org/stable/c/bd8c9404e44adb9f6219c09b3409a61ab7ce3427 - Patch
References () https://git.kernel.org/stable/c/c0039e3afda29be469d29b3013d7f9bdee136834 - () https://git.kernel.org/stable/c/c0039e3afda29be469d29b3013d7f9bdee136834 - Patch
References () https://git.kernel.org/stable/c/ca85c2d0db5f8309832be45858b960d933c2131c - () https://git.kernel.org/stable/c/ca85c2d0db5f8309832be45858b960d933c2131c - Patch
References () https://git.kernel.org/stable/c/f591cf9fce724e5075cc67488c43c6e39e8cbe27 - () https://git.kernel.org/stable/c/f591cf9fce724e5075cc67488c43c6e39e8cbe27 - Patch
References () https://lists.debian.org/debian-lts-announce/2025/10/msg00007.html - () https://lists.debian.org/debian-lts-announce/2025/10/msg00007.html - Third Party Advisory
References () https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html - () https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html - Third Party Advisory
First Time Linux linux Kernel
Debian
Linux
Debian debian Linux
CVSS v2 : unknown
v3 : unknown 		v2 : unknown
v3 : 5.5
CPE cpe:2.3:o:linux:linux_kernel:6.15:rc3:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.15:rc2:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.15:rc1:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:debian:debian_linux:11.0:*:*:*:*:*:*:*
CWE NVD-CWE-noinfo

03 Nov 2025, 18:16

Type Values Removed Values Added
References
  • () https://lists.debian.org/debian-lts-announce/2025/10/msg00007.html -
  • () https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html -

17 Jul 2025, 17:15

Type Values Removed Values Added
References
  • () https://git.kernel.org/stable/c/59614c5acf6688f7af3c245d359082c0e9e53117 -
  • () https://git.kernel.org/stable/c/80cf68489681c165ded460930e391b1eb37b5f6f -
  • () https://git.kernel.org/stable/c/8312a1ccff1566f375191a89b9ba71b6eb48a8cd -
Summary
  • (es) En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: vhost-scsi: proteger vq->log_used con vq->mutex La ruta de finalización de vhost-scsi puede acceder a vq->log_base cuando vq->log_used ya está configurado como falso. vhost-thread QEMU-thread vhost_scsi_complete_cmd_work() -> vhost_add_used() -> vhost_add_used_n() if (unlikely(vq->log_used)) QEMU deshabilita vq->log_used mediante 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) Suponiendo que el VMM es QEMU. La ruta vq->log_base proviene del espacio de usuario de QEMU y se puede recuperar mediante gfree(). Como resultado, esto provoca escrituras de memoria no válidas en el espacio de usuario de QEMU. La ruta de la cola de control presenta el mismo problema.

18 Jun 2025, 10:15

Type Values Removed Values Added
New CVE
Information

Published : 2025-06-18 10:15

Updated : 2025-12-17 18:54

NVD link : CVE-2025-38074

Mitre link : CVE-2025-38074

CVE.ORG link : CVE-2025-38074

JSON object : View

Products Affected

linux

debian

CWE
NVD-CWE-noinfo