dbcve.org
Use After FreeWeakness · CWE-416

CVE-2024-0147

MEDIUM · 5.5 CVSS v3.1 Published 2025-01-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

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 · unedited
NVIDIA GPU display driver for Windows and Linux contains a vulnerability where referencing memory after it has been freed can lead to denial of service or 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 confidence

Use-after-free vulnerability in NVIDIA GPU display drivers for Windows and Linux allows attackers to reference freed memory, potentially causing denial of service or data tampering. The vulnerability exists in the display driver component where memory management fails to properly track or invalidate pointers after memory deallocation.

MitigationApply the NVIDIA GPU driver update containing the fix for CVE-2024-0147 once released. Prioritize patching systems with direct GPU access or those running untrusted graphics workloads.

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify NVIDIA GPU driver version on Windows
    Open Device Manager, expand Display adapters, right-click the NVIDIA GPU, select Properties, go to the Driver tab, and record the driver version string.
    Affected if The displayed driver version falls within the affected version range for CVE-2024-0147
  2. Identify NVIDIA GPU driver version on Linux
    Run nvidia-smi or cat /proc/driver/nvidia/version in a terminal to retrieve the installed driver version.
    Affected if The displayed driver version falls within the affected version range for CVE-2024-0147
  3. Confirm display driver component is in use
    On Windows, verify the NVIDIA display driver service is running via Services.msc; on Linux, verify the nvidia kernel module is loaded via lsmod | grep nvidia.
    Affected if The NVIDIA display driver component is actively loaded and in use by the system
  4. Compare version to affected range
    Cross-reference your identified driver version with the official NVIDIA security bulletin for CVE-2024-0147 to determine if your version is within the affected range.
    Affected if Your driver version matches an affected version listed in the CVE-2024-0147 security advisory

A system is affected if it runs an NVIDIA GPU display driver version within the affected range and has the display driver component loaded and active.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the NVIDIA GPU driver update containing the fix for CVE-2024-0147 once released. Prioritize patching systems with direct GPU access or those running untrusted graphics workloads.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-0147 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-0147 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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