# CVE-2026-86565: Dpdk: dpdk: guest can desynchronize virtqueue size from inflight descriptor table size, causing out-of-bounds write

> A guest VM can trigger an out-of-bounds write in the host vhost process by desynchronizing virtqueue sizes, potentially leading to code execution or crashes.

- **Severity:** High 8.2 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** AZL-108333, DEBIAN-CVE-2026-86565, GHSA-frh8-6rpp-rx74, UBUNTU-CVE-2026-86565

## What is CVE-2026-86565?

CVE-2026-86565 is a high-severity memory corruption 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 guest can desynchronize virtqueue size from inflight descriptor table size, causing an out-of-bounds write in the host vhost process.

Weakness: CWE-787 (Out-of-bounds Write)

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


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

Apply the vendor's patch.

## Is CVE-2026-86565 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-86565 is a high-severity memory corruption 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-86565 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-86565/ (Markdown: https://insights.sbomify.com/CVE-2026-86565/index.md)
```

## Sources

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

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