An improper locking issue was found in the virStoragePoolLookupByTargetPath API of libvirt. It occurs in the storagePoolLookupByTargetPath function where a locked virStoragePoolObj object is not properly released on ACL permission failure. Clients connecting to the read-write socket with limited ACL permissions could use this flaw to acquire the lock and prevent other users from accessing storage pool/volume APIs, resulting in a denial of service condition. The highest threat from this vulnerability is to system availability.
The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.
Link | Tags |
---|---|
https://bugzilla.redhat.com/show_bug.cgi?id=1986094 | issue tracking vendor advisory |
https://libvirt.org/git/?p=libvirt.git%3Ba=commit%3Bh=447f69dec47e1b0bd15ecd7cd49a9fd3b050fb87 | patch |
https://gitlab.com/libvirt/libvirt/-/commit/447f69dec47e1b0bd15ecd7cd49a9fd3b050fb87 | third party advisory patch |
https://security.netapp.com/advisory/ntap-20220331-0005/ | third party advisory |
https://security.gentoo.org/glsa/202210-06 | third party advisory vendor advisory |
https://lists.debian.org/debian-lts-announce/2024/04/msg00000.html | third party advisory mailing list |