dbcve.org
Cuda ToolkitApplication · Nvidia

CVE-2025-23247

HIGH · 7.8 CVSS v3.1 Published 2025-05-27
Fix available
A fix is available. Upgrade to 12.9.0 or later.
See remediation →
81/100
Remediation priority · High
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 all platforms contains a vulnerability in the cuobjdump binary, where a failure to check the length of a buffer could allow a user to cause the tool to crash or execute arbitrary code by passing in a malformed ELF file. A successful exploit of this vulnerability might lead to arbitrary code execution.

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

A buffer length validation vulnerability exists in NVIDIA's cuobjdump binary within the CUDA Toolkit. When processing a malformed ELF file, the tool fails to properly check buffer sizes before reading data into them, allowing an attacker to trigger a buffer overflow and achieve arbitrary code execution.

MitigationUpdate the CUDA Toolkit to the latest patched version that addresses this vulnerability. Avoid processing untrusted or malformed ELF files with cuobjdump until the patch is applied.

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.9.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
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate cuobjdump binary
    Search for cuobjdump in common CUDA paths such as /usr/local/cuda/bin/, /usr/bin/cuda/bin/, or run 'which cuobjdump' or 'find /usr -name cuobjdump 2>/dev/null'
    Affected if cuobjdump binary exists on the system and is from a CUDA Toolkit version below 12.9.0
  2. Determine CUDA Toolkit version
    Run 'nvcc --version' to display the CUDA Toolkit version, or check the directory name in /usr/local/cuda/ (e.g., cuda-12.8, cuda-12.9)
    Affected if The installed CUDA Toolkit version is below 12.9.0 (for example, 12.8.x, 12.7.x, 12.6.x, etc.)
  3. Get cuobjdump version directly
    Run 'cuobjdump -V' or 'cuobjdump --version' to display the cuobjdump utility version
    Affected if cuobjdump reports a version number lower than 12.9.0
  4. Verify ELF processing workflow
    Check if cuobjdump is used in automated pipelines or scripts that process ELF files from untrusted sources by reviewing crontabs, build scripts, or CI/CD configurations
    Affected if cuobjdump is configured to process ELF files from external or untrusted sources

A system is affected if CUDA Toolkit (and thus cuobjdump) version is installed and is lower than 12.9.0, and cuobjdump processes potentially untrusted ELF 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.9.0 or later
Fixed in 12.9.0
Interim mitigation

Update the CUDA Toolkit to the latest patched version that addresses this vulnerability. Avoid processing untrusted or malformed ELF files with cuobjdump until the patch is applied.

Recommended fix High confidence

CUDA Toolkit 12.9.0

  1. 1. Download CUDA Toolkit version 12.9.0 or later from the official NVIDIA website (developer.nvidia.com/cuda-downloads)
  2. 2. Uninstall the currently installed version of CUDA Toolkit
  3. 3. Install the new CUDA Toolkit version 12.9.0 or later following NVIDIA's installation instructions
  4. 4. Verify the installation by running 'cuobjdump --version' to confirm the updated version is installed
  5. 5. Test any automation or scripts that use cuobjdump to ensure compatibility with the new version
Caveat Point release upgrade with minimal expected breaking changes; however, always test in a non-production environment first

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

Fix this in Cuda Toolkit Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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