CVE-2024-0126
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 which could allow a privileged attacker to escalate permissions. 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 and Linux contains a privilege escalation vulnerability that could allow a privileged attacker to gain elevated permissions. The vulnerability affects the driver software and could potentially lead to code execution, denial of service, information disclosure, or data tampering.
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
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/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 NVIDIA GPU Display Driver installationWindows: Run 'nvidia-smi' or check Device Manager > Display adapters. Linux: Run 'lspci | grep -i nvidia' or 'lsmod | grep nvidia'Affected if No NVIDIA GPU display driver is present, then the system is not affected by this CVE.
-
Retrieve installed driver versionWindows: Run 'nvidia-smi' and note the Driver Version field, or check HKLM\SYSTEM\CurrentControlSet\Services\nvlddmkm\Version in Registry. Linux: Run 'nvidia-smi' or 'cat /proc/driver/nvidia/version'Affected if Unable to retrieve a version number means the driver may not be properly installed.
-
Compare version against affected release rangesCross-reference the retrieved driver version with NVIDIA's official security bulletin for CVE-2024-0126 to determine if it falls within the vulnerable version rangeAffected if The installed version is within the vulnerable version range listed in NVIDIA's advisory for this CVE.
-
Verify driver components are loadedWindows: Check that nvlddmkm.sys or nvidia*.sys drivers are loaded via 'sc query nvlddmkm' or Device Manager status. Linux: Verify nvidia kernel modules are loaded via 'lsmod | grep nvidia'Affected if The privilege escalation requires the vulnerable driver component to be actively loaded and running.
A system is affected if it has an NVIDIA GPU Display Driver installed with a version that falls within the vulnerable range specified in NVIDIA's CVE-2024-0126 security advisory.
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 dataUpdate NVIDIA GPU display drivers to the latest version that includes the security patch. Prioritize systems with privileged users or those exposed to higher attack risk.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-0126 — 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-0126 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