CVE-2025-23259: NVIDIA Mellanox DPDK contains a vulnerability in Poll Mode Driver (PMD), where an attacker on a VM in the system might be able to cause info
Noroxi assessment
Priority: Monitor (action score 26/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.29% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: dpdk (Debian:13) 24.11.3-1~deb13u1; dpdk (Debian:14) 24.11.3-1; dpdk (openSUSE:Leap 15.6) 22.11.10-150600.3.15.1.
Low priority for now. Upgrade to dpdk (Debian:13) 24.11.3-1~deb13u1; dpdk (Debian:14) 24.11.3-1; dpdk (openSUSE:Leap 15.6) 22.11.10-150600.3.15.1 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
NVIDIA Mellanox DPDK contains a vulnerability in Poll Mode Driver (PMD), where an attacker on a VM in the system might be able to cause information disclosure and denial of service on the network interface.
- Published
- Sep 4, 2025
- Updated
- Oct 18, 2026
- EPSS
- 0.2% · 22th percentile
- CWE
- CWE-362
Report tools
Action score
26
Monitor
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · nvidia
- 6.5
- 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.
Running WordPress? Scan your site free with WP Lens
Noroxi 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 (nvidia). Independent of NVD's CPE analysis and usually ahead of it.
NVIDIA Mellanox DPDK 20.11
- All versions prior to 20.11_7.8.0 LTSaffected
NVIDIA Mellanox DPDK 22.11
- All versions prior to 22.11_2504.1.0, All versions prior to 22.11_2410 LTS, All versions prior to 22.11_2310 LTSaffected
NVIDIA Upstream DPDK
- All versions prior to 25.07, All versions prior to 24.11.3 LTS, All versions prior to 23.11.5 LTS, All versions prior to 22.11.10 LTSaffected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | dpdk | from 0 | — |
| Debian:13 | dpdk | before 24.11.3-1~deb13u1 | 24.11.3-1~deb13u1 |
| Debian:14 | dpdk | before 24.11.3-1 | 24.11.3-1 |
| openSUSE:Leap 15.6 | dpdk | before 22.11.10-150600.3.15.1 | 22.11.10-150600.3.15.1 |
| openSUSE:Leap 15.6 | dpdk-thunderx | before 22.11.10-150600.3.15.1 | 22.11.10-150600.3.15.1 |
| openSUSE:Leap 15.6 | dpdk22 | before 22.11.10-150500.5.10.1 | 22.11.10-150500.5.10.1 |
| openSUSE:Leap 15.6 | dpdk22-thunderx | before 22.11.10-150500.5.10.1 | 22.11.10-150500.5.10.1 |
| openSUSE:Leap 16.0 | dpdk | before 24.11.4-160000.1.1 | 24.11.4-160000.1.1 |
| SUSE:Linux Enterprise Micro 5.5 | dpdk22 | before 22.11.10-150500.5.10.1 | 22.11.10-150500.5.10.1 |
| SUSE:Linux Enterprise Micro 5.5 | dpdk22-thunderx | before 22.11.10-150500.5.10.1 | 22.11.10-150500.5.10.1 |
| SUSE:Linux Enterprise Module for Server Applications 15 SP6 | dpdk | before 22.11.10-150600.3.15.1 | 22.11.10-150600.3.15.1 |
| SUSE:Linux Enterprise Module for Server Applications 15 SP6 | dpdk-thunderx | before 22.11.10-150600.3.15.1 | 22.11.10-150600.3.15.1 |
| SUSE:Linux Enterprise Module for Server Applications 15 SP7 | dpdk | before 24.11.4-150700.3.6.1 | 24.11.4-150700.3.6.1 |
| SUSE:Linux Enterprise Module for Server Applications 15 SP7 | dpdk-thunderx | before 24.11.4-150700.3.6.1 | 24.11.4-150700.3.6.1 |
| SUSE:Linux Micro 6.0 | dpdk | before 22.11.10-1.1 | 22.11.10-1.1 |
| SUSE:Linux Micro 6.1 | dpdk | before 22.11.10-slfo.1.1_1.1 | 22.11.10-slfo.1.1_1.1 |
| SUSE:Linux Micro 6.2 | dpdk | before 24.11.4-160000.1.1 | 24.11.4-160000.1.1 |
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 |
|---|---|---|
| debian:dpdk | 24.11.3-1~deb13u1 · Debian:13 | Package registry (OSV) |
| opensuse:dpdk | 22.11.10-150600.3.15.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:dpdk-thunderx | 22.11.10-150600.3.15.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:dpdk22 | 22.11.10-150500.5.10.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:dpdk22-thunderx | 22.11.10-150500.5.10.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| suse:dpdk | 22.11.10-150600.3.15.1 · SUSE:Linux Enterprise Module for Server Applications 15 SP6 | Package registry (OSV) |
| suse:dpdk-thunderx | 22.11.10-150600.3.15.1 · SUSE:Linux Enterprise Module for Server Applications 15 SP6 | Package registry (OSV) |
| suse:dpdk22 | 22.11.10-150500.5.10.1 · SUSE:Linux Enterprise Micro 5.5 | Package registry (OSV) |
| suse:dpdk22-thunderx | 22.11.10-150500.5.10.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.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
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.
No nightly-computed relations.
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
- NVIDIA Public Bug BountyIntigriti · paid · up to $15,000
- NVIDIA Vulnerability Disclosure ProgramIntigriti · disclosure only (VDP)
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- low · data can be read
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/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.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.