dbcve.org
Gpu DriverApplication · Nvidia

CVE-2017-0351

HIGH · 7.8 CVSS v3.0 Published 2017-05-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

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
All versions of the NVIDIA GPU Display Driver contain a vulnerability in the kernel mode layer handler where a NULL pointer dereference caused by invalid user input may lead to denial of service or potential 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 · high confidence

A NULL pointer dereference vulnerability exists in the kernel mode layer handler of all NVIDIA GPU Display Driver versions. The vulnerability is triggered by invalid user input and can lead to denial of service or potential privilege escalation.

MitigationUpdate the NVIDIA GPU Display Driver to the latest version that includes the security fix for this kernel mode handler vulnerability.

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
Gpu DriverApplication
Affected:all versions

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm NVIDIA GPU Display Driver is installed
    Open Windows Device Manager, expand 'Display adapters', and look for any NVIDIA GPU entry. Alternatively, run 'wmic product get name,version' or check for NVIDIA driver files in C:\Windows\System32\drivers\ (files like nvlddmkm.sys)
    Affected if Any NVIDIA GPU display driver is present on the system
  2. Identify the installed driver version
    Right-click the NVIDIA GPU in Device Manager, select Properties, go to the Driver tab, and note the Driver Version. Or run 'nvidia-smi --query-gpu=driver_version --format=csv,noheader' if available, or check the registry at HKLM\SYSTEM\CurrentControlSet\Services\nvlddmkm\ImagePath
    Affected if The driver version cannot be determined or shows any version number (since all versions are affected)
  3. Verify the kernel mode driver component exists
    Check for the presence of nvlddmkm.sys or nvd3dumx.dll in the System32\drivers or System32 folders. This kernel mode component is where the NULL pointer dereference occurs
    Affected if The NVIDIA kernel mode driver file (nvlddmkm.sys) exists on the system

If an NVIDIA GPU Display Driver is installed (any version), the system is potentially affected by this vulnerability since all versions are impacted.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the NVIDIA GPU Display Driver to the latest version that includes the security fix for this kernel mode handler vulnerability.

Fix this in Gpu Driver Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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