Security readout for executives and security teams
Plain-English summary
CVE-2023-3750 is a denial-of-service flaw in libvirt. A permitted client using the read-only socket could trigger a race condition that crashes the libvirt daemon, disrupting virtualization management rather than stealing data or changing systems.
Executive priority
Treat this as a moderate availability risk for virtualization infrastructure. It is not described as data theft or privilege escalation, but daemon crashes can disrupt management workflows and should be patched during normal maintenance, sooner for critical hosts.
Technical view
libvirt's virStoragePoolObjListSearch does not return a locked storage pool as expected. That improper locking can race with another thread trying to lock the same object, causing daemon failure. CVSS 3.1 is 6.5: network vector, low complexity, low privileges, availability impact only.
Likely exposure
Exposure is most relevant to Red Hat Enterprise Linux 9 systems running the affected libvirt package. The bundle lists RHEL 6, 7, 8, and RHEL 8 Advanced Virtualization as unaffected.
Exploitation context
The provided sources say clients connecting to the read-only socket could crash the libvirt daemon. KEV status is false, and the bundle does not provide evidence of active exploitation or public weaponization.
Researcher notes
The key issue is CWE-667 improper locking in virStoragePoolObjListSearch. The reported trigger path involves read-only socket clients and concurrent locking of the same storage pool object. Evidence is vendor-centered; the bundle does not include exploit telemetry, proof-of-concept details, or non-Red Hat affected product claims.
Mitigation direction
- Apply Red Hat updates associated with RHSA-2023:6409 for affected RHEL 9 libvirt systems.
- Restrict libvirt read-only socket access to trusted users and services.
- Prioritize systems where virtualization management availability is operationally critical.
- Check Red Hat guidance before applying compensating controls beyond access restriction and patching.
Validation and detection
- Inventory RHEL 9 hosts running libvirt and compare package state against Red Hat guidance.
- Confirm RHSA-2023:6409 or superseding libvirt updates are installed where applicable.
- Verify RHEL 6, 7, and 8 hosts are not incorrectly flagged as affected.
- Review libvirt socket permissions and authorized client access.
- Monitor libvirt daemon crashes or restarts on virtualization hosts.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-667: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2023-3750 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H2.83.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.5MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Source materials
- CVE List V5 sourceCVE List V5
- RHSA-2023:6409CVE reference · vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/security/cve/CVE-2023-3750CVE reference · vdb-entry, x_refsource_REDHAT
- RHBZ#2222210CVE reference · issue-tracking, x_refsource_REDHAT
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/EVK6JKP36CHE7YAFDJNPNLTW4OWJJ7TQ/CVE reference · x_transferred
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Locking
Improper Locking represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.