# CVE-2026-86562: Dpdk: dpdk: control-queue descriptor double-fetch overflows host heap in dpdk vhost (vduse)

> A TOCTOU race condition in DPDK vhost allows heap buffer overflow, potentially enabling code execution or privilege escalation.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Oct 2026
- **Updated:** 20 Oct 2026
- **Also known as:** AZL-108342, DEBIAN-CVE-2026-86562, GHSA-x59g-22jw-gfvw, UBUNTU-CVE-2026-86562

## What is CVE-2026-86562?

CVE-2026-86562 is a high-severity vulnerability in Red Hat Fast Datapath for RHEL 10, published on 14 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A flaw was found in DPDK lib/vhost. A TOCTOU double-fetch of control-queue descriptors allows a heap buffer overflow with attacker-controlled content in the VDUSE control-queue handler.

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

## Which versions are affected by CVE-2026-86562?


## How do I fix CVE-2026-86562?

Apply the vendor's patch.

## Is CVE-2026-86562 being exploited?

There is no known exploitation of CVE-2026-86562 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-86562 and fix it if it is affected.

What it is: CVE-2026-86562 is a high-severity vulnerability in Red Hat Fast Datapath for RHEL 10, published on 14 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-86562 in the wild and no public exploit code.

Affected product: Red Hat Fast Datapath for RHEL 10. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-86562/ (Markdown: https://insights.sbomify.com/CVE-2026-86562/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-86562
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-86562
- OSV: https://osv.dev/vulnerability/CVE-2026-86562

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-86562/
Summaries are generated and may contain mistakes; the official description above is the record.