CVE-2019-5677
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 · uneditedNVIDIA Windows GPU Display driver software for Windows (all versions) contains a vulnerability in the kernel mode layer (nvlddmkm.sys) handler for DeviceIoControl where the software reads from a buffer using buffer access mechanisms such as indexes or pointers that reference memory locations after the targeted buffer, which may lead to 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 · high confidenceNVIDIA's Windows GPU display driver (nvlddmkm.sys) contains an out-of-bounds read vulnerability in its kernel-mode DeviceIoControl handler. The driver improperly accesses memory locations beyond the intended buffer boundary using incorrect indexes or pointers, causing a denial of service condition (likely a system crash).
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.
-
Verify NVIDIA GPU hardware is presentOpen Device Manager, expand 'Display adapters', or run 'lspci | grep -i nvidia' on Windows via PowerShell 'Get-PnpDevice -Class DisplayAdapter | Where-Object {$_.FriendlyName -match "NVIDIA"}'Affected if No NVIDIA GPU is found, the system is not affected by this driver vulnerability
-
Identify installed NVIDIA driver versionOpen NVIDIA Control Panel > System Information, or run 'nvidia-smi' from command line, or check driver version in Device Manager under the NVIDIA GPU properties > Driver tabAffected if Unable to retrieve a driver version indicates no NVIDIA driver is installed
-
Confirm nvlddmkm.sys kernel driver is loadedCheck driver loaded in memory: open Task Manager > Details tab > find 'nvlddmkm.sys' process or run 'driverquery /v | findstr nvlddmkm' in command promptAffected if The driver is not loaded, the specific vulnerability surface is not active
-
Compare driver version against patched releaseCross-reference the identified driver version with NVIDIA's security bulletin for CVE-2019-5677 - the driver version range listed in the NVIDIA advisory indicates the vulnerable versionsAffected if Driver version falls within the vulnerable range and no patch has been applied
A system is affected if it has an NVIDIA GPU with the nvlddmkm.sys kernel driver loaded and the installed driver version is within the vulnerable range before the patch was released.
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 patched version that addresses the out-of-bounds read vulnerability in the kernel-mode handler.
- Consultation3.0 h
- Implementation2.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 $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-5677 — 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-2019-5677 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