Skip to content
Fencer Intel
high 8.8

CVE-2026-86567 json

Dpdk: dpdk: vduse handler fails to invalidate vring pointers when iotlb is invalidated, leading to use-after-unmap

published 28d ago modified 15h ago also EUVD-2026-101505

cvss
8.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 8%
public exploits
0
none known

Summary

A flaw was found in DPDK lib/vhost. The VDUSE handler fails to invalidate vring pointers when the IOTLB is invalidated, leading to use-after-unmap.

Patch / fix

  • Red Hat Red Hat Enterprise Linux 10 2:25.11-2.el10_2, 2:25.11-2.el10_3
  • Red Hat Red Hat Enterprise Linux 8 0:23.11-3.el8_10
  • Red Hat Red Hat Enterprise Linux 9 2:25.11-2.el9_8, 2:25.11-2.el9_9
  • dpdk Debian 13 24.11.8-0+deb13u1
  • dpdk Debian 14 25.11.4-1

debian advisories DEBIAN-CVE-2026-86567

  • dpdk openSUSE Tumbleweed 25.11.4-1.1

opensuse advisories openSUSE-SU-2026:12151-1

  • dpdk AlmaLinux 8 23.11-3.el8_10
  • dpdk-tools AlmaLinux 8 23.11-3.el8_10
  • dpdk AlmaLinux 9 2:25.11-2.el9_8
  • dpdk-tools AlmaLinux 9 2:25.11-2.el9_8
  • dpdk AlmaLinux 10 2:25.11-2.el10_2
  • dpdk-tools AlmaLinux 10 2:25.11-2.el10_2

almalinux advisories ALSA-2026:96083ALSA-2026:94629ALSA-2026:94630

  • dpdk Rocky Linux 9 2:25.11-2.el9_8
  • dpdk Rocky Linux 8 23.11-3.el8_10
  • dpdk Rocky Linux 10 2:25.11-2.el10_2

rocky linux advisories RLSA-2026:98505RLSA-2026:96083RLSA-2026:94630RLSA-2026:94629

  • dpdk Azure Linux 3.0 23.11.8-1

azure linux advisories AZL-108336

Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT

Is CVE-2026-86567 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-86567 updated cvss 8.8

dpdk: dpdk: VDUSE handler fails to invalidate vring pointers when IOTLB is invalidated, leading to use-after-unmap

  • Red Hat Fast Datapath for RHEL 8 openvswitch2.11, openvswitch2.12, openvswitch2.13, openvswitch2.16, openvswitch2.17, openvswitch2.11-test, +17 more
    affected: workaround, no fix planned “No mitigation is currently available.”
  • Red Hat Fast Datapath for RHEL 9 grout, grout-frr, openvswitch3.0, openvswitch3.1, openvswitch3.2, openvswitch3.3, +28 more
    affected: workaround, no fix available, no fix planned “No mitigation is currently available.”
  • Red Hat Fast Datapath for RHEL 10 grout, grout-frr, openvswitch3.5, openvswitch3.6, openvswitch3.5-test, openvswitch3.6-test, +4 more
    affected: workaround, no fix available “No mitigation is currently available.”
  • Red Hat OpenStack Platform 13 (Queens) openvswitch, openvswitch-test, python-openvswitch, openvswitch-ovn-host, openvswitch-ovn-vtep, openvswitch-ovn-common, +1 more
    affected: workaround, no fix planned “No mitigation is currently available.”
  • Red Hat Enterprise Linux AppStream (v. 8) dpdk 23.11-3.el8_10, dpdk-tools 23.11-3.el8_10
    fixed: vendor fix “No mitigation is currently available.” RHSA-2026:96083
  • Red Hat Enterprise Linux AppStream (v. 9) dpdk 25.11-2.el9_8, dpdk 25.11-2.el9_9, dpdk-tools 25.11-2.el9_8, dpdk-tools 25.11-2.el9_9
    fixed: vendor fix “No mitigation is currently available.” RHSA-2026:94629
  • Red Hat Enterprise Linux AppStream (v. 10) dpdk 25.11-2.el10_2, dpdk 25.11-2.el10_3, dpdk-tools 25.11-2.el10_2, dpdk-tools 25.11-2.el10_3
    fixed: vendor fix “No mitigation is currently available.” RHSA-2026:94630
  • Red Hat Enterprise Linux CRB (v. 8) dpdk-devel 23.11-3.el8_10, dpdk-debuginfo 23.11-3.el8_10, dpdk-debugsource 23.11-3.el8_10
    fixed: vendor fix “No mitigation is currently available.” RHSA-2026:96083
show 1 more
  • Red Hat Fast Datapath for RHEL 8 openvswitch3.1, openvswitch2.15, openvswitch3.1-test, openvswitch2.15-test, openvswitch3.1-ipsec, openvswitch2.15-ipsec, +4 more Red Hat OpenShift Container Platform 4 openvswitch3.0, openvswitch3.1, openvswitch2.17, openvswitch3.0-test, openvswitch3.1-test, openvswitch2.17-test, +7 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
27d ago

Exploit prediction

0.19% chance of exploitation in the next 30 days, higher than 8% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 3.1 8.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Affected products

  • Red Hat Red Hat Enterprise Linux 10
  • Red Hat Red Hat Enterprise Linux 8
  • Red Hat Red Hat Enterprise Linux 9
  • Red Hat Fast Datapath for RHEL 10
  • Red Hat Fast Datapath for RHEL 8
  • Red Hat Fast Datapath for RHEL 9
  • Red Hat Red Hat OpenShift Container Platform 4
  • Red Hat Red Hat OpenStack Platform 13 (Queens)

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.