Quick answers
- Is CVE-2026-86564 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-86564 being exploited in the wild.
- How severe is CVE-2026-86564?
- Low severity, with a CVSS score of 3.3, published 8 September 2026.
- Which products and versions are affected?
- DPDK <unknown>.
- Is there a fix for CVE-2026-86564?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-86564 attacked?
- It is attacked with local access.
- Am I affected by CVE-2026-86564?
- Check whether you run DPDK at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
This is an out-of-bounds read vulnerability (CWE-125) in DPDK's lib/vhost component, specifically in the virtio-net control-queue handler. The flaw stems from missing length validation before reading command_data, allowing an attacker to read memory beyond allocated buffer boundaries. Attack vector is local; a malicious guest with access to the VDUSE virtio-net control virtqueue can trigger this flaw. Successful exploitation causes a host process crash (denial of service), and the out-of-bounds read may also leak sensitive information such as memory addresses. No mitigation is currently available; a patch is expected from the DPDK project.
Affected products
- DPDK DPDK <unknown>
Timeline
- 2026-09-08: disclosed