Gpu DriverApplication · Nvidia

CVE-2017-0341

HIGH · 7.8 CVSS v3.0 Published 2017-05-09

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

80/100

Remediation priority · High

Zero-click

Official description

NVD · unedited

All versions of the NVIDIA Windows GPU Display Driver contain a vulnerability in the kernel mode layer (nvlddmkm.sys) handler for DxgDdiEscape where user provided input can trigger an access to a pointer that has not been initialized which may lead to denial of service or potential escalation of privileges.

Technical summary

dbcve analysis · high confidence

A vulnerability exists in the NVIDIA Windows GPU Display Driver's kernel mode layer (nvlddmkm.sys) in the DxgDdiEscape handler. User-supplied input can trigger access to an uninitialized pointer, leading to potential denial of service or privilege escalation.

MitigationUpdate the NVIDIA GPU Display Driver to a version that includes the patched kernel mode layer (nvlddmkm.sys) addressing the uninitialized pointer access in DxgDdiEscape.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

Gpu DriverApplication

Affected:all versions

CVSS breakdown

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?

dbcve checks

Work through these to decide whether this CVE applies to you.

Locate the vulnerable driver file

Check if nvlddmkm.sys exists in C:\Windows\System32\Drivers\ (or search the system for this file)

Affected if The file nvlddmkm.sys is present on the system - all versions of this driver are affected by this CVE
Verify the NVIDIA driver is loaded

Open Device Manager, expand 'Display adapters', and confirm an NVIDIA GPU driver is installed and active; or run 'sc query nvlddmkm' in command prompt to check if the NVIDIA driver service exists

Affected if An NVIDIA display driver is installed and loaded - the kernel mode layer containing the vulnerability is active
Check the driver file version

Right-click nvlddmkm.sys in Windows\System32\Drivers\, select Properties, then view the File Version field; alternatively use 'wmic datafile where "name='C:\\Windows\\System32\\Drivers\\nvlddmkm.sys'" get version'

Affected if The driver file exists - per the CVE, all versions of nvlddmkm.sys contain the uninitialized pointer vulnerability in DxgDdiEscape
Confirm DxgDdiEscape is accessible

The vulnerability is triggered through the DxgDdiEscape handler in the kernel mode driver. Any application that can interface with the display driver (DirectX applications, GPU-accelerated software) can potentially reach this code path

Affected if The NVIDIA driver is actively handling graphics operations - the DxgDdiEscape handler is part of the normal driver operation for display escape functions

If the NVIDIA display driver (nvlddmkm.sys) is present and loaded on a Windows system, the environment is affected by CVE-2017-0341 as all versions contain the uninitialized pointer vulnerability in the DxgDdiEscape handler.

Generated from the published advisory. Verify against your own configuration.

Remediation

From vendor data

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Update the NVIDIA GPU Display Driver to a version that includes the patched kernel mode layer (nvlddmkm.sys) addressing the uninitialized pointer access in DxgDdiEscape.

Fix this in Gpu Driver Scoped from the published advisory

Consultation4.0 h
Implementation3.0 h
Testing4.0 h
Review / QA2.0 h

13.0 hours of engineering $2,300

Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,680.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2017-0341 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References

Primary sources

nvidia.custhelp.comVendor Advisory
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-0341 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2017-0341?

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.

What this is

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.

What belongs here

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

At a glance

A fix existsA vendor remedy is published

Severity 7.8 High

Exploit likelihood EPSS, next 30 days 0.3%

Affects: Gpu Driver

Remediation

A high-priority fix

Fix this in Gpu Driver 13 hrs · Moderate

Typical engagement from $2,300

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2017-0341 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

CVSS 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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References