CVE-2020-10726 [Medium] | Integer Overflow in Data Plane Development Kit

A vulnerability was found in DPDK versions 19.11 and above. A malicious container that has direct access to the vhost-user socket can keep sending VHOST_USER_GET_INFLIGHT_FD messages, causing a resource leak (file descriptors and virtual memory), which may result in a denial of service.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-15	0.11%	0.47%	+0.36%
2	2026-01-03	0.15%	0.11%	-0.04%
3	2025-11-21	—	0.15%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-15

0.11%

0.47%

+0.36%

2026-01-03

0.15%

0.11%

-0.04%

2025-11-21

—

0.15%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
6.0	3.1	MEDIUM	`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:N/I:N/A:H` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:H) They need powerful rights—admin, root, or similar—before this pays off. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:C) Breaking this can reach past the original component and bite other resources—bigger blast radius. Confidentiality (C:N) Doesn’t really leak secrets in a meaningful way. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	1.5	4.0	[email protected]
4.4	3.1	MEDIUM	`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:H) They need powerful rights—admin, root, or similar—before this pays off. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:N) Doesn’t really leak secrets in a meaningful way. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	0.8	3.6	[email protected]
2.1	2.0	LOW	`AV:L/AC:L/Au:N/C:N/I:N/A:P` Click to expand Access vector (AV:L) Requires local access to the target system. Access complexity (AC:L) Exploitation conditions are straightforward and predictable. Authentication (AU:N) No authentication is required. Confidentiality impact (C:N) No confidentiality impact. Integrity impact (I:N) No integrity impact. Availability impact (A:P) Partial availability impact.	3.9	2.9	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

6.0

3.1

MEDIUM

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:N/I:N/A:H Click to expand

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:H): They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:C): Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:N): Doesn’t really leak secrets in a meaningful way.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

1.5

4.0

[email protected]

4.4

3.1

MEDIUM

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H Click to expand

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:H): They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N): Doesn’t really leak secrets in a meaningful way.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

0.8

3.6

[email protected]

2.1

2.0

LOW

AV:L/AC:L/Au:N/C:N/I:N/A:P Click to expand

Access vector (AV:L): Requires local access to the target system.
Access complexity (AC:L): Exploitation conditions are straightforward and predictable.
Authentication (AU:N): No authentication is required.
Confidentiality impact (C:N): No confidentiality impact.
Integrity impact (I:N): No integrity impact.
Availability impact (A:P): Partial availability impact.

3.9

2.9

[email protected]

OS Trackers for CVE-2020-10726

vendor	priority	summary	link
`debian`	not yet assigned	CVE-2020-10726 not yet assigned priority: Debian including 1 source packages (dpdk), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5.	https://security-tracker.debian.org/tracker/CVE-2020-10726
`redhat`	medium	—	https://access.redhat.com/security/cve/CVE-2020-10726
`ubuntu`	medium	CVE-2020-10726 medium priority: Ubuntu including 1 source packages (dpdk), 6 status rows across 6 suites (bionic, eoan, focal, trusty, upstream, xenial): not-affected 3, released 2, DNE 1.	https://ubuntu.com/security/CVE-2020-10726

Affected software / configurations for CVE-2020-10726

Vendor	Product	Version	Raw CPE
dpdk	data_plane_development_kit	<= 19.11	cpe:2.3:a:dpdk:data_plane_development_kit::::::::
fedoraproject	fedora	32	cpe:2.3:o:fedoraproject:fedora:32:::::::*
opensuse	leap	15.1	cpe:2.3:o:opensuse:leap:15.1:::::::*
oracle	enterprise_communications_broker	3.1.0	cpe:2.3:a:oracle:enterprise_communications_broker:3.1.0:::::::*
oracle	enterprise_communications_broker	3.2.0	cpe:2.3:a:oracle:enterprise_communications_broker:3.2.0:::::::*

References for CVE-2020-10726

URL	Tags
http://lists.opensuse.org/opensuse-security-announce/2020-05/msg00045.html	Mailing List Third Party Advisory
https://bugs.dpdk.org/show_bug.cgi?id=271	Issue Tracking Patch Vendor Advisory
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2020-10726	Issue Tracking Third Party Advisory
https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/HRHKFVV4MRWNNJOYQOVP64L4UVWYPEO4/
https://www.openwall.com/lists/oss-security/2020/05/18/2	Mailing List Third Party Advisory
https://www.oracle.com/security-alerts/cpujan2021.html	Patch Third Party Advisory

URL

CVE-2020-10726

Exploit prediction scoring system (EPSS) score for CVE-2020-10726

Common vulnerability scoring system (CVSS) metrics for CVE-2020-10726

Weakness enumeration for CVE-2020-10726

OS Trackers for CVE-2020-10726

Affected software / configurations for CVE-2020-10726

References for CVE-2020-10726