CVE-2025-25177
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 kernel drivers where non-privileged users can make improper GPU system calls that trigger kernel exceptions, leading to memory safety issues in kernel-space GPU handling.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
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 kernel modulesRun 'lsmod | grep -i gpu' or 'lspci -v | grep -A10 VGA' on Linux, or check Device Manager > Display adapters on Windows. Note the driver names (e.g., amdgpu, nvidia, i915, etc.)Affected if GPU kernel drivers are loaded and running in kernel space
-
Check the installed GPU driver versionFor NVIDIA: 'nvidia-smi' or 'cat /proc/driver/nvidia/version'. For AMD: 'lsmod | grep amdgpu' then check /sys/module/amdgpu/version. For Intel i915: 'cat /sys/module/i915/version'. Compare the version string to vendor release notesAffected if The driver version matches any unpatched version range for this CVE (check vendor security advisories)
-
Verify non-privileged user access to GPU devicesRun 'ls -la /dev/dri/*' or 'ls -la /dev/nvidia*' to check device permissions. Run 'groups' for your test user and verify if they have video, render, or docker group membershipAffected if Non-privileged users (outside of root/admin) have direct or group-based access to GPU device nodes
-
Examine kernel logs for GPU-related errorsRun 'dmesg | grep -i -E "(gpu|amdgpu|nvidia|i915)" | tail -50' or check /var/log/kern.log. Look for signs of kernel exceptions, oops, or memory corruption messages tied to GPU operationsAffected if Kernel logs show GPU driver errors, use-after-free traces, or kernel panics related to GPU syscalls since the CVE disclosure date
-
Check for active GPU compute workloadsRun 'ps aux | grep -E "(cuda|opencl|gpu)"' or check running processes using GPU resources via vendor tools (nvidia-smi, rocminfo, etc.)Affected if Non-root users are running compute or graphics workloads that invoke kernel-mode GPU drivers
A user is affected if their system runs a GPU kernel driver that is unpatched for this CVE and permits non-privileged users to execute GPU system calls that could trigger the use-after-free condition.
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/software; consider restricting GPU access or isolating sensitive workloads until patches are deployed.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.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 $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-25177 — 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-2025-25177 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