CVE-2017-0322
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 (nvlddmkm.sys) handler where a value passed from a user to the driver is not correctly validated and used as the index to an array, leading 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 confidenceA vulnerability exists in all versions of the NVIDIA Windows GPU Display Driver (nvlddmkm.sys) where the kernel mode layer handler fails to properly validate a user-supplied value before using it as an array index. This improper input validation can lead to denial of service or privilege escalation when an attacker manipulates the unvalidated index.
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.
-
Confirm NVIDIA GPU hardware presentOpen Device Manager, expand 'Display adapters' and look for any NVIDIA GPU (e.g., GeForce, Quadro, Tesla series). Alternatively, run 'nvidia-smi' from command line if available.Affected if No NVIDIA GPU listed means likely not affected; presence of NVIDIA hardware indicates potential exposure.
-
Identify NVIDIA display driver versionIn Device Manager, right-click the NVIDIA GPU, select 'Properties', go to 'Driver' tab, and note the driver version. Or run 'nvidia-smi' which displays driver version in output.Affected if Any displayed driver version indicates the vulnerable driver component is installed.
-
Verify nvlddmkm.sys driver file versionNavigate to C:\Windows\System32\Drivers\nvlddmkm.sys, right-click the file, select 'Properties', go to 'Details' tab, and check 'File version'. This is the kernel mode driver component referenced in the CVE.Affected if File exists and has any version number - all versions of this driver are affected per CVE description.
-
Confirm kernel mode driver is loadedOpen Command Prompt as Administrator, run 'sc query nvlddmkm' or check Task Manager > Services for 'NVIDIA Display Container LS' or similar NVIDIA services. Also check 'Driver View' utilities if available.Affected if NVIDIA kernel mode driver service is running or loaded indicates active attack surface for this vulnerability.
If the system runs Windows with any NVIDIA GPU display driver installed (nvlddmkm.sys present), the environment is affected since all versions of this driver are vulnerable per CVE-2017-0322.
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 dataApply the vendor-supplied patch by updating the NVIDIA Windows GPU Display Driver to the latest version from NVIDIA's official security advisory.
- Consultation2.0 h
- Implementation1.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 $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-0322 — 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-0322 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