CVE-2024-47899
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 confidenceNon-privileged user applications can make improper GPU system calls that trigger use-after-free conditions in kernel code, causing kernel exceptions. This is a local privilege escalation and potential denial-of-service vulnerability in GPU driver or related kernel components.
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 installed GPU driver and versionRun 'lspci | grep -i vga' or 'lspci | grep -i gpu' to list GPU hardware, then check the driver in use via 'ls -la /sys/class/drm/card*/device/driver' or 'modinfo <driver_name>'Affected if The driver version matches an unpatched version known to contain this vulnerability (compare against vendor security advisories)
-
Check kernel logs for GPU-related exceptionsRun 'dmesg | grep -iE "(gpu|nvidia|amd|intel|i915|amdgpu|nouveau)" | tail -50' or review /var/log/syslog for use-after-free, NULL pointer dereference, or kernel panic messages related to GPU operationsAffected if Recent kernel exceptions mention GPU driver code with use-after-free conditions or memory corruption errors
-
Verify GPU device permissionsRun 'ls -la /dev/dri/*' or 'ls -la /dev/nvidia*' to check device file ownership and permissionsAffected if GPU device files are readable/writable by non-privileged users without explicit authorization (world-readable or belonging to a group that untrusted users can join)
-
Check for untrusted user access to GPU resourcesReview which users/groups have access to GPU devices via 'getent group video' 'getent group render' and check /etc/security/limits.conf for any GPU-related resource limits applied to unprivileged accountsAffected if Untrusted or non-privileged user accounts have direct access to GPU device files or are members of video/render groups containing GPU devices
-
Review system for recent privilege escalation indicatorsCheck audit logs via 'ausearch -k gpu' or review /var/log/audit/audit.log for suspicious GPU-related system calls from unprivileged processes, and check 'ps aux' for unexpected processes with elevated privileges that may have been obtained via GPU driver exploitationAffected if Audit logs show GPU system calls from unprivileged processes leading to privilege changes, or unexpected processes hold elevated privileges
A system is likely affected if it runs an unpatched GPU driver version and allows non-privileged users direct access to GPU device files, especially if kernel logs show GPU-related use-after-free exceptions.
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 patches for affected GPU drivers and software as soon as available. Until patched, monitor systems for kernel exceptions related to GPU operations and consider restricting untrusted application access to GPU resources.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-47899 — 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-47899 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