CVE-2020-5964
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, all versions, contains a vulnerability in the service host component, in which the application resources integrity check may be missed. Such an attack may lead to code execution, denial of service or information disclosure.
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 vulnerability in the NVIDIA Windows GPU Display Driver service host component fails to properly perform application resources integrity checks, potentially allowing attackers to inject or modify resources leading to code execution, denial of service, or information disclosure.
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 data>= 390, < 392.61>= 418, < 426.78>= 440, < 443.18>= 450, < 451.48>= 418, < 426.78>= 440, < 443.18>= 450, < 451.48< 3.20.4>= 390, < 392.61>= 418, < 426.78>= 440, < 443.18>= 450, < 451.48>= 450, < 451.48CVSS 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.1/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.
-
Identify NVIDIA GPU hardwareOpen Device Manager, expand 'Display adapters' to list installed NVIDIA GPUs, or run 'nvidia-smi -q' to query GPU detailsAffected if Any NVIDIA GPU from the Quadro, Tesla, Nvs, or Geforce product lines is present
-
Check NVIDIA display driver versionRun 'nvidia-smi' or right-click the NVIDIA icon in the system tray and select 'NVIDIA Control Panel', then check 'System Information' for the driver versionAffected if The driver version falls within any of these vulnerable ranges: 390 to 392.60, 418 to 426.77, 440 to 443.17, or 450 to 451.47
-
Check NVIDIA firmware versionRun 'nvidia-smi' to query the VBIOS/firmware version installed on the GPU, or use NVIDIA Enterprise Management Tools to query firmwareAffected if The firmware version matches the affected Quadro, Tesla, Nvs, or Geforce firmware ranges provided in the CVE (390-392.60, 418-426.77, 440-443.17, or 450-451.47)
-
Check Geforce Experience versionOpen Programs and Features or the Windows Apps & features list, find 'NVIDIA GeForce Experience', and note the installed version numberAffected if The installed version is lower than 3.20.4
You are affected if any installed NVIDIA driver, firmware, or Geforce Experience version falls within the specific vulnerable version ranges listed in the CVE.
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 data3.20.4392.61426.78
Update NVIDIA GPU display drivers to the latest version incorporating security fixes; apply any vendor-supplied patches for affected versions.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.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,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-5964 — 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-2020-5964 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