Answer in brief
CVE-2025-38074 records a Unknown severity vulnerability in vhost-scsi: protect vq->log_used with vq->mutex. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2025-38074 records a Unknown severity vulnerability in vhost-scsi: protect vq->log_used with vq->mutex. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=057cbf49a1f08297877e46c82f707b1bfea806a8 <80cf68489681c165ded460930e391b1eb37b5f6f || >=057cbf49a1f08297877e46c82f707b1bfea806a8 <8312a1ccff1566f375191a89b9ba71b6eb48a8cd || >=057cbf49a1f08297877e46c82f707b1bfea806a8 <59614c5acf6688f7af3c245d359082c0e9e53117 || >=057cbf49a1f08297877e46c82f707b1bfea806a8 <ca85c2d0db5f8309832be45858b960d933c2131c || >=057cbf49a1f08297877e46c82f707b1bfea806a8 <bd8c9404e44adb9f6219c09b3409a61ab7ce3427 || >=057cbf49a1f08297877e46c82f707b1bfea806a8 <c0039e3afda29be469d29b3013d7f9bdee136834 || >=057cbf49a1f08297877e46c82f707b1bfea806a8 <f591cf9fce724e5075cc67488c43c6e39e8cbe27 | 80cf68489681c165ded460930e391b1eb37b5f6f, 8312a1ccff1566f375191a89b9ba71b6eb48a8cd, 59614c5acf6688f7af3c245d359082c0e9e53117, ca85c2d0db5f8309832be45858b960d933c2131c, bd8c9404e44adb9f6219c09b3409a61ab7ce3427, c0039e3afda29be469d29b3013d7f9bdee136834, f591cf9fce724e5075cc67488c43c6e39e8cbe27 |
| Linux/Linuxgeneric | 3.6 | Not reported |
Published upstream
Jun 18, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=057cbf49a1f08297877e46c82f707b1bfea806a8 <80cf68489681c165ded460930e391b1eb37b5f6f || >=057cbf49a1f08297877e46c82f707b1bfea806a8 <8312a1ccff1566f375191a89b9ba71b6eb48a8cd || >=057cbf49a1f08297877e46c82f707b1bfea806a8 <59614c5acf6688f7af3c245d359082c0e9e53117 || >=057cbf49a1f08297877e46c82f707b1bfea806a8 <ca85c2d0db5f8309832be45858b960d933c2131c || >=057cbf49a1f08297877e46c82f707b1bfea806a8 <bd8c9404e44adb9f6219c09b3409a61ab7ce3427 || >=057cbf49a1f08297877e46c82f707b1bfea806a8 <c0039e3afda29be469d29b3013d7f9bdee136834 || >=057cbf49a1f08297877e46c82f707b1bfea806a8 <f591cf9fce724e5075cc67488c43c6e39e8cbe27 | 80cf68489681c165ded460930e391b1eb37b5f6f, 8312a1ccff1566f375191a89b9ba71b6eb48a8cd, 59614c5acf6688f7af3c245d359082c0e9e53117, ca85c2d0db5f8309832be45858b960d933c2131c, bd8c9404e44adb9f6219c09b3409a61ab7ce3427, c0039e3afda29be469d29b3013d7f9bdee136834, f591cf9fce724e5075cc67488c43c6e39e8cbe27 |
| Linux/Linuxgeneric | 3.6 | Not reported |
Published upstream
Jun 18, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.