CVE-2024-0108
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 Jetson Linux contains a vulnerability in NvGPU where error handling paths in GPU MMU mapping code fail to clean up a failed mapping attempt. A successful exploit of this vulnerability may lead to denial of service, code execution, and escalation of privileges.
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 confidenceNVIDIA Jetson Linux contains a vulnerability in the NvGPU driver where error handling paths in the GPU MMU mapping code fail to properly clean up resources after a failed mapping attempt. This memory management flaw can lead to resource leaks or memory corruption, potentially allowing an attacker to achieve denial of service, arbitrary code execution, or privilege escalation.
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< 32.7.5CVSS 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
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/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.
-
Identify Jetson Linux versionRun 'cat /etc/nv_tegra_release' or 'cat /etc/version' on the Jetson device to retrieve the installed Jetson Linux release versionAffected if The version shown is less than 32.7.5 (for example, 32.7.4, 32.7.3, 32.6.1, etc.)
-
Confirm NvGPU driver is presentRun 'lsmod | grep nvgpu' or check 'ls /proc/driver/' to verify the NVIDIA GPU driver module is loaded on the systemAffected if The nvgpu or nvgpu driver module is listed as loaded or present, indicating the vulnerable component is in use
-
Verify GPU is accessibleRun 'ls -la /dev/nv*' or check for GPU device nodes; also run 'nvidia-smi' if available on the Jetson platform to confirm GPU functionality is enabledAffected if GPU device nodes exist or nvidia-smi returns GPU information, confirming the GPU and its driver are active
If the installed Jetson Linux version is below 32.7.5 and the NvGPU GPU driver is loaded and active, the environment is affected by this vulnerability.
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 · scoped32.7.5
Apply NVIDIA's Jetson Linux updates when available. Until a patch is released, limit device exposure to trusted users and networks, and ensure principle of least privilege for processes interacting with the GPU.
Jetson Linux 32.7.5
- Backup all critical data from the Jetson device before proceeding with the upgrade
- Obtain the Jetson Linux 32.7.5 release image from NVIDIA's official download portal
- Follow NVIDIA's standard Jetson Linux flashing procedure to install version 32.7.5 or later
- After flashing, verify the installed version matches the fixed release using 'head -n 1 /etc/nv_tegra_release' or similar version check
- Re-deploy any required applications and restore data from the backup
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-0108 — 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-2024-0108 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