CVE-2023-0188
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 and Linux contains a vulnerability in the kernel mode layer handler, where an unprivileged user can cause improper restriction of operations within the bounds of a memory buffer cause an out-of-bounds read, which may lead to denial of service.
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 · high confidenceNVIDIA GPU Display Driver for Windows and Linux contains a kernel-mode layer handler vulnerability where an unprivileged user can cause improper restriction of operations within memory buffer bounds, resulting in an out-of-bounds read that leads to denial of service.
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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 vGPU software installationOn Windows: Check Programs and Features or run 'nvidia-smi' in command prompt. On Linux: run 'nvidia-smi' or check /usr/bin/vgpu* files. Also check for NVIDIA vGPU Manager service (vgpu-manager on Linux, NVIDIA vGPU Service on Windows).Affected if NVIDIA Virtual GPU software is installed and the version falls within vulnerable ranges (< 11.12, 13.0-13.6.x, or 15.0-15.1.x)
If the NVIDIA vGPU software version is less than 11.12, between 13.0 and 13.6.x inclusive, or between 15.0 and 15.1.x inclusive, the system is affected by this out-of-bounds read vulnerability in the kernel-mode layer handler.
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 GPU Display Driver security patch from NVIDIA's security bulletin to all affected systems.
NVIDIA Virtual GPU >= 11.12 (for 11.x branch), >= 13.7 (for 13.x branch), or >= 15.2 (for 15.x branch)
- Identify the current NVIDIA Virtual GPU software version by checking the host hypervisor or using NVIDIA-smi
- Navigate to the NVIDIA Virtual GPU Software Downloads page (https://www.nvidia.com/en-us/virtual-gpu-technology/)
- Download the appropriate fixed version based on your current branch: if on 11.x branch, upgrade to 11.12 or later; if on 13.x branch, upgrade to 13.7 or later; if on 15.x branch, upgrade to 15.2 or later
- Follow NVIDIA's standard Virtual GPU upgrade procedure: stop virtual machines, uninstall current vGPU software, install the new version, restart the hypervisor host
- Restart any affected virtual machines to load the updated driver
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-0188 — 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-0188 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