dbcve.org
Cuda ToolkitApplication · Nvidia

CVE-2023-25514

MEDIUM · 6.6 CVSS v3.1 Published 2023-04-22
Fix available
A fix is available. Upgrade to 12.1.1 or later.
See remediation →
69/100
Remediation priority · Elevated
No privileges

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 CUDA toolkit for Linux and Windows contains a vulnerability in cuobjdump, where an attacker may cause an out-of-bounds read by tricking a user into running cuobjdump on a malformed input file. A successful exploit of this vulnerability may lead to limited denial of service, code execution, and limited information disclosure.

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 · high confidence

NVIDIA cuobjdump utility contains an out-of-bounds read vulnerability when processing malformed input files. An attacker can craft a specially designed file that triggers the vulnerability through user interaction, potentially leading to limited DoS, code execution, or information disclosure.

MitigationAvoid running cuobjdump on untrusted or unverified input files; implement file validation before processing; monitor for NVIDIA patches and update CUDA toolkit when available.

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
Cuda ToolkitApplication
Affected:< 12.1.1

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
High
Availability
Low

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

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. Locate cuobjdump utility
    Run 'which cuobjdump' on Linux/macOS or check common installation paths like '/usr/local/cuda/bin/cuobjdump' on Linux, 'C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v*\bin\cuobjdump.exe' on Windows
    Affected if cuobjdump is not found on the system, then this CVE does not apply directly (but the broader CUDA toolkit may still be present)
  2. Identify CUDA Toolkit version
    Check the CUDA version by running 'nvcc --version' or inspecting the directory path containing cuobjdump (e.g., cuda/v12.0 indicates version 12.0)
    Affected if The directory path or version output shows a version lower than 12.1.1 (e.g., 12.0.x, 11.x, etc.)
  3. Confirm cuobjdump binary version
    Run 'cuobjdump --version' or 'cuobjdump -V' to obtain the utility's specific version string
    Affected if The reported version is earlier than 12.1.1 (note: version format may vary; compare numerically

The environment is affected if cuobjdump is present AND the installed CUDA Toolkit version is below 12.1.1, since the vulnerability only triggers when processing malformed input files with this utility.

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 12.1.1 or later
Fixed in 12.1.1
Interim mitigation

Avoid running cuobjdump on untrusted or unverified input files; implement file validation before processing; monitor for NVIDIA patches and update CUDA toolkit when available.

Recommended fix High confidence

CUDA Toolkit 12.1.1

  1. 1. Identify the current CUDA Toolkit version by running 'nvcc --version' or checking /usr/local/cuda directory
  2. 2. Download CUDA Toolkit 12.1.1 from the official NVIDIA website (https://developer.nvidia.com/cuda-downloads)
  3. 3. Uninstall the current CUDA Toolkit version using the appropriate method for your OS (run uninstaller or remove the cuda directory)
  4. 4. Install CUDA Toolkit 12.1.1 using the downloaded installer for your Linux distribution or Windows
  5. 5. Update environment variables (PATH, LD_LIBRARY_PATH) to point to the new CUDA 12.1.1 installation if necessary
  6. 6. Verify the installation by running 'nvcc --version' to confirm version 12.1.1 is installed
  7. 7. Ensure any dependent applications or scripts that reference CUDA are updated to use the new path if needed
Caveat Major CUDA version upgrades may require recompilation of CUDA applications and could have driver compatibility requirements - ensure your NVIDIA driver version supports CUDA 12.1.1

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

Fix this in Cuda Toolkit Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-25514 — 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-2023-25514 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