CVE-2025-33218
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 (nvlddmkm.sys), where an attacker could cause an integer overflow. A successful exploit of this vulnerability might lead to code execution, escalation of privileges, data tampering, denial of service, 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 confidenceNVIDIA GPU Display Driver for Windows (nvlddmkm.sys) contains an integer overflow vulnerability in the kernel mode layer. An attacker who gains local access could trigger the overflow, potentially achieving code execution with kernel-level privileges, causing denial of service, or enabling further system compromise.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- 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 GPU Display Driver is installedOpen Device Manager, expand 'Display adapters', and look for NVIDIA GPU entries. Alternatively, run 'driverquery /v | findstr nvlddmkm' to list the driver.Affected if NVIDIA GPU Display Driver is present on the system
-
Locate the nvlddmkm.sys driver fileSearch for nvlddmkm.sys in the C:\Windows\System32\Drivers\ directory or check the driver store: C:\Windows\System32\DriverStore\FileRepository\Affected if The driver file exists on the system
-
Retrieve the driver file versionRight-click the nvlddmkm.sys file, select Properties, then view the Details tab for File Version. Or run 'wmic datafile where name="C:\\Windows\\System32\\Drivers\\nvlddmkm.sys" get Version'Affected if The driver version matches or falls within the known vulnerable version ranges for this CVE
-
Check if the kernel mode driver is loadedOpen an elevated command prompt and run 'sc query nvlddmkm' or check under System Information > Software Environment > Drivers to confirm the driver is loaded.Affected if The nvlddmkmkm driver is currently loaded in kernel mode, making the vulnerability exploitable if the version is vulnerable
-
Verify local user access contextReview which user accounts have interactive logon access to the system using 'query user' or by checking Remote Desktop settings and local user group memberships.Affected if Untrusted or unprivileged users have local access to the system, increasing the attack surface for this local privilege escalation flaw
The system is affected if NVIDIA GPU Display Driver with nvlddmkm.sys is installed with a version that falls within the vulnerable version range, and the driver is loaded with local user access present.
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.
From vendor dataApply the latest NVIDIA GPU display driver patch from the official NVIDIA security bulletin. Prioritize systems with direct user access or those exposed to untrusted GPU workloads.
- Consultation2.0 h
- Implementation3.0 h
- Testing4.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2025-33218 — 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-2025-33218 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