Daemon crash via prematurely released storage-pool lock
Published Jul 24, 2023 · Updated Nov 8, 2025
Improper locking in libvirt on Red Hat Enterprise Linux 9 allows remote authenticated users to crash the libvirt daemon via read-only connections. virStoragePoolObjListSearch returns a referenced storage-pool object after VIR_LOCK_GUARD automatically releases its lock, allowing another thread to race the caller's next lock attempt. A client needs read-only API access; exploitation interrupts virtualization management by terminating the daemon, without reported data disclosure or modification.
Summary
What happened
Improper locking in libvirt on Red Hat Enterprise Linux 9 allows remote authenticated users to crash the libvirt daemon via read-only connections. virStoragePoolObjListSearch returns a referenced storage-pool object after VIR_LOCK_GUARD automatically releases its lock, allowing another thread to race the caller's next lock attempt. A client needs read-only API access; exploitation interrupts virtualization management by terminating the daemon, without reported data disclosure or modification.
The record
- CVE
- CVE-2023-3750
- Published
- Jul 24, 2023
- Updated
- Nov 8, 2025
- Vendor
- Red Hat
- Product
- Red Hat Enterprise Linux 9
- Classifications
- CWE-667, T1499.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 24, 2023CVE publishedPublication date reported by the CVE source.
- Nov 8, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo