CVE-2026-34192
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 cause an error path leading to UAF of GPU page tables. The vulnerability allows physical memory allocated for MMU page tables to be used after being freed. This was caused by an error path that would not cleanup properly before freeing the physical allocation.
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 page table management where an error path triggered by improper GPU system calls from a non-privileged user fails to properly clean up before freeing physical memory allocated for MMU page tables. This allows the freed page table memory to be accessed after deallocation.
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
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/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 and drivers presentRun 'lspci | grep -i gpu' or 'ls -la /dev/dri/*' to list GPU devices and check for GPU driver modules with 'lsmod | grep -i gpu'Affected if GPU hardware and associated drivers are installed on the system
-
Check GPU driver versionFor NVIDIA: 'nvidia-smi' or 'cat /proc/driver/nvidia/version'; For AMD: 'lsmod | grep amdgpu' and check driver version; For Intel: 'lsmod | grep i915' - compare against any vendor advisoriesAffected if The installed GPU driver version is unpatched and matches the vulnerable version range (if known)
-
Verify non-privileged GPU access is possibleCheck /dev/dri/* and /dev/nvidia* permissions with 'ls -la /dev/dri/* /dev/nvidia* 2>/dev/null' - determine if unprivileged users have read/write access to GPU device nodesAffected if Non-privileged (non-root) users have direct access to GPU device files without restrictions
-
Inspect kernel logs for error indicatorsCheck dmesg, journalctl, or /var/log/messages for GPU-related errors: 'dmesg | grep -i -E "(gpu|memory|page.table|mmu|error|fail)"'Affected if System logs show GPU memory management errors or page table allocation failures that may indicate the vulnerable code path
-
Check for GPU system call tracing capabilityReview audit logs if enabled: 'ausearch -sc all | grep -i gpu' or check /var/log/audit/audit.log for GPU system calls from unprivileged processesAffected if Unprivileged processes are making GPU system calls that trigger the error handling path
The environment is affected if GPU hardware with vulnerable drivers is present AND unprivileged users can access GPU device nodes, allowing the error path in page table management to be triggered.
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 dataRestrict or monitor GPU access from untrusted code and apply vendor patches for GPU drivers that address the error handling path in page table cleanup.
- Consultation4.0 h
- Implementation16.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,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-34192 — 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-34192 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