CVE-2017-0353
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 for DxgDdiEscape where due to improper locking on certain conditions may lead to a denial of service
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 confidenceA race condition or deadlock vulnerability exists in the NVIDIA GPU Display Driver's kernel mode layer handler for the DxgDdiEscape function. Improper locking on certain conditions allows an attacker to trigger a denial of service, likely causing system hang or crash. The vulnerability is locally exploitable given the kernel-level access required.
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.
-
Check for NVIDIA GPU hardwareOpen Device Manager and expand 'Display adapters' or run 'nvidia-smi' from command line if available. Also check System Information (msinfo32) under Components > Display.Affected if An NVIDIA GPU is listed as installed in Device Manager or System Information.
-
Identify NVIDIA kernel driver presenceCheck for NVIDIA display driver files in system directories: look for nvlddmkm.sys or nvlddmkm in C:\Windows\System32\drivers\ or check registry under HKLM\SYSTEM\CurrentControlSet\Services\nvlddmkm.Affected if NVIDIA kernel mode driver (nvlddmkm.sys) is present on the system.
-
Confirm driver version if needed for inventoryRun 'nvidia-smi --query-gpu=driver_version --format=csv,noheader' or check the driver version in Device Manager properties for the NVIDIA display adapter, or query the registry key HKLM\SYSTEM\CurrentControlSet\Services\nvlddmkm\Version.Affected if A driver version is returned (any version confirms the driver is installed).
If any NVIDIA GPU with the display driver is installed on the system, the environment is affected since all versions of the NVIDIA GPU Display Driver contain this vulnerability.
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 GPU Display Driver to a version that includes the fix for CVE-2017-0353. If immediate patching is not feasible, restrict access to privileged users and monitor for abnormal system behavior related to GPU operations.
- 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-0353 — 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-0353 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