CVE-2025-23339
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 CUDA Toolkit for all platforms contains a vulnerability in cuobjdump where an attacker may cause a stack-based buffer overflow by getting the user to run cuobjdump on a malicious ELF file. A successful exploit of this vulnerability may lead to arbitrary code execution at the privilege level of the user running cuobjdump.
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 confidenceA stack-based buffer overflow vulnerability exists in NVIDIA's cuobjdump utility (used to inspect CUDA binary files). When a user runs cuobjdump on a maliciously crafted ELF file, the overflow occurs during parsing, potentially allowing arbitrary code execution at the privilege level of the user running the tool.
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< 13.0.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Locate cuobjdump installationRun 'which cuobjdump' or search common CUDA paths such as /usr/local/cuda/bin/cuobjdump, /opt/cuda/bin/cuobjdump, or check your CUDA_INSTALL_PATH environment variableAffected if cuobjdump is not found on the system, the vulnerability does not apply
-
Determine cuobjdump versionRun 'cuobjdump --version' or 'cuobjdump -v' to obtain the installed version numberAffected if the version cannot be determined and you have an older CUDA Toolkit installation
-
Identify CUDA Toolkit versionRun 'nvcc --version' or check /usr/local/cuda/version.txt if available, as cuobjdump version typically aligns with the parent CUDA Toolkit versionAffected if the CUDA Toolkit version is less than 13.0.0 and cuobjdump is present
You are affected if cuobjdump is installed and the CUDA Toolkit version is below 13.0.0, since the vulnerability exists in the tool itself when parsing ELF files.
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.
dbcve · scoped13.0.0
Avoid running cuobjdump on untrusted or unknown ELF files. Apply the NVIDIA CUDA Toolkit security patch when released. Consider restricting access to cuobjdump in high-security environments.
CUDA Toolkit 13.0.0 or later
- Identify the current CUDA Toolkit version by running 'nvcc --version' or checking the installation directory
- Download CUDA Toolkit version 13.0.0 or later from the official NVIDIA website (developer.nvidia.com/cuda-downloads)
- Backup any existing CUDA projects and configurations before upgrading
- Install the new CUDA Toolkit version following NVIDIA's official installation guide for your operating system
- Verify the installation by running 'nvcc --version' to confirm the new version is active
- Verify cuobjdump has been updated by running 'cuobjdump --version' to ensure the patched version is installed
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-23339 — 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-23339 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