Gpu Display DriverApplication · Nvidia
CVE-2023-0199
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 out-of-bounds write can lead to denial of service 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 and Linux contains an out-of-bounds write vulnerability in the kernel mode layer handler. This flaw allows a local attacker to potentially cause denial of service and data tampering by writing beyond allocated memory boundaries in kernel space.
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
>= 470, < 470.182.03>= 515, < 515.105.01>= 525, < 525.105.17>= 530, < 530.41.03>= 450, < 450.236.01>= 450, < 454.14>= 470, < 474.30>= 515, < 518.03>= 525, < 528.89>= 530, < 531.41CVSS 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
- Low
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/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 driver version on WindowsOpen Command Prompt and run: nvidia-smi --query-gpu=driver_version --format=csv,noheader. If nvidia-smi is not available, check via Device Manager: expand 'Display adapters', right-click NVIDIA GPU, select 'Properties', go to 'Driver' tab and note the Driver Version.Affected if The reported driver version falls within any of these ranges: >=470 and <470.182.03; >=515 and <515.105.01; >=525 and <525.105.17; >=530 and <530.41.03; >=450 and <450.236.01; >=450 and <454.14; >=470 and <474.30; >=515 and <518.03; >=525 and <528.89; >=530 and <531.41
-
Identify NVIDIA driver version on LinuxRun command: cat /proc/driver/nvidia/version. Alternatively, run: nvidia-smi --query-gpu=driver_version --format=csv,noheader. Both commands display the installed kernel mode driver version.Affected if The reported driver version falls within any of these ranges: >=470 and <470.182.03; >=515 and <515.105.01; >=525 and <525.105.17; >=530 and <530.41.03; >=450 and <450.236.01; >=450 and <454.14; >=470 and <474.30; >=515 and <518.03; >=525 and <528.89; >=530 and <531.41
-
Confirm NVIDIA kernel module is loadedOn Linux, run: lsmod | grep nvidia. Verify that nvidia, nvidia_uvm, nvidia_modeset modules appear in the output. This confirms the kernel mode layer handler is active.Affected if The kernel modules are loaded and the driver version from step 2 falls within the affected version ranges
You are affected if the installed NVIDIA GPU Display Driver version matches any of the listed vulnerable ranges and the kernel mode layer is active.
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 · scoped450.236.01454.14470.182.03
Apply the latest NVIDIA GPU Display Driver update from the official NVIDIA website or through your organization's patch management system to address the kernel mode layer vulnerability.
470.182.03 (for 470 branch) | 515.105.01 (for 515 branch) | 525.105.17 (for 525 branch) | 530.41.03 (for 530 branch)
- Identify current NVIDIA driver version using 'nvidia-smi' or system display settings
- Determine which driver branch (470, 515, 525, or 530) is installed
- Download the appropriate fixed driver version from NVIDIA's official website: 470.182.03, 515.105.01, 525.105.17, or 530.41.03
- Install the driver following NVIDIA's standard installation procedure for your operating system
- Reboot the system to load the new driver
- Verify the installed version matches the expected fixed release using 'nvidia-smi'
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Gpu Display Driver
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.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 $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-0199 — 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-0199 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