CVE-2020-10723: Integer Overflow
A memory corruption issue was found in DPDK versions 17.05 and above
Other sources
A vulnerability was found in DPDK through version 18.11, vhostusercheckandallocqueuepair() is used to extract a vring index from a payload. This function validates the index and is called early on in when performing message handling. Most message handlers depend on it correctly validating the vring index. Depending on the message type the vring index is in different parts of the payload. The function contains a switch/case for each type and copies the index. This is stored in a uint16. This index is then validated. Depending on the message, the source index is an unsigned int. If integer truncation occurs (uint->uint16) the top 16 bits of the index are never validated. When they are used later on (e.g. in vhostusersetvringnum() or vhostusersetvringaddr()) it can lead to out of bound indexing. The out of bound indexed data gets written to, and hence this can cause memory corruption.
— Red Hat
Affected Software
Remediation
Patch Available
Patch Available
Patch Available
Event History
Parent advisories
This vulnerability appears in the following advisories.
Frequently Asked Questions
What is CVE-2020-10723?
CVE-2020-10723 is a memory corruption issue found in DPDK versions 17.05 and above.
What causes the memory corruption issue in CVE-2020-10723?
The memory corruption issue in CVE-2020-10723 is caused by an integer truncation on the index of a payload.
Which software versions are affected by CVE-2020-10723?
DPDK versions 17.05 and above are affected by CVE-2020-10723.
How severe is CVE-2020-10723?
CVE-2020-10723 has a severity rating of 6.7, which is considered medium.
How can I fix CVE-2020-10723?
To fix CVE-2020-10723, update DPDK to version 20.02.1 or higher.