dbcve.org
Out-of-bounds WriteWeakness · CWE-787

CVE-2024-47897

HIGH · 8.8 CVSS v3.1 Published 2025-01-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
Software installed and run as a non-privileged user may conduct improper GPU system calls resulting in platform instability and reboots.

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

Non-privileged users can make improper GPU system calls that cause platform instability and system reboots, likely due to insufficient permission checks in GPU drivers or related software.

MitigationImplement proper permission validation for GPU system calls and restrict or sandbox GPU access for non-privileged users to prevent abuse.

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
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/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 checks

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

  1. Identify GPU driver installations
    List installed GPU drivers on the system. On Linux, check /var/log/Xorg.0.log for driver info, or run 'lspci | grep -i vga' and 'lsmod | grep -i video'. On Windows, check Device Manager under Display adapters.
    Affected if Any GPU driver from a vendor that has not addressed permission validation in GPU system calls is installed and running.
  2. Check for unprivileged GPU access permissions
    Verify which user accounts or groups have access to GPU device files. On Linux, check /dev/dri/* and /dev/nvidia* permissions with 'ls -la /dev/dri/* /dev/nvidia* 2>/dev/null'. Verify if video group membership is granted to standard users with 'getent group video'.
    Affected if Non-privileged user accounts are members of the video or graphics groups, or device files are world-readable/writable, allowing unprivileged GPU system calls.
  3. Inspect GPU driver configuration files
    Examine GPU driver configuration for permission settings. On Linux, check /etc/X11/xorg.conf and files in /etc/X11/xorg.conf.d/ for any 'Option' directives controlling user privileges. For NVIDIA, check /etc/modprobe.d/ configuration files.
    Affected if Configuration allows unrestricted or unprivileged access to GPU functions without proper permission validation.
  4. Review GPU runtime environment settings
    Check for container GPU runtime configurations (like NVIDIA Container Toolkit or containerd GPU plugins) and system-wide GPU access settings. Look for files like /etc/nvidia-container-runtime/config.toml or equivalent.
    Affected if Container or application runtimes are configured to allow non-privileged containers or users direct access to GPU devices without permission enforcement.
  5. Audit GPU system call access
    Use audit rules or system call tracing (auditd, strace) to monitor GPU-related system calls from non-privileged processes. Check existing audit logs for unusual GPU ioctl calls from unprivileged UIDs.
    Affected if Non-privileged processes are successfully making GPU system calls that should require elevated privileges, evidenced by audit logs or successful execution.

A user is affected if their system runs GPU drivers that permit non-privileged users to execute GPU system calls without proper permission validation, as evidenced by group membership, device permissions, or audit logs showing unprivileged GPU access.

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

Implement proper permission validation for GPU system calls and restrict or sandbox GPU access for non-privileged users to prevent abuse.

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-47897 — 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-47897 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