CVE-2025-38074: vhost-scsi: protect vq->log_used with vq->mutex
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 59614c5acf6688f7af3c245d359082c0e9e53117, 80cf68489681c165ded460930e391b1eb37b5f6f, 8312a1ccff1566f375191a89b9ba71b6eb48a8cd.
- Severity is disputed: the assigning authority (CNA) scores it 8.8, NVD 5.5.
Low priority for now. Upgrade to Linux Linux 59614c5acf6688f7af3c245d359082c0e9e53117, 80cf68489681c165ded460930e391b1eb37b5f6f, 8312a1ccff1566f375191a89b9ba71b6eb48a8cd or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Jun 18, 2025
- Updated
- Aug 5, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- —
Report tools
Action score
22
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CNA vs NVD score
- NVD
- 5.5
- CNA · Linux
- 8.8
- 3.3 point gap
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 3.6affected
- 057cbf49a1f08297877e46c82f707b1bfea806a8 and later · before 80cf68489681c165ded460930e391b1eb37b5f6faffected · git
- 057cbf49a1f08297877e46c82f707b1bfea806a8 and later · before 8312a1ccff1566f375191a89b9ba71b6eb48a8cdaffected · git
- 057cbf49a1f08297877e46c82f707b1bfea806a8 and later · before 59614c5acf6688f7af3c245d359082c0e9e53117affected · git
- 057cbf49a1f08297877e46c82f707b1bfea806a8 and later · before ca85c2d0db5f8309832be45858b960d933c2131caffected · git
- 057cbf49a1f08297877e46c82f707b1bfea806a8 and later · before bd8c9404e44adb9f6219c09b3409a61ab7ce3427affected · git
- 057cbf49a1f08297877e46c82f707b1bfea806a8 and later · before c0039e3afda29be469d29b3013d7f9bdee136834affected · git
- 057cbf49a1f08297877e46c82f707b1bfea806a8 and later · before f591cf9fce724e5075cc67488c43c6e39e8cbe27affected · git
- before 3.6not affected · semver
- 5.10.240 and later · up to and including 5.10.*not affected · semver
Affected versions · NVD (8)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux11.0
- linux linux kernel5.11 and later · before 5.15.189
- linux linux kernel5.16 and later · before 6.1.146
- linux linux kernel6.2 and later · before 6.6.93
- linux linux kernelbefore 5.10.240
- linux linux kernel6.13 and later · before 6.14.9
- linux linux kernel6.7 and later · before 6.12.31
- linux linux kernel6.15
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.147-1 | 6.1.147-1 |
| Debian:13 | linux | before 6.12.32-1 | 6.12.32-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2025-38068Jun 18, 2025 · crypto: lzo - Fix compression buffer overrun31Monitor
- ← EarlierCVE-2025-38070Jun 18, 2025 · ASoC: sma1307: Add NULL check in sma1307_setting_loaded()22Monitor
- Later →CVE-2025-38076Jun 18, 2025 · alloc_tag: allocate percpu counters for module tags dynamically31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 59614c5acf6688f7af3c245d359082c0e9e53117 | Vendor (CNA) |
| Linux Linux | 80cf68489681c165ded460930e391b1eb37b5f6f | Vendor (CNA) |
| Linux Linux | 8312a1ccff1566f375191a89b9ba71b6eb48a8cd | Vendor (CNA) |
| Linux Linux | bd8c9404e44adb9f6219c09b3409a61ab7ce3427 | Vendor (CNA) |
| Linux Linux | c0039e3afda29be469d29b3013d7f9bdee136834 | Vendor (CNA) |
| Linux Linux | ca85c2d0db5f8309832be45858b960d933c2131c | Vendor (CNA) |
| Linux Linux | f591cf9fce724e5075cc67488c43c6e39e8cbe27 | Vendor (CNA) |
| debian:linux | 6.1.147-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (8 more)Show less
- git.kernel.org/stable/c/80cf68489681c165ded460930e391b1eb37b5f6f
- git.kernel.org/stable/c/8312a1ccff1566f375191a89b9ba71b6eb48a8cd
- git.kernel.org/stable/c/bd8c9404e44adb9f6219c09b3409a61ab7ce3427
- git.kernel.org/stable/c/c0039e3afda29be469d29b3013d7f9bdee136834
- git.kernel.org/stable/c/ca85c2d0db5f8309832be45858b960d933c2131c
- git.kernel.org/stable/c/f591cf9fce724e5075cc67488c43c6e39e8cbe27
- lists.debian.org/debian-lts-announce/2025/10/msg00007.html
- lists.debian.org/debian-lts-announce/2025/10/msg00008.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.