A flaw was found in dpdk, which allows a malicious primary vhost-user to attach an unexpected number of fds as ancillary data to VHOSTUSERGETINFLIGHTFD / VHOSTUSERSETINFLIGHTFD messages that are not closed by the secondary vhost-user. By sending such messages continuously, the primary vhost-user exhausts available fd in the vhost-user standby process, leading to a denial of service.

An integer underflow in dpdk versions before 18.11.10 and before 19.11.5 in the movedesc function can lead to large amounts of CPU cycles being eaten up in a long running loop. An attacker could cause movedesc to get stuck in a 4,294,967,295-count iteration loop. Depending on how vhostcrypto is being used this could prevent other VMs or network tasks from being serviced by the busy DPDK lcore for an extended period.

A vulnerability was found in DPDK through version 19.11, A malicious container which has direct access to the vhost-user socket can keep sending VHOSTUSERGETINFLIGHTFD messages which may cause leaking resources until resulting a DoS. Leaking resources being both file descriptors and virtual memory.

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 missing validity check of the descriptor address in the function virtiodevrxbatchpacked().

A vulnerability was found in DPDK through version 18.11, The vhost crypto library code contains a post message handler (vhostcryptomsgposthandler) which calls vhostcryptocreatesess() which in turn calls transformcipherparam() depending on the operation type. It is transformcipherparam() that handles the payload data. The payload contains a cipher key length and a static VHOSTUSERCRYPTOMAXCIPHERKEYLENGTH (64) byte key buffer. When transformcipherparam() handles the payload data it does not check to see if the buffer length doesn't exceed VHOSTUSERCRYPTOMAXCIPHERKEYLENGTH. This missing check can cause out of bound reads which could trigger a crash or a potential information leak. Also, the vhost crypto library code contains a post message handler (vhostcryptomsgposthandler) which calls vhostcryptocreatesess() which in turn calls transformchainparam() depending on the operation type. It is transformchainparam() that handles the payload data. The payload contains a cipher key length and a static VHOSTUSERCRYPTOMAXCIPHERKEYLENGTH (64) byte key buffer, it also contains a digest length and a static authentication key buffer (size: VHOSTUSERCRYPTOMAXHMACKEYLENGTH(512)) and authentication key buffer length. None of these length values are validated. Which can lead to reading out of bound.

A memory corruption issue was found in DPDK versions 17.05 and above

A vulnerability was found in DPDK through version 18.11, vhostusersetlogbase() is a message handler that is called to handle the VHOSTUSERSETLOGBASE message. Its payload contains a 64 bit size and offset. Both are added up and used as a size when calling mmap(). There is no integer overflow check. If an integer overflow occurs a smaller memory map would be created than requested. Since the returned mapping is mapped as writable and used for logging, it seems highly likely that memory corruption can occur.

Last updated 18 August 2025