rpm package
opensuse/dpdk&distro=openSUSE Tumbleweed
pkg:rpm/opensuse/dpdk&distro=openSUSE%20Tumbleweed
Vulnerabilities (9)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2024-11614 | Hig | 7.4 | < 23.11.1-4.1 | 23.11.1-4.1 | Dec 18, 2024 | An out-of-bounds read vulnerability was found in DPDK's Vhost library checksum offload feature. This issue enables an untrusted or compromised guest to crash the hypervisor's vSwitch by forging Virtio descriptors to cause out-of-bounds reads. This flaw allows an attacker with a m | |
| CVE-2020-14374 | — | < 19.11.8-2.7 | 19.11.8-2.7 | Sep 30, 2020 | A flaw was found in dpdk in versions before 18.11.10 and before 19.11.5. A flawed bounds checking in the copy_data function leads to a buffer overflow allowing an attacker in a virtual machine to write arbitrary data to any address in the vhost_crypto application. The highest thr | ||
| CVE-2020-14376 | — | < 19.11.8-2.7 | 19.11.8-2.7 | Sep 30, 2020 | A flaw was found in dpdk in versions before 18.11.10 and before 19.11.5. A lack of bounds checking when copying iv_data from the VM guest memory into host memory can lead to a large buffer overflow. The highest threat from this vulnerability is to data confidentiality and integri | ||
| CVE-2020-14375 | — | < 19.11.8-2.7 | 19.11.8-2.7 | Sep 30, 2020 | A flaw was found in dpdk in versions before 18.11.10 and before 19.11.5. Virtio ring descriptors, and the data they describe are in a region of memory accessible by from both the virtual machine and the host. An attacker in a VM can change the contents of the memory after vhost_c | ||
| CVE-2020-14378 | — | < 19.11.8-2.7 | 19.11.8-2.7 | Sep 30, 2020 | An integer underflow in dpdk versions before 18.11.10 and before 19.11.5 in the `move_desc` function can lead to large amounts of CPU cycles being eaten up in a long running loop. An attacker could cause `move_desc` to get stuck in a 4,294,967,295-count iteration loop. Depending | ||
| CVE-2020-10725 | — | < 19.11.8-2.7 | 19.11.8-2.7 | May 20, 2020 | A flaw was found in DPDK version 19.11 and above that allows a malicious guest to cause a segmentation fault of the vhost-user backend application running on the host, which could result in a loss of connectivity for the other guests running on that host. This is caused by a miss | ||
| CVE-2020-10722 | — | < 19.11.8-2.7 | 19.11.8-2.7 | May 19, 2020 | A vulnerability was found in DPDK versions 18.05 and above. A missing check for an integer overflow in vhost_user_set_log_base() could result in a smaller memory map than requested, possibly allowing memory corruption. | ||
| CVE-2019-14818 | — | < 19.11.8-2.7 | 19.11.8-2.7 | Nov 14, 2019 | A flaw was found in all dpdk version 17.x.x before 17.11.8, 16.x.x before 16.11.10, 18.x.x before 18.11.4 and 19.x.x before 19.08.1 where a malicious master, or a container with access to vhost_user socket, can send specially crafted VRING_SET_NUM messages, resulting in a memory | ||
| CVE-2018-1059 | — | < 19.11.8-2.7 | 19.11.8-2.7 | Apr 24, 2018 | The DPDK vhost-user interface does not check to verify that all the requested guest physical range is mapped and contiguous when performing Guest Physical Addresses to Host Virtual Addresses translations. This may lead to a malicious guest exposing vhost-user backend process memo |
- affected < 23.11.1-4.1fixed 23.11.1-4.1
An out-of-bounds read vulnerability was found in DPDK's Vhost library checksum offload feature. This issue enables an untrusted or compromised guest to crash the hypervisor's vSwitch by forging Virtio descriptors to cause out-of-bounds reads. This flaw allows an attacker with a m
- CVE-2020-14374Sep 30, 2020affected < 19.11.8-2.7fixed 19.11.8-2.7
A flaw was found in dpdk in versions before 18.11.10 and before 19.11.5. A flawed bounds checking in the copy_data function leads to a buffer overflow allowing an attacker in a virtual machine to write arbitrary data to any address in the vhost_crypto application. The highest thr
- CVE-2020-14376Sep 30, 2020affected < 19.11.8-2.7fixed 19.11.8-2.7
A flaw was found in dpdk in versions before 18.11.10 and before 19.11.5. A lack of bounds checking when copying iv_data from the VM guest memory into host memory can lead to a large buffer overflow. The highest threat from this vulnerability is to data confidentiality and integri
- CVE-2020-14375Sep 30, 2020affected < 19.11.8-2.7fixed 19.11.8-2.7
A flaw was found in dpdk in versions before 18.11.10 and before 19.11.5. Virtio ring descriptors, and the data they describe are in a region of memory accessible by from both the virtual machine and the host. An attacker in a VM can change the contents of the memory after vhost_c
- CVE-2020-14378Sep 30, 2020affected < 19.11.8-2.7fixed 19.11.8-2.7
An integer underflow in dpdk versions before 18.11.10 and before 19.11.5 in the `move_desc` function can lead to large amounts of CPU cycles being eaten up in a long running loop. An attacker could cause `move_desc` to get stuck in a 4,294,967,295-count iteration loop. Depending
- CVE-2020-10725May 20, 2020affected < 19.11.8-2.7fixed 19.11.8-2.7
A flaw was found in DPDK version 19.11 and above that allows a malicious guest to cause a segmentation fault of the vhost-user backend application running on the host, which could result in a loss of connectivity for the other guests running on that host. This is caused by a miss
- CVE-2020-10722May 19, 2020affected < 19.11.8-2.7fixed 19.11.8-2.7
A vulnerability was found in DPDK versions 18.05 and above. A missing check for an integer overflow in vhost_user_set_log_base() could result in a smaller memory map than requested, possibly allowing memory corruption.
- CVE-2019-14818Nov 14, 2019affected < 19.11.8-2.7fixed 19.11.8-2.7
A flaw was found in all dpdk version 17.x.x before 17.11.8, 16.x.x before 16.11.10, 18.x.x before 18.11.4 and 19.x.x before 19.08.1 where a malicious master, or a container with access to vhost_user socket, can send specially crafted VRING_SET_NUM messages, resulting in a memory
- CVE-2018-1059Apr 24, 2018affected < 19.11.8-2.7fixed 19.11.8-2.7
The DPDK vhost-user interface does not check to verify that all the requested guest physical range is mapped and contiguous when performing Guest Physical Addresses to Host Virtual Addresses translations. This may lead to a malicious guest exposing vhost-user backend process memo