dbcve.org
Cuda ToolkitApplication · Nvidia

CVE-2023-25512

MEDIUM · 6.6 CVSS v3.1 Published 2023-04-22
Fix available
A fix is available. Upgrade to 12.1.0 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 memory read by 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 toolkit utility for examining GPU executables, contains an out-of-bounds read vulnerability when processing malformed input files. An attacker can trigger this by providing a specially crafted file to cuobjdump, potentially leading to denial of service, limited code execution, or information disclosure through memory contents exposure.

MitigationAvoid running cuobjdump on untrusted input files and monitor for NVIDIA security patches for the CUDA toolkit. Consider restricting access to cuobjdump until a fix is 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.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
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 the cuobjdump binary
    Run 'which cuobjdump' or 'find /usr -name cuobjdump 2>/dev/null' to find the cuobjdump executable in your environment
    Affected if cuobjdump binary is found on the system - the tool is installed and could be used to process files
  2. Determine CUDA Toolkit version
    Run 'nvcc --version' or check '/usr/local/cuda/version.txt' to identify the installed CUDA Toolkit version number
    Affected if CUDA Toolkit version is present and is less than 12.1.0 - this indicates the vulnerable version is installed
  3. Verify cuobjdump version directly
    Run 'cuobjdump -V' or 'cuobjdump --version' to get the cuobjdump utility version directly
    Affected if cuobjdump version reports less than 12.1.0, confirming the vulnerable binary is present
  4. Check for multiple CUDA installations
    Search for other cuobjdump instances: 'find / -name cuobjdump -type f 2>/dev/null' to identify all installed copies
    Affected if Any cuobjdump instance found with version below 12.1.0 means that path is vulnerable

A user is affected if cuobjdump is installed and the CUDA Toolkit version is below 12.1.0, as the out-of-bounds read flaw can be triggered when processing malformed 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.1.0 or later
Fixed in 12.1.0
Interim mitigation

Avoid running cuobjdump on untrusted input files and monitor for NVIDIA security patches for the CUDA toolkit. Consider restricting access to cuobjdump until a fix is available.

Recommended fix High confidence

CUDA Toolkit 12.1.0 or later

  1. 1. Identify the current installed CUDA Toolkit version using 'nvcc --version' or checking the installation directory
  2. 2. Download CUDA Toolkit version 12.1.0 or later from the NVIDIA developer website (https://developer.nvidia.com/cuda-downloads)
  3. 3. Install the updated CUDA Toolkit following the NVIDIA installation guide for your operating system (Linux or Windows)
  4. 4. Verify the installation by running 'nvcc --version' to confirm the version is 12.1.0 or higher
  5. 5. Test that cuobjdump functions correctly with the updated installation
Caveat Review NVIDIA CUDA 12.1 release notes for any potential compatibility considerations with existing projects and dependencies

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
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA6.0 h
20.0 hours of engineering $3,560
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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