dbcve.org
Ubuntu LinuxOperating system · Canonical

CVE-2015-7869

MEDIUM · 6.6 CVSS v2.0 Published 2015-11-24
Fix available
A fix is available. Upgrade to 304.131 / 340.96 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
Multiple integer overflows in the kernel mode driver for the NVIDIA GPU graphics driver R340 before 341.92, R352 before 354.35, and R358 before 358.87 on Windows and R304 before 304.131, R340 before 340.96, R352 before 352.63, and R358 before 358.16 on Linux allow local users to obtain sensitive information, cause a denial of service (crash), or possibly gain privileges via unknown vectors, which trigger uninitialized or out of bounds memory access. NOTE: this identifier has been SPLIT per ADT2 and ADT3 due to different vulnerability type and affected versions. See CVE-2015-8328 for the vulnerability in the NVAPI support layer in NVIDIA drivers for Windows.

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

Multiple integer overflow vulnerabilities in NVIDIA's kernel-mode GPU driver allow local users to trigger uninitialized or out-of-bounds memory access, potentially enabling information disclosure, denial of service (crash), or privilege escalation. The vulnerabilities exist across multiple driver branches (R304, R340, R352, R358) on both Windows and Linux platforms.

MitigationUpdate NVIDIA GPU drivers to the patched versions: R341.92 or later for Windows R340, R354.35 or later for Windows R352, R358.87 or later for Windows R358; or R304.131, R340.96, R352.63, R358.16 or later for Linux.

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
Ubuntu LinuxOperating system
Affected:= 12.04= 14.04= 15.04= 15.10
Gpu DriverApplication
Affected:>= 304, < 304.131>= 340, < 340.96>= 352, < 352.63>= 358, < 358.16= 346.22>= 340, < 341.96>= 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 kernel driver is loaded
    On Linux, run: lsmod | grep nvidia. On Windows, check Device Manager under Display Adapters for NVIDIA GPU
    Affected if The NVIDIA kernel-mode driver is present and loaded
  2. Check installed NVIDIA driver version on Linux
    Run: cat /proc/driver/nvidia/version OR nvidia-smi --query-gpu=driver_version --format=csv,noheader
    Affected if The reported version falls within affected ranges: >=304 to <304.131, >=340 to <340.96, >=352 to <352.63, >=358 to <358.16, or exactly 346.22, or >=340 to <341.96, >=352 to <354.35, >=358 to <358.87
  3. Check installed NVIDIA driver version on Windows
    Open Command Prompt and run: nvidia-smi --query-gui=driver_version --format=csv,noheader OR check the driver version in Device Manager under NVIDIA GPU properties
    Affected if The reported version falls within the same affected ranges listed above
  4. Identify the specific driver branch in use
    Examine the full version string: for example, version 340.xx indicates R340 branch. Compare the major branch number (304, 340, 352, 358) against the vulnerable branches
    Affected if The driver branch is R304, R340, R352, or R358 with a version lower than the patched releases for that branch

You are affected if you have an NVIDIA kernel-mode GPU driver loaded with a version matching any of the vulnerable branches (R304, R340, R352, R358) at versions below the patched thresholds (304.131, 340.96, 352.63, 358.16 for Linux; or 341.92, 354.35, 358.87 for 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 304.131 / 340.96 / 341.96 or later
Fixed in 304.131340.96341.96
Interim mitigation

Update NVIDIA GPU drivers to the patched versions: R341.92 or later for Windows R340, R354.35 or later for Windows R352, R358.87 or later for Windows R358; or R304.131, R340.96, R352.63, R358.16 or later for Linux.

Fix this in Ubuntu Linux Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-7869 — 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-7869 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