CVE-2017-0350
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 · uneditedAll versions of the NVIDIA GPU Display Driver contain a vulnerability in the kernel mode layer handler where a value passed from a user to the driver is not correctly validated and used in an offset calculation 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 · moderate confidenceNVIDIA GPU Display Driver contains a kernel mode layer handler vulnerability where user-supplied values are not validated before use in offset calculations. This improper validation allows local attackers to potentially manipulate memory offsets, leading to denial of service or privilege escalation to kernel level.
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 dataall versionsCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify NVIDIA GPU Display Driver is installedCheck for NVIDIA driver components. Windows: Look for 'NVIDIA Control Panel' in Programs and Features, or run 'nvidia-smi' from command line. Linux: Run 'nvidia-smi' or check /proc/driver/nvidia/versionAffected if NVIDIA GPU Display Driver is present on the system
-
Determine installed driver versionRun 'nvidia-smi' and note the driver version in the output header (e.g., 'Driver Version: 375.26'), or on Windows check the version of nvlddmkm.sys in System32\drivers\Affected if A driver version is returned by nvidia-smi or found in driver properties
-
Confirm kernel mode layer component is loadedWindows: Run 'sc query nvlddmkm' or check Device Manager for 'NVIDIA Virtual Audio Device' or GPU adapters. Linux: Run 'lsmod | grep nvidia' to confirm nvidia kernel module is loadedAffected if The NVIDIA kernel mode driver (nvlddmkm.sys on Windows, nvidia.ko on Linux) is loaded or present in the driver database
-
Verify all versions are affectedSince CVE-2017-0350 states ALL versions of NVIDIA GPU Display Driver are vulnerable, compare your installed version (from step 2) to any version range provided in NVIDIA security bulletins. No version is safe from this vulnerability.Affected if Any version of NVIDIA GPU Display Driver is installed, regardless of version number
If the NVIDIA GPU Display Driver is installed and the kernel mode layer component (nvlddmkm.sys or nvidia.ko) is loaded, the system is affected by CVE-2017-0350 since all driver versions contain the validation flaw in the kernel mode layer handler.
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.
From vendor dataUpdate NVIDIA GPU Display Driver to a patched version that properly validates user-supplied values before using them in offset calculations within the kernel mode layer handler.
- Consultation3.0 h
- Implementation2.0 h
- Testing3.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 $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-0350 — 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-2017-0350 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