CVE-2024-47891
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 · uneditedSoftware installed and run as a non-privileged user may conduct improper GPU system calls to trigger use-after-free kernel exceptions.
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 confidenceA vulnerability in GPU system call handling allows non-privileged users to make improper GPU calls that trigger use-after-free conditions in kernel space, potentially enabling privilege escalation or system crashes.
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 checksWork through these to decide whether this CVE applies to you.
-
Identify GPU hardware presentRun 'lspci | grep -i gpu' or 'ls /dev/dri/* /dev/nvidia* 2>/dev/null' to list GPU devicesAffected if No GPU hardware found means the system is not affected by this GPU-specific vulnerability
-
Determine GPU driver versionFor NVIDIA: run 'nvidia-smi' or 'cat /proc/driver/nvidia/version'; for AMD: run 'modinfo amdgpu' or check /sys/class/drm/card*/device/driver_version; for Intel: check 'modinfo i915'Affected if Driver version is unpatched and matches the vulnerable version range for CVE-2024-47891; compare your version against vendor security advisories for this CVE
-
Verify non-privileged GPU device accessCheck permissions on GPU device nodes: 'ls -la /dev/dri/* /dev/nvidia* /dev/vga* 2>/dev/null' and verify if users in the 'video' or 'render' groups existAffected if Non-privileged users have read/write access to GPU device nodes (e.g., /dev/dri/card*, /dev/nvidia0) without additional group restrictions, making the attack surface accessible
-
Check for GPU-related use-after-free in kernel logsRun 'dmesg | grep -iE "gpu|use.after|nvidia|amdgpu|i915" | tail -50' or check /var/log/kern.log for UAF or memory corruption errors related to GPUAffected if Kernel logs show use-after-free, memory corruption, or OOPS errors mentioning GPU driver functions indicates active exploitation or vulnerable condition
-
Monitor GPU system call activityUse 'auditctl -w /dev/dri -p rwxa' or 'strace -f -e trace=gpu_calls' (if available) to observe which users are making GPU system callsAffected if Non-privileged users are actively making frequent GPU system calls, especially ioctl calls to GPU drivers, increasing the risk of triggering the vulnerability
A system is likely affected if it has GPU hardware with an unpatched driver version and non-privileged users have direct access to GPU device nodes, especially if kernel logs show any GPU-related memory errors.
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 dataApply vendor-provided GPU driver and kernel security patches; consider restricting GPU access or monitoring for anomalous GPU system call patterns until patches are deployed.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-47891 — 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-47891 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