dbcve.org
Data Plane Development KitApplication · Nvidia

CVE-2022-28199

MEDIUM · 6.5 CVSS v3.1 Published 2022-09-01
Fix available
A fix is available. Upgrade to 20.11_5.0.0 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
NVIDIA’s distribution of the Data Plane Development Kit (MLNX_DPDK) contains a vulnerability in the network stack, where error recovery is not handled properly, which can allow a remote attacker to cause denial of service and some impact to data integrity and confidentiality.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

NVIDIA's MLNX_DPDK contains a vulnerability in the network stack where error recovery is not handled properly. A remote attacker can exploit this improper error handling to cause denial of service and achieve limited impact to data integrity and confidentiality.

MitigationApply vendor-provided patches or updates to MLNX_DPDK. If no patch is available, consider network segmentation and limiting DPDK-facing attack surface until remediation is possible.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Data Plane Development KitApplication
Affected:>= 19.11_1.0.0, < 20.11_5.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if MLNX_DPDK is installed
    Check for presence of MLNX_DPDK packages or installation directories on the system. Common locations include /usr/local/dpdk, /opt/mlnx/dpdk, or check installed packages via dpkg/rpm listings for packages containing 'mlnx' or 'dpdk' in the name.
    Affected if MLNX_DPDK is present on the system
  2. Determine the installed MLNX_DPDK version
    Run the version command for MLNX_DPDK if available, such as 'dpdk-version' or check the package metadata via 'dpkg -l' or 'rpm -qi' for the mlnx-dpdk package. Look for version strings in the format like 19.11.x.x or 20.11.x.x.
    Affected if The installed version falls within >= 19.11_1.0.0 and < 20.11_5.0.0
  3. Verify the network stack component is in use
    Check if DPDK-based network applications or services are running. Review running processes that utilize DPDK ports or examine DPDK configuration files (typically in /etc/dpdk or within application directories) to confirm active network interface bindings.
    Affected if DPDK network stack is actively processing network traffic
  4. Confirm DPDK-facing network exposure
    Review network configuration to determine if DPDK ports are exposed to untrusted network segments. Check firewall rules, network bonding configurations, and interface bindings that allow remote access to DPDK-managed interfaces.
    Affected if DPDK interfaces are accessible from network segments beyond the trusted internal network

A system is affected if MLNX_DPDK version is 19.11_1.0.0 or higher but lower than 20.11_5.0.0 and the DPDK network stack is actively processing traffic on exposed network interfaces.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 20.11_5.0.0 or later
Fixed in 20.11_5.0.0
Interim mitigation

Apply vendor-provided patches or updates to MLNX_DPDK. If no patch is available, consider network segmentation and limiting DPDK-facing attack surface until remediation is possible.

Recommended fix Moderate confidence

NVIDIA MLNX_DPDK 20.11_5.0.0 or later stable release

  1. 1. Identify the currently installed DPDK version by checking the MLNX_DPDK package or running 'dpdk-version' if available
  2. 2. Plan an upgrade to version 20.11_5.0.0 or later (e.g., 20.11_5.0.0, 21.x, or latest stable LTS)
  3. 3. Review the DPDK release notes for version 20.11_5.0.0 to understand changes and migration requirements
  4. 4. Back up current DPDK configuration files and application settings
  5. 5. Install the updated MLNX_DPDK package from NVIDIA's official download portal or package repository
  6. 6. Update any application code or scripts that depend on DPDK APIs if breaking changes are noted in release notes
  7. 7. Reconfigure and rebuild applications against the new DPDK version
  8. 8. Test the deployment in a staging environment before production rollout
Caveat DPDK major version upgrades may introduce API/ABI changes requiring application code updates; review release notes for migration guidance

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Data Plane Development Kit Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-28199 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-28199 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data