CVE-2023-0182
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 GPU Display Driver for Windows contains a vulnerability in the kernel mode layer, where an out-of-bounds write can lead to denial of service, information disclosure, and data tampering.
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 confidenceNVIDIA GPU Display Driver for Windows contains an out-of-bounds write vulnerability in the kernel mode layer. This memory corruption issue in the graphics driver can lead to denial of service, information disclosure, and data tampering.
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< 11.12>= 13.0, < 13.7>= 15.0, < 15.2CVSS 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 if NVIDIA Virtual GPU software is installedCheck for NVIDIA vGPU driver components. On Windows, look for NVIDIA virtual GPU driver packages in Programs and Features, or check for NVIDIA driver services (nvvsvc). On hypervisor hosts, check for NVIDIA vGPU Manager installation.Affected if NVIDIA Virtual GPU software is present on the system
-
Determine the installed NVIDIA vGPU driver versionRun 'nvidia-smi' command if available, or check the NVIDIA vGPU Manager version through the hypervisor's virtual machine settings. On Windows guests, check the display driver version via Device Manager under Display adapters.Affected if The installed version cannot be determined or is in the affected ranges
-
Compare installed version against affected rangesReview the installed version number and compare it to the affected version ranges: versions < 11.12, versions >= 13.0 and < 13.7, and versions >= 15.0 and < 15.2.Affected if The installed version falls within any of these ranges: < 11.12, 13.0-13.6, or 15.0-15.1
The system is affected if NVIDIA Virtual GPU software is installed and the installed version is less than 11.12, between 13.0-13.6, or between 15.0-15.1.
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.
dbcve · scoped11.1213.715.2
Apply the NVIDIA driver update/patch released to address this kernel-mode vulnerability in the display driver for Windows.
NVIDIA Virtual GPU 11.12, 13.7, or 15.2 (depending on your current version branch)
- Identify the current version of NVIDIA Virtual GPU software installed
- Determine which version range your current installation falls into: < 11.12, >= 13.0 and < 13.7, or >= 15.0 and < 15.2
- For versions < 11.12: upgrade to version 11.12 or later
- For versions >= 13.0 and < 13.7: upgrade to version 13.7 or later
- For versions >= 15.0 and < 15.2: upgrade to version 15.2 or later
- Verify the upgrade was successful by checking the driver version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-0182 — 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-2023-0182 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