CVE-2026-34195
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 intentional GPU sparse memory API calls to cause out of bounds write in the kernel. The product incorrectly indexes internal state when performing sparse allocation remapping.
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 GPU driver vulnerability allows non-privileged users to trigger incorrect indexing during sparse allocation remapping through intentional sparse memory API calls, resulting in out-of-bounds kernel writes that could enable local privilege escalation.
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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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 -v | grep -i vga' or 'cat /proc/driver/nvidia/version' (for NVIDIA), 'cat /sys/class/drm/card*/device/driver' for AMD/Intel, or check vendor-specific tools like 'amdvlk64 --version' or 'intel_gpu_top'Affected if Unable to determine driver version or version falls within an unpatched range for the specific GPU vendor
-
Verify sparse memory API availabilityCheck if sparse memory or migration features are exposed: look for 'capable' flags in /sys/class/drm/*/device or check driver module parameters with 'modinfo <driver_name>' for sparse-related optionsAffected if Sparse memory API or migration capabilities are exposed and accessible to user-space applications
-
Check GPU device file permissionsRun 'ls -la /dev/dri/*' or 'ls -la /dev/nvidia*' to list GPU device files and their permission bitsAffected if GPU device files are readable/writable by non-root users or belong to groups that non-privileged users can join
-
Audit user access to GPU resourcesCheck which users have access to video/ rendering groups: 'getent group video' or 'getent group render' and review /etc/security/limits.conf for any GPU-specific resource limitsAffected if Non-privileged users are members of video/render groups or have direct access to GPU device nodes without restrictions
-
Inspect sparse allocation usageMonitor for sparse allocation ioctls or API calls using 'auditctl' rules (e.g., 'auditctl -w /dev/dri/card0 -p rwxa') or check dmesg for sparse memory-related kernel messagesAffected if Sparse memory operations are being invoked from user-space processes without mediation
If unprivileged users have direct access to GPU device nodes with sparse memory API capabilities and the driver version is unpatched, the system is vulnerable to local privilege escalation via out-of-bounds kernel writes.
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 security patches for the affected GPU driver; until patched, restrict or monitor unprivileged user access to GPU resources.
- 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-2026-34195 — 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-2026-34195 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