CVE-2017-0319
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 NVIDIA Windows GPU Display Driver contain a vulnerability in the kernel mode layer handler where improper handling of values may cause a denial of service on the system.
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 confidenceVulnerability in the kernel mode layer handler of NVIDIA Windows GPU Display Driver where improper handling of values can cause a system denial of service. The flaw exists in the kernel-mode portion of the display driver, making it capable of crashing the system.
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
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 NVIDIA GPU hardware in the systemOpen Device Manager, expand 'Display adapters', or run 'lspci | grep -i nvidia' or check System Information for NVIDIA graphics devicesAffected if An NVIDIA GPU is present in the system
-
Verify NVIDIA display driver is installedOpen Device Manager, right-click the NVIDIA adapter, select Properties, check the Driver tab for the driver version and provider. Alternatively, open NVIDIA Control Panel and check 'System Information' in the Help menuAffected if A NVIDIA display driver is installed (any version)
-
Check the kernel-mode driver file versionLocate the driver file (typically nvlddmkm.sys in C:\Windows\System32\drivers\ or nvddriver.sys), right-click and view Properties, or run 'driverquery /v | findstr nvlddmkm'Affected if The kernel-mode driver file exists on the system (all versions are affected)
-
Confirm the kernel driver is loadedOpen Command Prompt as admin and run 'sc query nvlddmkm' or check in Device Manager if the driver status shows 'This device is started' under Driver detailsAffected if The NVIDIA kernel-mode driver is running (required for exploitation)
If an NVIDIA GPU with the display driver is installed and the kernel-mode driver is loaded on a Windows system, the environment is affected by this vulnerability since all driver versions are impacted.
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 the NVIDIA Windows GPU Display Driver to a patched version that addresses this kernel mode layer handler vulnerability. Given that all versions are affected, inventorying and updating all affected systems is necessary.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-0319 — 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-0319 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