dbcve.org
Race ConditionWeakness · CWE-362

CVE-2024-47892

HIGH · 7.8 CVSS v3.1 Published 2024-12-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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 GPU system calls to read and write freed physical memory from the GPU.

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

A vulnerability in GPU system calls allows non-privileged software to read and write freed physical memory from the GPU, potentially enabling privilege escalation or sensitive data exposure.

MitigationApply vendor-provided patches for GPU drivers and associated software components; ensure all affected systems receive the security update.

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 checks

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

  1. Identify GPU hardware present in the system
    Run lspci | grep -i vga or lspci | grep -i gpu to list installed graphics hardware. Note the vendor (NVIDIA, AMD, Intel, etc.) and model.
    Affected if A GPU from any affected vendor is present and the system runs untrusted workloads or allows non-privileged access to GPU resources.
  2. Determine installed GPU driver version
    For NVIDIA: nvidia-smi | grep Driver Version. For AMD: clinfo or cat /sys/class/drm/card0/device/driver_version. For Intel: cat /sys/class/drm/card0/device/uevent shows driver info.
    Affected if The driver version is older than the latest vendor-provided patched version for this CVE.
  3. Check for GPU virtualization or passthrough configuration
    Look for virsh list --all if using libvirt, or check for IOMMU groups: cat /sys/kernel/iommu_groups/*/devices/*/physfn. Also check for nvidia-smi -L or amd-smi list.
    Affected if GPU passthrough or virtualization is enabled, allowing untrusted VMs or containers to access the GPU directly.
  4. Verify GPU memory access permissions
    Check /dev/nvidia* or /dev/dri/* device permissions with ls -la /dev/nvidia* /dev/dri/*. Also check for any user-space GPU compute frameworks (OpenCL, CUDA, Vulkan) accessible to non-privileged users.
    Affected if Non-privileged users have access to GPU device nodes or GPU compute APIs without additional security controls.

You are affected if your system has a GPU and runs untrusted code, containers, or VMs with GPU access while using an unpatched driver version that does not address this memory isolation flaw.

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 vendor-provided patches for GPU drivers and associated software components; ensure all affected systems receive the security update.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-47892 — 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-47892 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