dbcve.org
Gpu DriverApplication · Nvidia

CVE-2015-8328

MEDIUM · 6.6 CVSS v2.0 Published 2015-11-24
Fix available
A fix is available. Upgrade to 341.92 or later.
See remediation →
71/100
Remediation priority · Elevated
No privileges Zero-click

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 · unedited
Unspecified vulnerability in the NVAPI support layer in the NVIDIA GPU graphics driver R340 before 341.92, R352 before 354.35, and R358 before 358.87 on Windows allows local users to obtain sensitive information, cause a denial of service (crash), or possibly gain privileges via unknown vectors. NOTE: this identifier was SPLIT from CVE-2015-7869 per ADT2 and ADT3 due to different vulnerability types and affected versions.

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 confidence

Local privilege escalation and information disclosure vulnerability in NVIDIA's NVAPI support layer affecting graphics drivers R340 before 341.92, R352 before 354.35, and R358 before 358.87 on Windows. Allows local users to potentially obtain sensitive information, cause denial of service, or gain elevated privileges through unspecified vectors.

MitigationUpdate NVIDIA GPU graphics drivers to version 341.92 or later for R340, 354.35 or later for R352, and 358.87 or later for R358. In enterprise environments, test driver updates for compatibility with graphics-intensive applications before broad deployment.

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
Gpu DriverApplication
Affected:>= 340, < 341.92>= 352, <= 354.35>= 358, <= 358.87

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.

From the vector
Attack vector
Local
Complexity
M
Authentication
None
Confidentiality
Complete
Integrity
Partial
Availability
Complete

AV:L/AC:M/Au:N/C:C/I:P/A:C

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 checks

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

  1. Verify NVIDIA GPU driver is installed
    Open Windows Device Manager, expand 'Display adapters', and look for NVIDIA GPU entries. Alternatively, check for the presence of C:\Windows\System32\nvapi.dll or C:\Windows\System32\nvidia-smi.exe.
    Affected if No NVIDIA GPU or driver files are found, then this CVE does not apply.
  2. Retrieve installed NVIDIA driver version via nvidia-smi
    Open Command Prompt or PowerShell and run: nvidia-smi --query-gdriver_version --format=csv,noheader
    Affected if The command fails or returns no version, the NVIDIA driver may not be properly installed or accessible.
  3. Retrieve installed NVIDIA driver version via registry
    Open Registry Editor and navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\nvlddmkm\DriverVersion (or check the Display drivers section in Device Manager properties).
    Affected if Unable to locate driver version in registry indicates no NVIDIA driver is present.
  4. Compare version against affected R340 range
    If installed version starts with 340, verify it is less than 341.92. For example, 340.62 would be affected; 341.92 or higher would not.
    Affected if Installed version is 340.x where x is less than 341.92 (e.g., 340.00 through 341.91).
  5. Compare version against affected R352 range
    If installed version starts with 352, verify it is less than or equal to 354.35. Versions 352.00 through 354.35 inclusive are all affected.
    Affected if Installed version is 352.xx or 353.xx or 354.xx where the full version is 354.35 or lower.
  6. Compare version against affected R358 range
    If installed version starts with 358, verify it is less than or equal to 358.87. Versions 358.00 through 358.87 inclusive are all affected.
    Affected if Installed version is 358.xx where the full version is 358.87 or lower.

A system is affected if it has an NVIDIA GPU driver installed with version 340.x below 341.92, or version 352.xx/353.xx/354.xx at 354.35 or below, or version 358.xx at 358.87 or below, on Windows.

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

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 341.92 or later
Fixed in 341.92
Interim mitigation

Update NVIDIA GPU graphics drivers to version 341.92 or later for R340, 354.35 or later for R352, and 358.87 or later for R358. In enterprise environments, test driver updates for compatibility with graphics-intensive applications before broad deployment.

Fix this in Gpu Driver Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-8328 — 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 Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

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

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