dbcve.org
Gpu Display DriverApplication · Nvidia

CVE-2023-25515

HIGH · 7.6 CVSS v3.1 Published 2023-06-23
Fix available
A fix is available. Upgrade to 11.12 / 13.7 or later.
See remediation →
81/100
Remediation priority · High
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
NVIDIA GPU Display Driver for Windows and Linux contains a vulnerability where unexpected untrusted data is parsed, which may lead to code execution, denial of service, escalation of privileges, data tampering, 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 confidence

NVIDIA GPU Display Driver for Windows and Linux contains a parsing vulnerability where unexpected untrusted data is processed, potentially allowing an attacker to achieve code execution, cause denial of service, escalate privileges, tamper with data, or disclose information.

MitigationApply the latest NVIDIA GPU display driver update/patch from NVIDIA's official drivers page or through your organization's patch management system to remediate this vulnerability.

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 Display DriverApplication
Affected:>= 470, < 474.44>= 530, < 536.23>= 530, < 536.40>= 525, < 529.11>= 530, < 536.25>= 450, < 454.23>= 470, < 470.199.02>= 525, < 525.125.06>= 530, < 535.54.03>= 450, < 450.248.02
Virtual GpuApplication
Affected:< 11.12>= 13.0, < 13.7>= 15.0, < 15.2
Cloud GamingApplication
Affected:< 531.79

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
Physical
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:C/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 checks

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

  1. Check NVIDIA GPU Display Driver version on Windows
    Open Command Prompt or PowerShell and run: nvidia-smi --query-gpu=driver_version --format=csv,noheader. Alternatively, open NVIDIA Control Panel > Help > System Information, or view the driver version in Device Manager under Display adapters.
    Affected if Driver version matches any of these vulnerable ranges: 450 to 454.23, 450 to 450.248.02, 470 to 474.44, 470 to 470.199.02, 525 to 529.11, 525 to 525.125.06, 530 to 535.54.03, 530 to 536.23, 530 to 536.25, or 530 to 536.40 (but not including the fixed versions)
  2. Check NVIDIA GPU Display Driver version on Linux
    Open a terminal and run: nvidia-smi --query-gpu=driver_version --format=csv,noheader. Alternatively, check the installed package version using package manager (e.g., dpkg -l | grep nvidia or rpm -qa | grep nvidia).
    Affected if Driver version matches any of the vulnerable ranges listed above for Windows (same version ranges apply)
  3. Check NVIDIA vGPU software version
    On the hypervisor host, check the installed vGPU software package version. For VMware: vmware -v or check the NVIDIA vGPU manager package. For Citrix: check the XenServer NVIDIA vGPU package. For Windows Server: check Programs and Features or run nvidia-smi to see the vGPU version.
    Affected if vGPU software version is less than 11.12, or between 13.0 and 13.7 (inclusive), or between 15.0 and 15.2 (inclusive)
  4. Check NVIDIA Cloud Gaming version
    Check the installed NVIDIA Cloud Gaming client version through the application, or check the installed package on the cloud gaming server system.
    Affected if Cloud Gaming version is less than 531.79

The environment is affected if the installed NVIDIA GPU driver, vGPU software, or Cloud Gaming version falls within any of the vulnerable version ranges specified in the CVE.

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.

dbcve · scoped
Upgrade available Upgrade to 11.12 / 13.7 / 15.2 or later
Fixed in 11.1213.715.2
Interim mitigation

Apply the latest NVIDIA GPU display driver update/patch from NVIDIA's official drivers page or through your organization's patch management system to remediate this vulnerability.

Recommended fix High confidence

Gpu Display Driver: 474.44 (470 series), 529.11 (525 series), 536.40 (530 series) | Virtual GPU: 11.12, 13.7, 15.2 | Cloud Gaming: 531.79

  1. 1. Identify the exact NVIDIA driver version currently installed by running 'nvidia-smi' or checking the Windows Device Manager
  2. 2. For Gpu Display Driver users: Determine which branch series you are on (470, 525, or 530) by checking the driver version number
  3. 3. For Virtual GPU users: Check the current version of the vGPU Manager (host) and vGPU Guest Driver
  4. 4. For Cloud Gaming users: Identify the current Grid/Cloud Gaming software version
  5. 5. Download the appropriate fixed driver/software from the official NVIDIA download center or your enterprise software distribution channel
  6. 6. For Windows: Run the executable installer and follow the prompts; for Linux: Extract and run the .run installer with root privileges, or use your distribution's package manager
  7. 7. Reboot the system after installation completes
  8. 8. Verify the new version is installed by running 'nvidia-smi' and confirming the driver version matches the fixed release
Caveat Driver updates may require CUDA toolkit reconfiguration; some legacy applications may have compatibility issues with newer driver branches; enterprise environments should test in staging before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Gpu Display Driver 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-2023-25515 — 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-2023-25515 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