dbcve.org
Cuda ToolkitApplication · Nvidia

CVE-2024-0102

MEDIUM · 5.5 CVSS v3.1 Published 2024-08-08
Fix available
A fix is available. Upgrade to 12.6.0 or later.
See remediation →
58/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 all platforms contains a vulnerability in nvdisasm, where an attacker can cause an out-of-bounds read issue by deceiving a user into reading a malformed ELF file. A successful exploit of this vulnerability might lead to denial of service.

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 CUDA Toolkit's nvdisasm tool contains an out-of-bounds read vulnerability when processing malformed ELF files. An attacker can craft a specially designed ELF file that, when opened by a user in nvdisasm, causes the tool to read beyond allocated memory boundaries, potentially leading to denial of service.

MitigationUsers should avoid opening untrusted or malformed ELF files with nvdisasm. Organizations should update to the latest NVIDIA CUDA Toolkit version once the patch is available and implement file validation before processing binaries.

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

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/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. Check if nvdisasm is installed
    Run 'which nvdisasm' or 'where nvdisasm' on Windows to locate the binary. Also check common CUDA installation paths like /usr/local/cuda/bin/nvdisasm or C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v*\bin\nvdisasm.exe
    Affected if nvdisasm binary exists on the system and the CUDA Toolkit version is below 12.6.0
  2. Determine CUDA Toolkit version
    Run 'nvcc --version' to display the CUDA compiler version, or check the directory name in the CUDA installation path (e.g., cuda/v12.4). The version is typically listed in the folder structure under /usr/local/cuda/ or C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\
    Affected if The installed CUDA Toolkit version is anything less than 12.6.0 (for example, 12.4, 12.3, 12.2, 12.1, 12.0, 11.x, etc.)
  3. Verify the specific nvdisasm binary version
    Run 'nvdisasm --version' or 'nvdisasm -v' to get the exact version string of the nvdisasm tool itself
    Affected if The nvdisasm version displayed is earlier than 12.6.0, indicating the tool is vulnerable to malformed ELF file handling
  4. Identify if untrusted ELF files are processed
    Review any automated pipelines, scripts, or user workflows that invoke nvdisasm on files from untrusted or external sources. Search for commands like 'nvdisasm input.elf' where input.elf may originate from outside the organization
    Affected if Users or automated systems use nvdisasm to process ELF files that are not validated as trusted or well-formed

The environment is affected if NVIDIA CUDA Toolkit with nvdisasm version below 12.6.0 is installed AND the tool is used to process potentially untrusted or malformed 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.6.0 or later
Fixed in 12.6.0
Interim mitigation

Users should avoid opening untrusted or malformed ELF files with nvdisasm. Organizations should update to the latest NVIDIA CUDA Toolkit version once the patch is available and implement file validation before processing binaries.

Recommended fix High confidence

CUDA Toolkit 12.6.0

  1. 1. Download CUDA Toolkit 12.6.0 or later from the official NVIDIA website (developer.nvidia.com/cuda-downloads)
  2. 2. Install the new CUDA Toolkit version following NVIDIA's installation instructions for your platform
  3. 3. Verify the nvdisasm version is 12.6.0 or later by running 'nvdisasm --version'
  4. 4. Ensure any automated build or analysis pipelines that use nvdisasm are updated to reference the new Toolkit version
  5. 5. Re-scan or re-analyze any ELF files that were previously processed by the vulnerable nvdisasm version to confirm they parse correctly with the updated tool

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
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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