Skip to main content
← All vulnerabilities
CVE-2026-86845

Dpdk: dpdk: guest-triggered use-after-free and type confusion in vhost-crypto session cleanup

Published
Last modified
published
Not listed in CISA KEV
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: partial

Summary

A flaw was found in DPDK lib/vhost vhost-crypto. Session cleanup can leave a stale cached session pointer, and the data path does not check the session type before attaching it, leading to use-after-free or type confusion in the host vhost-crypto backend.

Timeline

  1. CVE published
  2. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  3. Record last updated

Affected versions

  • grout

    Version range not reported

  • openvswitch3.5

    Version range not reported

  • openvswitch3.6

    Version range not reported

  • openvswitch2.11

    Version range not reported

  • openvswitch2.12

    Version range not reported

  • openvswitch2.13

    Version range not reported

  • openvswitch2.15

    Version range not reported

  • openvswitch2.16

    Version range not reported

  • openvswitch2.17

    Version range not reported

  • openvswitch3.1

    Version range not reported

  • grout

    Version range not reported

  • openvswitch2.17

    Version range not reported

  • openvswitch3.0

    Version range not reported

  • openvswitch3.1

    Version range not reported

  • openvswitch3.2

    Version range not reported

  • openvswitch3.3

    Version range not reported

  • openvswitch3.4

    Version range not reported

  • openvswitch3.5

    Version range not reported

  • openvswitch3.6

    Version range not reported

  • dpdk

    Version range not reported

  • dpdk

    Version range not reported

  • dpdk

    Version range not reported

  • openvswitch2.17

    Version range not reported

  • openvswitch3.0

    Version range not reported

  • openvswitch3.1

    Version range not reported

  • openvswitch

    Version range not reported

References 2

access.redhat.com

bugzilla.redhat.com