CVE-2017-0310
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 GPU Display Driver contain a vulnerability in the kernel mode layer handler where improper access controls allowing unprivileged user to cause 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 confidenceAll versions of NVIDIA GPU Display Driver contain a vulnerability in the kernel mode layer handler where improper access controls allow an unprivileged user to cause a denial of service via the kernel mode layer.
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
- Changed
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/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.
-
Confirm NVIDIA GPU Display Driver is installedCheck system device manager or run 'driverquery /v' and look for NVIDIA display drivers (nvlddmkm.sys or similar) in the outputAffected if NVIDIA GPU Display Driver is present on the system
-
Identify the installed driver versionIn Device Manager, right-click the NVIDIA display adapter, select Properties, go to the Driver tab, and note the Driver Version field. Alternatively, run 'nvidia-smi' from the command line if availableAffected if The installed version matches the range of all versions and has not been patched
-
Verify kernel mode layer component is loadedCheck for the presence of NVIDIA kernel mode drivers (typically nvlddmkm.sys) in the Windows\System32\drivers directory or via 'sc query nvlddmkm' commandAffected if The NVIDIA kernel mode driver is loaded and active
-
Check if the driver is accessible to unprivileged usersReview the security descriptor of the NVIDIA driver device object using tools like 'sdutil' or by examining NTFS permissions on driver files in System32\driversAffected if Unprivileged or standard users have write or execute access to the kernel mode driver interface
-
Compare installed version to vendor-fixed releasesCheck NVIDIA's official security bulletin for CVE-2017-0310 to identify the patched version number, then compare against your installed versionAffected if The installed driver version is older than the vendor-specified patched version
The system is affected if NVIDIA GPU Display Driver is installed and the installed version predates the vendor's patched release, with the kernel mode layer accessible to unprivileged users.
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-provided patch or update to the NVIDIA GPU Display Driver to the latest version that addresses this access control vulnerability.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-0310 — 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-0310 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