CVE-2017-0320
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 confidenceAll 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. The flaw exists in the kernel-mode component of the display driver, allowing local attackers to potentially crash the system via malformed input handling.
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 hardwareOpen Device Manager and expand 'Display adapters' or run 'lspci | grep -i nvidia' command to list NVIDIA graphics hardwareAffected if No NVIDIA GPU is found in the system
-
Check if NVIDIA display driver is installedIn Windows, open Device Manager, locate the NVIDIA GPU under Display adapters, and check driver details. Alternatively, open NVIDIA Control Panel and go to 'System Information' to verify driver presence.Affected if NVIDIA GPU shows no driver or displays as 'Standard VGA adapter' indicating no NVIDIA driver loaded
-
Verify kernel-mode driver component is loadedOpen Services (services.msc) and check for 'NVIDIA Display Container LS' or similar NVIDIA kernel-mode services, or run 'sc query nvlddmkm' in command promptAffected if NVIDIA kernel-mode driver service is running or loaded into memory
-
Confirm the driver versionIn NVIDIA Control Panel, go to System Information or run 'nvidia-smi' command to display driver version, or check Driver version in Device Manager properties for the NVIDIA GPUAffected if Any version number is displayed (per CVE summary, all versions of NVIDIA Windows GPU Display Driver are affected)
If an NVIDIA GPU is present with the NVIDIA Windows display driver installed and kernel-mode components loaded, the system is affected by this vulnerability since all 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 vulnerability. Organizations should prioritize patching systems with kernel-mode driver exposure and test driver updates in controlled environments before broad deployment.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.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,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-0320 — 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-0320 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