https://patchthecve.com/CVEs with upgrade or downgrade fix stepshttps://patchthecve.com/cve/CVE-2024-8235.htmlhttps://patchthecve.com/cve/CVE-2024-8235.htmlWed, 17 Jun 2026 08:22:10 +0000MEDIUM 6.2: A flaw was found in libvirt. A refactor of the code fetching the list of interfaces for multiple APIs introduced a corner case on platforms where allocating 0 bytes of memory results in a NULL pointer. This corner case would lead to a NULL-pointer dereference and subsequent crash of virtinterfaced. https://patchthecve.com/cve/CVE-2024-2496.htmlhttps://patchthecve.com/cve/CVE-2024-2496.htmlWed, 17 Jun 2026 07:24:39 +0000MEDIUM 5.0: A NULL pointer dereference flaw was found in the udevConnectListAllInterfaces() function in libvirt. This issue can occur when detaching a host interface while at the same time collecting the list of interfaces via virConnectListAllInterfaces API. This flaw could be used to perform a denial of servihttps://patchthecve.com/cve/CVE-2023-3750.htmlhttps://patchthecve.com/cve/CVE-2023-3750.htmlWed, 17 Jun 2026 06:14:46 +0000MEDIUM 6.5: A 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 crashhttps://patchthecve.com/cve/CVE-2023-2700.htmlhttps://patchthecve.com/cve/CVE-2023-2700.htmlWed, 17 Jun 2026 05:53:13 +0000MEDIUM 5.5: A vulnerability was found in libvirt. This security flaw ouccers due to repeatedly querying an SR-IOV PCI device's capabilities that exposes a memory leak caused by a failure to free the virPCIVirtualFunction array within the parent struct's g_autoptr cleanup.https://patchthecve.com/cve/CVE-2021-3975.htmlhttps://patchthecve.com/cve/CVE-2021-3975.htmlWed, 17 Jun 2026 04:06:19 +0000MEDIUM 6.5: A use-after-free flaw was found in libvirt. The qemuMonitorUnregister() function in qemuProcessHandleMonitorEOF is called using multiple threads without being adequately protected by a monitor lock. This flaw could be triggered by the virConnectGetAllDomainStats API when the guest is shutting down. https://patchthecve.com/cve/CVE-2022-0897.htmlhttps://patchthecve.com/cve/CVE-2022-0897.htmlWed, 17 Jun 2026 04:21:26 +0000MEDIUM 4.3: A flaw was found in the libvirt nwfilter driver. The virNWFilterObjListNumOfNWFilters method failed to acquire the driver->nwfilters mutex before iterating over virNWFilterObj instances. There was no protection to stop another thread from concurrently modifying the driver->nwfilters object. This flahttps://patchthecve.com/cve/CVE-2021-4147.htmlhttps://patchthecve.com/cve/CVE-2021-4147.htmlWed, 17 Jun 2026 04:19:07 +0000MEDIUM 6.5: A flaw was found in the libvirt libxl driver. A malicious guest could continuously reboot itself and cause libvirtd on the host to deadlock or crash, resulting in a denial of service condition.https://patchthecve.com/cve/CVE-2021-3667.htmlhttps://patchthecve.com/cve/CVE-2021-3667.htmlWed, 17 Jun 2026 04:05:32 +0000MEDIUM 6.5: 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 ACLhttps://patchthecve.com/cve/CVE-2021-3631.htmlhttps://patchthecve.com/cve/CVE-2021-3631.htmlWed, 17 Jun 2026 04:05:28 +0000MEDIUM 6.3: A flaw was found in libvirt while it generates SELinux MCS category pairs for VMs' dynamic labels. This flaw allows one exploited guest to access files labeled for another guest, resulting in the breaking out of sVirt confinement. The highest threat from this vulnerability is to confidentiality and https://patchthecve.com/cve/CVE-2020-14301.htmlhttps://patchthecve.com/cve/CVE-2020-14301.htmlWed, 17 Jun 2026 02:54:29 +0000MEDIUM 6.5: An information disclosure vulnerability was found in libvirt in versions before 6.3.0. HTTP cookies used to access network-based disks were saved in the XML dump of the guest domain. This flaw allows an attacker to access potentially sensitive information in the domain configuration via the `dumpxmlhttps://patchthecve.com/cve/CVE-2020-10701.htmlhttps://patchthecve.com/cve/CVE-2020-10701.htmlWed, 17 Jun 2026 02:48:16 +0000MEDIUM 6.5: A missing authorization flaw was found in the libvirt API responsible for changing the QEMU agent response timeout. This flaw allows read-only connections to adjust the time that libvirt waits for the QEMU guest agent to respond to agent commands. Depending on the timeout value that is set, this flahttps://patchthecve.com/cve/CVE-2021-3559.htmlhttps://patchthecve.com/cve/CVE-2021-3559.htmlWed, 17 Jun 2026 04:05:20 +0000MEDIUM 6.5: A flaw was found in libvirt in the virConnectListAllNodeDevices API in versions before 7.0.0. It only affects hosts with a PCI device and driver that supports mediated devices (e.g., GRID driver). This flaw could be used by an unprivileged client with a read-only connection to crash the libvirt daemhttps://patchthecve.com/cve/CVE-2020-14339.htmlhttps://patchthecve.com/cve/CVE-2020-14339.htmlWed, 17 Jun 2026 02:54:33 +0000HIGH 8.8: A flaw was found in libvirt, where it leaked a file descriptor for `/dev/mapper/control` into the QEMU process. This file descriptor allows for privileged operations to happen against the device-mapper on the host. This flaw allows a malicious guest user or process to perform operations outside of thttps://patchthecve.com/cve/CVE-2020-25637.htmlhttps://patchthecve.com/cve/CVE-2020-25637.htmlWed, 17 Jun 2026 03:07:01 +0000MEDIUM 6.7: A double free memory issue was found to occur in the libvirt API, in versions before 6.8.0, responsible for requesting information about network interfaces of a running QEMU domain. This flaw affects the polkit access control driver. Specifically, clients connecting to the read-write socket with limhttps://patchthecve.com/cve/CVE-2020-10703.htmlhttps://patchthecve.com/cve/CVE-2020-10703.htmlWed, 17 Jun 2026 02:48:17 +0000MEDIUM 6.5: A NULL pointer dereference was found in the libvirt API responsible introduced in upstream version 3.10.0, and fixed in libvirt 6.0.0, for fetching a storage pool based on its target path. In more detail, this flaw affects storage pools created without a target path such as network-based pools like https://patchthecve.com/cve/CVE-2020-12430.htmlhttps://patchthecve.com/cve/CVE-2020-12430.htmlWed, 17 Jun 2026 02:51:49 +0000MEDIUM 6.5: An issue was discovered in qemuDomainGetStatsIOThread in qemu/qemu_driver.c in libvirt 4.10.0 though 6.x before 6.1.0. A memory leak was found in the virDomainListGetStats libvirt API that is responsible for retrieving domain statistics when managing QEMU guests. This flaw allows unprivileged users https://patchthecve.com/cve/CVE-2019-20485.htmlhttps://patchthecve.com/cve/CVE-2019-20485.htmlWed, 17 Jun 2026 02:30:33 +0000MEDIUM 5.7: qemu/qemu_driver.c in libvirt before 6.0.0 mishandles the holding of a monitor job during a query to a guest agent, which allows attackers to cause a denial of service (API blockage).https://patchthecve.com/cve/CVE-2019-10168.htmlhttps://patchthecve.com/cve/CVE-2019-10168.htmlWed, 17 Jun 2026 02:10:24 +0000HIGH 7.8: The virConnectBaselineHypervisorCPU() and virConnectCompareHypervisorCPU() libvirt APIs, 4.x.x before 4.10.1 and 5.x.x before 5.4.1, accept an "emulator" argument to specify the program providing emulation for a domain. Since v1.2.19, libvirt will execute that program to probe the domain's capabilithttps://patchthecve.com/cve/CVE-2019-10167.htmlhttps://patchthecve.com/cve/CVE-2019-10167.htmlWed, 17 Jun 2026 02:10:23 +0000HIGH 7.8: The virConnectGetDomainCapabilities() libvirt API, versions 4.x.x before 4.10.1 and 5.x.x before 5.4.1, accepts an "emulatorbin" argument to specify the program providing emulation for a domain. Since v1.2.19, libvirt will execute that program to probe the domain's capabilities. Read-only clients cohttps://patchthecve.com/cve/CVE-2019-10166.htmlhttps://patchthecve.com/cve/CVE-2019-10166.htmlWed, 17 Jun 2026 02:10:23 +0000HIGH 7.8: It was discovered that libvirtd, versions 4.x.x before 4.10.1 and 5.x.x before 5.4.1, would permit readonly clients to use the virDomainManagedSaveDefineXML() API, which would permit them to modify managed save state files. If a managed save had already been created by a privileged user, a local atthttps://patchthecve.com/cve/CVE-2019-10161.htmlhttps://patchthecve.com/cve/CVE-2019-10161.htmlWed, 17 Jun 2026 02:10:23 +0000HIGH 7.8: It was discovered that libvirtd before versions 4.10.1 and 5.4.1 would permit read-only clients to use the virDomainSaveImageGetXMLDesc() API, specifying an arbitrary path which would be accessed with the permissions of the libvirtd process. An attacker with access to the libvirtd socket could use thttps://patchthecve.com/cve/CVE-2019-10132.htmlhttps://patchthecve.com/cve/CVE-2019-10132.htmlWed, 17 Jun 2026 02:10:18 +0000HIGH 8.8: A vulnerability was found in libvirt >= 4.1.0 in the virtlockd-admin.socket and virtlogd-admin.socket systemd units. A missing SocketMode configuration parameter allows any user on the host to connect using virtlockd-admin-sock or virtlogd-admin-sock and perform administrative tasks against the virthttps://patchthecve.com/cve/CVE-2016-10746.htmlhttps://patchthecve.com/cve/CVE-2016-10746.htmlWed, 17 Jun 2026 00:40:17 +0000HIGH 7.5: libvirt-domain.c in libvirt before 1.3.1 supports virDomainGetTime API calls by guest agents with an RO connection, even though an RW connection was supposed to be required, a different vulnerability than CVE-2019-3886.https://patchthecve.com/cve/CVE-2019-3886.htmlhttps://patchthecve.com/cve/CVE-2019-3886.htmlWed, 17 Jun 2026 02:35:48 +0000MEDIUM 5.4: An incorrect permissions check was discovered in libvirt 4.8.0 and above. The readonly permission was allowed to invoke APIs depending on the guest agent, which could lead to potentially disclosing unintended information or denial of service by causing libvirt to block.https://patchthecve.com/cve/CVE-2019-3840.htmlhttps://patchthecve.com/cve/CVE-2019-3840.htmlWed, 17 Jun 2026 02:35:42 +0000MEDIUM 5.8: A NULL pointer dereference flaw was discovered in libvirt before version 5.0.0 in the way it gets interface information through the QEMU agent. An attacker in a guest VM can use this flaw to crash libvirtd and cause a denial of service.https://patchthecve.com/cve/CVE-2017-2635.htmlhttps://patchthecve.com/cve/CVE-2017-2635.htmlWed, 17 Jun 2026 01:16:33 +0000HIGH 7.7: A NULL pointer deference flaw was found in the way libvirt from 2.5.0 to 3.0.0 handled empty drives. A remote authenticated attacker could use this flaw to crash libvirtd daemon resulting in denial of service.https://patchthecve.com/cve/CVE-2015-5160.htmlhttps://patchthecve.com/cve/CVE-2015-5160.htmlWed, 17 Jun 2026 00:28:34 +0000MEDIUM 5.5: libvirt before 2.2 includes Ceph credentials on the qemu command line when using RADOS Block Device (aka RBD), which allows local users to obtain sensitive information via a process listing.https://patchthecve.com/cve/CVE-2018-1064.htmlhttps://patchthecve.com/cve/CVE-2018-1064.htmlWed, 17 Jun 2026 01:50:24 +0000HIGH 7.5: libvirt version before 4.2.0-rc1 is vulnerable to a resource exhaustion as a result of an incomplete fix for CVE-2018-5748 that affects QEMU monitor but now also triggered via QEMU guest agent.https://patchthecve.com/cve/CVE-2018-6764.htmlhttps://patchthecve.com/cve/CVE-2018-6764.htmlWed, 17 Jun 2026 02:02:14 +0000HIGH 7.8: util/virlog.c in libvirt does not properly determine the hostname on LXC container startup, which allows local guest OS users to bypass an intended container protection mechanism and execute arbitrary commands via a crafted NSS module.https://patchthecve.com/cve/CVE-2018-5748.htmlhttps://patchthecve.com/cve/CVE-2018-5748.htmlWed, 17 Jun 2026 02:00:42 +0000HIGH 7.5: qemu/qemu_monitor.c in libvirt allows attackers to cause a denial of service (memory consumption) via a large QEMU reply.https://patchthecve.com/cve/CVE-2017-1000256.htmlhttps://patchthecve.com/cve/CVE-2017-1000256.htmlWed, 17 Jun 2026 00:59:00 +0000HIGH 8.1: libvirt version 2.3.0 and later is vulnerable to a bad default configuration of "verify-peer=no" passed to QEMU by libvirt resulting in a failure to validate SSL/TLS certificates by default.