Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2025-38074vhost-scsi: protect vq->log_used with vq->mutex

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.

Timeline

  1. ID reserved

    By Linux

  2. · 2 months later

    Published

  3. · 14 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-38074, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High8.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.22% · top 88% of all CVEs (19 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.8.

Affected products

  • Linux · Linux

    • affected 057cbf49a1f08297877e46c82f707b1bfea806a8 – < 80cf68489681c165ded460930e391b1eb37b5f6f
    • affected 057cbf49a1f08297877e46c82f707b1bfea806a8 – < 8312a1ccff1566f375191a89b9ba71b6eb48a8cd
    • affected 057cbf49a1f08297877e46c82f707b1bfea806a8 – < 59614c5acf6688f7af3c245d359082c0e9e53117
    • affected 057cbf49a1f08297877e46c82f707b1bfea806a8 – < ca85c2d0db5f8309832be45858b960d933c2131c
    • affected 057cbf49a1f08297877e46c82f707b1bfea806a8 – < bd8c9404e44adb9f6219c09b3409a61ab7ce3427
    • affected 057cbf49a1f08297877e46c82f707b1bfea806a8 – < c0039e3afda29be469d29b3013d7f9bdee136834
    • affected 057cbf49a1f08297877e46c82f707b1bfea806a8 – < f591cf9fce724e5075cc67488c43c6e39e8cbe27
  • Linux · Linux

    • affected 3.6
    • unaffected < 3.6
    • unaffected 5.10.240 – ≤ 5.10.*
    • unaffected 5.15.189 – ≤ 5.15.*
    • unaffected 6.1.146 – ≤ 6.1.*
    • unaffected 6.6.93 – ≤ 6.6.*
    • unaffected 6.12.31 – ≤ 6.12.*
    • unaffected 6.14.9 – ≤ 6.14.*
    • unaffected 6.15 – ≤ *

References

References9

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-38074 badge
[![CVE-2025-38074](https://cveledger.app/badge/CVE-2025-38074.svg)](https://cveledger.app/cve/CVE-2025-38074)

Record last updated .