Network-interface denial of service via failed mlx5 recovery
Published Sep 1, 2022 · Updated Aug 3, 2024
Improper quantity validation in the MLNX_DPDK mlx5 network stack in NVIDIA FLARE allows remote authenticated users to interrupt service. After an mlx5 driver failure, the network stack mishandles error recovery and can leave the network interface in an unrecoverable state. Exploitation requires low privileges and traffic reaching an affected mlx5-backed data plane; the vendor assessment limits the demonstrated impact to availability.
Summary
What happened
Improper quantity validation in the MLNX_DPDK mlx5 network stack in NVIDIA FLARE allows remote authenticated users to interrupt service. After an mlx5 driver failure, the network stack mishandles error recovery and can leave the network interface in an unrecoverable state. Exploitation requires low privileges and traffic reaching an affected mlx5-backed data plane; the vendor assessment limits the demonstrated impact to availability.
The record
- CVE
- CVE-2022-28199
- Published
- Sep 1, 2022
- Updated
- Aug 3, 2024
- Vendor
- DPDK Project
- Product
- NVIDIA FLARE
- Classifications
- CWE-20, CWE-1284, T1499
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 1, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=mlnx_dpdk_19.11_1.*.* through mlnx_dpdk_20.11_1.0.0-4.*.*
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo