CVE-2025-23351
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 · uneditedNVIDIA ConnectX and BlueField contain a vulnerability in the command interface where a local user with virtual function (VF) access may cause a write out of bounds by crafted input. A successful exploit of this vulnerability may lead to arbitrary code execution on the device.
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 confidenceNVIDIA ConnectX and BlueField network adapters contain a command interface vulnerability where a local user with virtual function (VF) access can trigger an out-of-bounds write via crafted input, leading to arbitrary code execution on the device.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Adjacent
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify NVIDIA network adapters in the systemRun 'lspci | grep -i mellanox' or 'lspci | grep -i nvidia' to list NVIDIA ConnectX or BlueField network devices present in the systemAffected if No NVIDIA ConnectX or BlueField adapters are found, the system is not affected by this CVE
-
Determine the firmware version of the adapterUse NVIDIA tools such as 'mstflint -d <device> q' or 'flint -d <device> q' to query the current firmware version of the ConnectX or BlueField adapterAffected if The installed firmware version falls within the affected version range (compare against NVIDIA's firmware release notes for this CVE)
-
Check if Virtual Function (VF) is enabledRun 'ip link show' or check /sys/class/net/ for SR-IOV VF interfaces. Use 'lspci -k' to verify if VFs are allocated. Also run 'cat /sys/class/net/<interface>/device/sriov_totalvfs' to check if SR-IOV is configuredAffected if Virtual Functions are enabled and allocated on the affected adapter, creating the attack surface for this vulnerability
-
Verify command interface accessibilityCheck if the command interface (often accessible via /dev/mst/* or through NVIDIA MLX tools) is available to local users. Review permissions on /dev/mst/ devices and check which users have accessAffected if The command interface device is accessible to non-privileged local users, allowing the crafted input vector described in the CVE
A system is affected if it contains a NVIDIA ConnectX or BlueField adapter with a vulnerable firmware version and has Virtual Function (VF) access enabled, allowing a local user to access the command interface.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataApply NVIDIA's firmware update for ConnectX and BlueField devices; restrict VF access to trusted users until the patch is deployed.
- Consultation8.0 h
- Implementation4.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,320.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-23351 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-23351 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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