Quick answers
- Is CVE-2026-86567 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-86567 being exploited in the wild.
- How severe is CVE-2026-86567?
- High severity, with a CVSS score of 8.8, published 14 October 2026.
- Which products and versions are affected?
- DPDK DPDK.
- Is there a fix for CVE-2026-86567?
- 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-86567 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-86567?
- Check whether you run DPDK. 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
The VDUSE handler in DPDK lib/vhost does not invalidate vring pointers when the IOTLB (I/O Translation Lookaside Buffer) is invalidated, leading to a use-after-free condition. A guest VM can trigger this flaw through memory hot-remove, balloon inflation, or IOMMU mapping changes. This allows an attacker with low privileges in a guest VM to corrupt host memory, leak sensitive data, or achieve code execution with the impact scope crossing host and guest boundaries.
Affected products
- DPDK DPDK
Timeline
- 2026-10-14: disclosed