CVE-2024-0090
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 GPU driver for Windows and Linux contains a vulnerability where a user can cause an out-of-bounds write. A successful exploit of this vulnerability might lead to code execution, denial of service, escalation of privileges, information disclosure, and data tampering.
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 GPU driver for Windows and Linux contains an out-of-bounds write vulnerability that can be triggered by a user, potentially leading to code execution, denial of service, privilege escalation, information disclosure, or data tampering. The vulnerability exists in the driver's memory handling logic.
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>= 470, < 475.06>= 535, < 538.67>= 550, < 552.55>= 555, < 555.99>= 470, < 470.256.02>= 535, < 535.180.01>= 550, < 550.90.07>= 555, < 555.52.04< 13.11>= 14.0, < 16.6>= 17.0, < 17.2< 17.2< 555.99< 555.52.04CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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 NVIDIA Display Driver version on WindowsRun 'nvidia-smi' in Command Prompt or PowerShell, or check via Device Manager by right-clicking the NVIDIA GPU and selecting Properties > Driver versionAffected if The displayed driver version falls within any of these ranges: 470.x to 475.05, 535.x to 538.66, 550.x to 552.54, 555.x to 555.98, 470.x to 470.256.01, 535.x to 535.180.00, 550.x to 550.90.06, or 555.x to 555.52.03
-
Check NVIDIA Display Driver version on LinuxRun 'nvidia-smi' or 'cat /proc/driver/nvidia/version' in terminalAffected if The displayed driver version falls within any of the affected ranges listed above (470.x to 475.05, 535.x to 538.66, etc.)
-
Check NVIDIA vGPU software versionOn the hypervisor host, check the installed NVIDIA vGPU Manager version via 'nvidia-smi' or consult your virtualization management console for the installed vGPU software package versionAffected if The vGPU software version is lower than 13.11, or between 14.0 and 16.5, or between 17.0 and 17.1, or lower than 17.2 (for the >=17.0 branch)
-
Check NVIDIA Cloud Gaming software versionConsult your Cloud Gaming installation or management system to identify the installed NVIDIA Cloud Gaming software versionAffected if The Cloud Gaming version is lower than 555.99 or lower than 555.52.04 (checking both branches)
You are affected if your installed NVIDIA GPU driver, vGPU software, or Cloud Gaming version matches any of the specific version ranges listed in the affected products and versions.
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.1116.617.2
Apply the latest NVIDIA GPU driver update from NVIDIA's website or your enterprise patch management system. Verify driver compatibility with production systems before deployment.
Gpu Display Driver: 475.06, 538.67, 552.55, or 555.99 (depending on current branch); Virtual GPU: 13.11, 16.6, or 17.2; Cloud Gaming: 555.99 or 555.52.04
- 1. Identify the currently installed NVIDIA driver version by running 'nvidia-smi' or checking the NVIDIA Control Panel/System Information.
- 2. For Gpu Display Driver users: Determine which version branch you are on (470.x, 535.x, 550.x, or 555.x) based on the installed version.
- 3. Download the appropriate fixed driver version from the official NVIDIA website (nvidia.com) or your enterprise software distribution channel:
- - For 470.x branch: Upgrade to 475.06 or later
- - For 535.x branch: Upgrade to 538.67 or later
- - For 550.x branch: Upgrade to 552.55 or later
- - For 555.x branch: Upgrade to 555.99 or later
- 4. For Virtual GPU users: Upgrade to version 13.11, 16.6, 17.2, or later as applicable to your deployment.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.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,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-0090 — 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-0090 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