LibvirtApplication · Redhat
CVE-2023-3750
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA flaw was found in libvirt. The virStoragePoolObjListSearch function does not return a locked pool as expected, resulting in a race condition and denial of service when attempting to lock the same object from another thread. This issue could allow clients connecting to the read-only socket to crash the libvirt daemon.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe virStoragePoolObjListSearch function in libvirt fails to return a properly locked pool object, creating a race condition where multiple threads can attempt to lock the same storage pool. This allows clients connecting to the read-only socket to trigger a crash in the libvirt daemon due to the concurrent access vulnerability.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
LibvirtApplication
all versions
Enterprise LinuxOperating system
= 9.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed libvirt versionRun `rpm -q libvirt` or `libvirtd --version` to determine the installed libvirt package versionAffected if The installed version falls within 'all versions' for Redhat Libvirt or matches RHEL 9.0 and has not been patched for CVE-2023-3750
-
Verify read-only socket is enabledCheck for the existence of the libvirt read-only socket (commonly /var/run/libvirt/libvirt-sock-ro) or verify configuration in /etc/libvirt/libvirtd.conf for 'listen_addr' or 'unix_sock_ro' settingsAffected if The read-only socket is enabled and accessible, allowing remote or local clients to connect
-
Confirm storage pools are definedRun `virsh pool-list --all` or check for storage pool configuration files in /etc/libvirt/storagepool/Affected if One or more storage pools are defined in the libvirt environment, as the vulnerability lies in the virStoragePoolObjListSearch function handling pool objects
-
Check for active storage pool operationsMonitor for concurrent access patterns to storage pools using `virsh pool-list` or review daemon logs for concurrent pool access attemptsAffected if Multiple threads or clients can simultaneously access storage pool objects, triggering the race condition in the vulnerable code path
A system is affected if it runs an unpatched version of libvirt with an enabled read-only socket and has storage pools defined, allowing concurrent access that could trigger the race condition crash.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply the vendor patch for CVE-2023-3750 which corrects the locking logic in virStoragePoolObjListSearch to properly return locked pool objects, preventing the race condition.
Fix this in Libvirt
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-3750 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-3750 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data