CVE-2026-86848: Dpdk: dpdk: time-of-check/time-of-use vulnerability allowing guest-triggered out-of-bounds write in vhost-crypto
Noroxi assessment
Priority: Monitor (action score 35/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.10% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: dpdk (AlmaLinux:10) 2:25.11-2.el10_2; dpdk-devel (AlmaLinux:10) 2:25.11-2.el10_2; dpdk-doc (AlmaLinux:10) 2:25.11-2.el10_2.
Low priority for now. Upgrade to dpdk (AlmaLinux:10) 2:25.11-2.el10_2; dpdk-devel (AlmaLinux:10) 2:25.11-2.el10_2; dpdk-doc (AlmaLinux:10) 2:25.11-2.el10_2 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
A flaw was found in DPDK lib/vhost vhost-crypto. The indirect-descriptor snapshot double-fetches a guest descriptor next index, allowing a malicious guest to cause an out-of-bounds access in the host backend.
- Published
- Oct 14, 2026
- Updated
- Nov 11, 2026
- EPSS
- 0.1% · 1th percentile
- CWE
- CWE-367
Report tools
Action score
35
Monitor
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · redhat
- 8.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.
Red Hat Fast Datapath for RHEL 10
- all versionsaffected
- all versionsaffected
- all versionsaffected
Red Hat Fast Datapath for RHEL 8
- all versionsaffected
- all versionsaffected
- all versionsaffected
- all versionsaffected
- all versionsaffected
- all versionsaffected
- all versionsaffected
Red Hat Fast Datapath for RHEL 9
- all versionsaffected
- all versionsaffected
- all versionsaffected
- all versionsaffected
- all versionsaffected
- all versionsaffected
- all versionsaffected
- all versionsaffected
- all versionsaffected
Red Hat Red Hat Enterprise Linux 10
- 2:25.11-2.el10_2 and laternot affected · rpm
- 2:25.11-2.el10_3 and laternot affected · rpm
Red Hat Red Hat Enterprise Linux 8
- 0:23.11-3.el8_10 and laternot affected · rpm
Red Hat Red Hat Enterprise Linux 9
- 2:25.11-2.el9_8 and laternot affected · rpm
- 2:25.11-2.el9_9 and laternot affected · rpm
Red Hat Red Hat OpenShift Container Platform 4
- all versionsunknown
- all versionsunknown
- all versionsunknown
Red Hat Red Hat OpenStack Platform 13 (Queens)
- all versionsaffected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | dpdk | before 2:25.11-2.el10_2 | 2:25.11-2.el10_2 |
| AlmaLinux:10 | dpdk-devel | before 2:25.11-2.el10_2 | 2:25.11-2.el10_2 |
| AlmaLinux:10 | dpdk-doc | before 2:25.11-2.el10_2 | 2:25.11-2.el10_2 |
| AlmaLinux:10 | dpdk-tools | before 2:25.11-2.el10_2 | 2:25.11-2.el10_2 |
| AlmaLinux:8 | dpdk | before 23.11-3.el8_10 | 23.11-3.el8_10 |
| AlmaLinux:8 | dpdk-devel | before 23.11-3.el8_10 | 23.11-3.el8_10 |
| AlmaLinux:8 | dpdk-doc | before 23.11-3.el8_10 | 23.11-3.el8_10 |
| AlmaLinux:8 | dpdk-tools | before 23.11-3.el8_10 | 23.11-3.el8_10 |
| AlmaLinux:9 | dpdk | before 2:25.11-2.el9_8 | 2:25.11-2.el9_8 |
| AlmaLinux:9 | dpdk-devel | before 2:25.11-2.el9_8 | 2:25.11-2.el9_8 |
| AlmaLinux:9 | dpdk-doc | before 2:25.11-2.el9_8 | 2:25.11-2.el9_8 |
| AlmaLinux:9 | dpdk-tools | before 2:25.11-2.el9_8 | 2:25.11-2.el9_8 |
| Debian:12 | dpdk | from 0 | — |
| Debian:13 | dpdk | before 24.11.8-0+deb13u1 | 24.11.8-0+deb13u1 |
| Debian:14 | dpdk | before 25.11.4-1 | 25.11.4-1 |
| openSUSE:Tumbleweed | dpdk | before 25.11.4-1.1 | 25.11.4-1.1 |
| Rocky Linux:10 | dpdk | before 2:25.11-2.el10_2 | 2:25.11-2.el10_2 |
| Rocky Linux:8 | dpdk | before 0:23.11-3.el8_10 | 0:23.11-3.el8_10 |
| Rocky Linux:9 | dpdk | before 2:25.11-2.el9_8 | 2:25.11-2.el9_8 |
| SUSE:Linux Enterprise Micro 5.5 | dpdk22 | before 22.11.11-150500.5.16.1 | 22.11.11-150500.5.16.1 |
| SUSE:Linux Enterprise Micro 5.5 | dpdk22-thunderx | before 22.11.11-150500.5.16.1 | 22.11.11-150500.5.16.1 |
Same product
red hat: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-86567Dpdk: dpdk: vduse handler fails to invalidate vring pointers when iotlb is invalidated, leading to use-after-unmap35Monitor
- CVE-2026-100236Dpdk: dpdk: heap out-of-bounds read/write in gso header copy34Monitor
- CVE-2026-86565Dpdk: dpdk: guest can desynchronize virtqueue size from inflight descriptor table size, causing out-of-bounds write32Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-86846Oct 14, 2026 · Dpdk: dpdk: guest can trigger out-of-bounds write by controlling avail ring index in vhost-crypto26Monitor
- ← EarlierCVE-2026-86847Oct 14, 2026 · Dpdk: dpdk: guest can trigger infinite loop in vhost-crypto writeback chain cleanup26Monitor
- Later →CVE-2026-86849Oct 14, 2026 · Dpdk: dpdk: integer overflow combined with missing validation leads to host buffer overflow in vhost-crypto26Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| almalinux:dpdk | 2:25.11-2.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:dpdk-devel | 2:25.11-2.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:dpdk-doc | 2:25.11-2.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:dpdk-tools | 2:25.11-2.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| debian:dpdk | 24.11.8-0+deb13u1 · Debian:13 | Package registry (OSV) |
| debian:dpdk | 25.11.4-1 · Debian:14 | Package registry (OSV) |
| opensuse:dpdk | 25.11.4-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| rocky linux:dpdk | 2:25.11-2.el9_8 · Rocky Linux:9 | Package registry (OSV) |
| suse:dpdk22 | 22.11.11-150500.5.16.1 · SUSE:Linux Enterprise Micro 5.5 | Package registry (OSV) |
| suse:dpdk22-thunderx | 22.11.11-150500.5.16.1 · SUSE:Linux Enterprise Micro 5.5 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recorded+3 d
- TodayNov 11, 2026+28 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-936830 days apartDpdk: dpdk: guest-triggered out-of-bounds walk via vhost indirect descriptor length toctou25Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-367 · Time-of-check Time-of-use (TOCTOU) Race ConditionCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log
- Fix✗ → ✓
- SSVC exploitation— → none
- Exploit maturity— → none
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.