CVE-2026-86561: Dpdk: dpdk: missing memory size validation before mmap in vhost memory region setup
A flaw was found in DPDK lib/vhost. Memory size is not adequately validated before mmap during vhost memory-region setup, which can lead to a host crash or memory corruption.
Other sources
A flaw was found in DPDK lib/vhost. The vhost-user SETMEMTABLE mmap path does not adequately validate frontend-supplied region size before mapping, which may lead to denial of service in the host vhost backend. Integer-overflow and zero-size-after-align checks are already present; the remaining size check is as reported by the DPDK vhost maintainer.
— Red Hat
Affected Software
Event History
Frequently Asked Questions
Who is exposed to this issue?
Hosts running a DPDK lib/vhost backend that processes vhost-user SET_MEM_TABLE requests are exposed. The impact described is on the host vhost backend, rather than solely on the frontend.
What access does an attacker need to exploit it?
The severity vector indicates local access and low privileges are required, with no user interaction. Exploitation involves supplying a crafted memory-region size through the vhost-user SET_MEM_TABLE path.
What is the likely impact?
A successful exploit may cause a host denial of service through a crash and may result in memory corruption. The provided severity vector indicates availability impact, with no stated confidentiality or integrity impact.
Do existing overflow checks prevent this issue?
No. Integer-overflow and zero-size-after-alignment checks are already present, but they do not cover the remaining missing validation of the frontend-supplied region size before mmap.