CVE-2024-0091
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 Display Driver for Windows and Linux contains a vulnerability where a user can cause an untrusted pointer dereference by executing a driver API. A successful exploit of this vulnerability might lead to denial of service, 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 Display Driver for Windows and Linux contains an untrusted pointer dereference vulnerability that can be triggered through a driver API call. This memory safety issue allows a local user to potentially cause denial of service, expose sensitive information, or tamper with data.
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>= 550, < 552.55>= 555, < 555.99>= 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 GPU Display Driver version on Windows or LinuxRun 'nvidia-smi' from command line or terminal. The output displays Driver Version in the format like '550.127.05' or '555.52.03'. Record the full version string.Affected if The installed driver version falls within these vulnerable ranges: >= 550 and < 552.55, OR >= 555 and < 555.99, OR >= 550 and < 550.90.07, OR >= 555 and < 555.52.04
-
Verify driver file version on WindowsOpen Windows Explorer, navigate to C:\Windows\System32\nvlddmkm.sys (or the .sys file matching your driver). Right-click, select Properties, then Details to view File Version. Alternatively, run 'driverquery /v | findstr nvlddmkm' in command prompt.Affected if The file version matches the affected version ranges listed above for Nvidia Gpu Display Driver
-
Check NVIDIA vGPU Manager versionOn the hypervisor host (VMware ESXi, Citrix Hypervisor, or KVM), use the hypervisor-specific command to check the NVIDIA vGPU manager driver version. For ESXi: 'esxcli software vib list | grep nvidia'. For KVM: check the virsh command or the vGPU manager package version.Affected if The vGPU Manager version is less than 13.11, OR >= 14.0 and < 16.6, OR >= 17.0 and < 17.2, OR < 17.2
-
Check NVIDIA Cloud Gaming software versionOn systems running NVIDIA Cloud Gaming (GeForce NOW server or similar), check the installed NVIDIA driver or gaming software version through its control panel or installed programs list.Affected if The Cloud Gaming component version is less than 555.99 OR less than 555.52.04
A user is affected if their installed NVIDIA GPU Display Driver version, vGPU Manager version, or Cloud Gaming version falls within any of the vulnerable version ranges specified in the CVE.
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 NVIDIA driver patch or update to a version that addresses CVE-2024-0091, following NVIDIA's security bulletin and testing for compatibility with dependent applications.
552.55 (550.x branch), 555.99 (555.x branch), 550.90.07, 555.52.04 for Display Driver; 13.11, 16.6, 17.2 for Virtual GPU; 555.99 or 555.52.04 for Cloud Gaming
- 1. Identify the currently installed NVIDIA GPU driver version using nvidia-smi or system information
- 2. Determine which driver branch (550 or 555 series) is currently in use
- 3. For Gpu Display Driver users: Upgrade to version 552.55 or higher (if using 550.x branch), or 555.99 (if using 555.x branch)
- 4. For Gpu Display Driver users on 550.90.x branch: Upgrade to 550.90.07 or higher
- 5. For Gpu Display Driver users on 555.52.x branch: Upgrade to 555.52.04 or higher
- 6. For Virtual GPU users: Upgrade to 13.11 (for v13.x), 16.6 (for 14.x-16.x), or 17.2 (for 17.x)
- 7. For Cloud Gaming users: Upgrade to 555.99 or 555.52.04
- 8. Download the appropriate driver from nvidia.custhelp.com or NVIDIA Driver Download page
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-0091 — 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-0091 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