CVE-2024-47898
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 use-after-free vulnerability exists in GPU system call handling where non-privileged users can trigger the vulnerability through improper GPU system calls, causing kernel exceptions.
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 drivers and softwareList installed GPU drivers using system tools (e.g., 'lsmod' for kernel modules, 'dpkg -l' or 'rpm -qa' for packages, 'lspci | grep -i vga' for hardware). Record vendor, package name, and installed version.Affected if GPU drivers or GPU-related software is installed and the installed version falls within any affected version range for this CVE.
-
Verify GPU system call interface is accessibleCheck if /dev/dri/*, /dev/nvidia*, or similar GPU device nodes exist and are accessible (ls -la /dev/dri/* /dev/nvidia* 2>/dev/null). Determine which user groups have read/write access.Affected if Non-privileged (non-root) users have access to GPU device nodes and can invoke GPU system calls.
-
Review kernel logs for GPU-related exceptionsExamine dmesg, journalctl, or /var/log/kern.log for recent use-after-free errors, kernel panics, or exceptions related to GPU subsystem (grep -i 'gpu\|nvidia\|amd\|intel' /var/log/kern.log or equivalent).Affected if Kernel logs show use-after-free or memory corruption errors in GPU system call handling paths.
-
Check for unprivileged GPU API accessReview GPU runtime configurations (e.g., nvidia-smi -L, clinfo, vulkaninfo) and verify which user accounts can invoke GPU APIs or submit GPU workloads.Affected if Non-root users can submit GPU workloads or invoke GPU system calls without proper privilege separation.
-
Compare installed driver version against vendor advisoriesQuery the GPU driver version (e.g., nvidia-smi, amdgpu-version, cat /sys/class/drm/card0/device/vendor) and cross-reference with vendor security advisories for CVE-2024-47898.Affected if The installed driver version matches the version range identified as vulnerable in vendor security bulletins for this CVE.
The environment is affected if GPU drivers are installed, non-privileged users can access GPU system calls or device nodes, and the installed driver version aligns with the vulnerable version range for this use-after-free flaw.
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-supplied patches for affected GPU drivers and software; monitor for kernel stability issues if no patch is immediately available.
- 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-47898 — 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-47898 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