CVE-2022-21821
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 SDK contains an integer overflow vulnerability in cuobjdump.To exploit this vulnerability, a remote attacker would require a local user to download a specially crafted, corrupted file and locally execute cuobjdump against the file. Such an attack may lead to remote code execution that causes complete denial of service and an impact on data confidentiality and integrity.
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 confidenceInteger overflow vulnerability in NVIDIA CUDA Toolkit's cuobjdump utility. A local user can trigger the overflow by running cuobjdump against a specially crafted corrupted file, potentially leading to remote code execution, denial of service, and data integrity/confidentiality impacts.
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< 11.6.2CVSS 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.
-
Check if CUDA Toolkit is installedSearch for CUDA Toolkit installation directories (common paths: /usr/local/cuda on Linux, C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA on Windows) or run 'nvcc --version' if the compiler is in PATHAffected if CUDA Toolkit is not installed means not affected by this vulnerability
-
Determine the installed CUDA Toolkit versionRun 'nvcc --version' to retrieve the compiler version, or check the version file in the CUDA installation directoryAffected if Version is less than 11.6.2 indicates the environment falls within the affected range
-
Locate the cuobjdump utilityFind the cuobjdump binary in the CUDA bin directory (typically at /usr/local/cuda/bin/cuobjdump or C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v*\bin\cuobjdump.exe)Affected if cuobjdump must be present and executable for the vulnerability to be exploitable
You are affected if CUDA Toolkit version is below 11.6.2 and the cuobjdump utility is available in your environment to process 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 · scoped11.6.2
Apply NVIDIA's patch/update for the CUDA Toolkit when released; avoid processing untrusted or corrupted files with cuobjdump.
CUDA Toolkit 11.6.2 or later
- Identify the current version of CUDA Toolkit installed by running 'nvcc --version' or checking the installation directory
- Download CUDA Toolkit 11.6.2 or later from NVIDIA's official website at https://developer.nvidia.com/cuda-downloads
- Install the updated CUDA Toolkit following NVIDIA's installation instructions for your operating system
- Verify the installation by running 'cuobjdump --version' to confirm the patched version is installed
- Ensure any projects or scripts that reference cuobjdump are updated to use the new installation path if necessary
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-21821 — 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-2022-21821 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