CVE-2026-93683
Dpdk: dpdk: guest-triggered out-of-bounds walk via vhost indirect descriptor length toctou
What happened?
A flaw was found in the DPDK vhost library. When handling a virtio indirect descriptor table, the host reads the table length more than once from guest memory and can allocate a host copy before validating that length. A guest that changes the length between those reads, or that supplies an out-of-range next index on a small host copy in the vDPA relay path, can cause the host vhost process to walk past the validated mapping or heap copy. That can crash or disrupt the vhost process. Out-of-bounds bytes are consumed as descriptor fields for GPA translation and are not returned to the guest as payload. This is a residual issue in the non-contiguous indirect descriptor copy path introduced as part of the CVE-2018-1059 fix.
Affected software and versions
| Software | Version information | Fixed version |
|---|---|---|
| dpdkRed Hat | unaffected: 2:25.11-2.el10_2 to < * | See vendor advisory |
| dpdkRed Hat | unaffected: 2:25.11-2.el9_8 to < * | See vendor advisory |
| openvswitch3.5Red Hat | Default status: affected | See vendor advisory |
| openvswitch3.6Red Hat | Default status: affected | See vendor advisory |
| openvswitch2.11Red Hat | Default status: affected | See vendor advisory |
| openvswitch2.12Red Hat | Default status: affected | See vendor advisory |
| openvswitch2.13Red Hat | Default status: affected | See vendor advisory |
| openvswitch2.15Red Hat | Default status: affected | See vendor advisory |
| openvswitch2.16Red Hat | Default status: affected | See vendor advisory |
| openvswitch2.17Red Hat | Default status: affected | See vendor advisory |
| openvswitch3.1Red Hat | Default status: affected | See vendor advisory |
| openvswitch2.17Red Hat | Default status: affected | See vendor advisory |
| openvswitch3.0Red Hat | Default status: affected | See vendor advisory |
| openvswitch3.1Red Hat | Default status: affected | See vendor advisory |
| openvswitch3.2Red Hat | Default status: affected | See vendor advisory |
| openvswitch3.3Red Hat | Default status: affected | See vendor advisory |
| openvswitch3.4Red Hat | Default status: affected | See vendor advisory |
| openvswitch3.5Red Hat | Default status: affected | See vendor advisory |
| openvswitch3.6Red Hat | Default status: affected | See vendor advisory |
| dpdkRed Hat | Default status: affected | See vendor advisory |
| openvswitch2.17Red Hat | Default status: affected | See vendor advisory |
| openvswitch3.0Red Hat | Default status: affected | See vendor advisory |
| openvswitch3.1Red Hat | Default status: affected | See vendor advisory |
| openvswitchRed Hat | Default status: affected | See vendor advisory |
Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.
Is it being exploited?
This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.
How to respond
- Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
- Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
- Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.