dbcve.org
Cuda ToolkitApplication · Nvidia

CVE-2023-25513

MEDIUM · 6.6 CVSS v3.1 Published 2023-04-22
Fix available
A fix is available. Upgrade to 12.0.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 · moderate confidence

NVIDIA cuobjdump, a CUDA binary analysis tool, contains an out-of-bounds read vulnerability when parsing malformed input files. An attacker could craft a specially crafted file that, when processed by cuobjdump, allows reading memory beyond allocated buffers, potentially leading to denial of service, code execution via memory disclosure, or limited information exposure.

MitigationAvoid running cuobjdump on untrusted or malformed input files until NVIDIA releases an official patch; validate and sanitize all input files before processing with cuobjdump.

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.0.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 cuobjump executable
    Run 'which cuobjump' or 'where cuobjump' on Windows to find the tool's installation path
    Affected if cuobjump is present on the system and processes external input files
  2. Identify CUDA Toolkit version
    Run 'nvcc --version' or check the CUDA installation directory for a version file, or run 'cuobjump --version' if supported
    Affected if The installed CUDA Toolkit version is below 12.0.1
  3. Compare version against affected range
    Compare the discovered version number to 12.0.1 using semantic version comparison
    Affected if The version is 12.0.0 or earlier, or any version string that evaluates to less than 12.0.1
  4. Assess input exposure
    Review any scripts, workflows, or automated processes that invoke cuobjump on files from untrusted or external sources
    Affected if cuobjump processes files from untrusted or unknown origins without prior validation

You are affected if cuobjump is installed and the CUDA Toolkit version is below 12.0.1 and the tool processes external input files.

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.0.1 or later
Fixed in 12.0.1
Interim mitigation

Avoid running cuobjdump on untrusted or malformed input files until NVIDIA releases an official patch; validate and sanitize all input files before processing with cuobjdump.

Recommended fix High confidence

CUDA Toolkit 12.0.1

  1. 1. Identify the current installed CUDA Toolkit version by running 'nvcc --version'
  2. 2. Download CUDA Toolkit version 12.0.1 or later from the NVIDIA website (developer.nvidia.com/cuda-downloads)
  3. 3. Uninstall the current CUDA Toolkit version using the appropriate package manager or installer
  4. 4. Install the downloaded CUDA Toolkit 12.0.1 for your OS (Linux or Windows)
  5. 5. Verify the installation by running 'nvcc --version' to confirm version 12.0.1 or later is installed
  6. 6. Ensure environment variables (PATH, LD_LIBRARY_PATH) point to the new CUDA installation if manually configuring
Caveat Upgrading CUDA versions may require recompiling applications and verifying compatibility with CUDA-dependent libraries and drivers; ensure your GPU driver version supports CUDA 12.0.1

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

Fix this in Cuda Toolkit Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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