CVE-2024-0107
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 user mode layer, where an unprivileged regular user can cause an out-of-bounds read. A successful exploit of this vulnerability might lead to code execution, denial of service, escalation of privileges, 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 a vulnerability in the user mode layer where an unprivileged regular user can cause an out-of-bounds read. This memory safety flaw could potentially be leveraged to achieve code execution, denial of service, privilege escalation, information disclosure, or 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>= 470, < 475.14>= 555, < 556.12>= 535, < 538.78>= 550, < 552.74< 13.12>= 14.0, < 16.7>= 17.0, < 17.3all versionsCVSS 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.
-
Check NVIDIA GPU Display Driver version on WindowsOpen Device Manager, expand Display Adapters, right-click the NVIDIA GPU, select Properties, go to the Driver tab, and note the Driver Version field. Alternatively, run 'nvidia-smi' in Command Prompt if available, and read the Driver Version from the output.Affected if The displayed version falls within any of these ranges: 470.x to 475.13, 535.x to 538.77, 550.x to 552.73, or 555.x to 556.11
-
Identify if NVIDIA Virtual GPU software is installedOpen Programs and Features in Control Panel and look for entries named 'NVIDIA Virtual GPU Manager' or similar NVIDIA virtualization software. Check the Windows Services list for NVIDIA-related virtual GPU services.Affected if The installed Virtual GPU version is lower than 13.12, between 14.0 and 16.6 inclusive, or between 17.0 and 17.2 inclusive
-
Check for NVIDIA Cloud Gaming installationOpen Programs and Features and look for 'NVIDIA GeForce NOW' or 'NVIDIA Cloud Gaming' in the installed programs list. Also check for any NVIDIA cloud gaming service running in the background.Affected if Any version of NVIDIA Cloud Gaming is installed, as all versions are affected according to the provided version data
-
Verify the specific driver componentConfirm the driver is the Windows display driver component. In Device Manager, ensure the driver provider is listed as NVIDIA and the driver date corresponds to the version range being checked.Affected if The driver is confirmed as NVIDIA's display driver for Windows and the version matches the affected ranges listed
A user is affected if their NVIDIA GPU Display Driver version (on Windows) is between 470-475.13, 535-538.77, 550-552.73, or 555-556.11; OR if NVIDIA Virtual GPU version is below 13.12, between 14.0-16.6, or between 17.0-17.2; OR if any version of NVIDIA Cloud Gaming is installed.
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 · scoped13.1216.717.3
Apply the latest NVIDIA GPU Display Driver update from NVIDIA's official drivers page. Prior to deployment in production environments, validate driver compatibility with critical GPU-dependent applications.
Gpu Display Driver: 475.14+ (470 branch), 538.78+ (535 branch), 552.74+ (550 branch), 556.12+ (555 branch) | Virtual GPU: 13.12+, 16.7+, 17.3+ | Cloud Gaming: Contact NVIDIA
- Identify the currently installed NVIDIA GPU driver version by opening NVIDIA GeForce Experience and checking the Driver Version, or running 'nvidia-smi' in command prompt
- Determine which driver branch you are currently on (470, 535, 550, or 555 series) based on the first three digits of your version number
- For Gpu Display Driver: If on 470 series, upgrade to version 475.14 or later; if on 535 series, upgrade to version 538.78 or later; if on 550 series, upgrade to version 552.74 or later; if on 555 series, upgrade to version 556.12 or later
- For Virtual GPU: If affected version is before 13.12, upgrade to 13.12 or later; if between 14.0 and 16.7, upgrade to 16.7 or later; if between 17.0 and 17.3, upgrade to 17.3 or later
- For Cloud Gaming: Contact NVIDIA for specific guidance as no fixed version is listed in the advisory; consider disabling the service as a temporary mitigation if possible
- Download the appropriate driver from nvidia.com/drivers or use GeForce Experience to receive the patched driver automatically
- Restart the system after installing the driver update to ensure the vulnerability is fully remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.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,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-0107 — 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-2024-0107 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