dbcve.org
DdkApplication · Imaginationtech

CVE-2026-34196

HIGH · 7.8 CVSS v3.1 Published 2026-07-10
Fix available
A fix is available. Upgrade to 26.1 or later.
See remediation →
80/100
Remediation priority · High
Zero-click 6 weeks old

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 · unedited
Software installed and run as a non-privileged user may conduct improper GPU system calls to cause an integer overflow and map two GPU virtual addresses to the same physical address. One of these virutal mappings can be freed along with the physical page, allowing for a read/write UAF via the second mapping The second virtual mapping references a physical address that has been freed after the first virtual mapping has been freed. This allows the physical memory to be allocated (for example) by another process and read/written to.

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 confidence

A Use-After-Free (UAF) vulnerability in GPU drivers allows a non-privileged user to trigger improper GPU system calls causing an integer overflow that maps two GPU virtual addresses to the same physical address. When the first virtual mapping is freed, the second mapping retains access to the freed physical memory, which can then be allocated by other processes enabling arbitrary read/write.

MitigationApply vendor-provided GPU driver updates that address the integer overflow in GPU memory mapping. Restrict untrusted users from GPU access until patches are applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
DdkApplication
Affected:< 26.1= 26.1

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify GPU hardware and driver
    Run 'lspci | grep -i vga' or 'lshw -C display' to list GPU hardware. Then check driver version with 'lsmod | grep video' and 'cat /sys/class/drm/card*/device/driver_version' or 'nvidia-smi' for NVIDIA, 'amdgpu-version' for AMD, or 'intel_gpu_top' for Intel.
    Affected if The driver version cannot be compared to a fixed safe version (no patch available or version unknown)
  2. Check GPU device permissions
    Run 'ls -la /dev/dri/*' and 'getent group video' to see which users and groups have access to GPU device nodes.
    Affected if Users outside a trusted admin group (like 'video' or 'render' group) have access to /dev/dri/* or GPU compute nodes
  3. Verify user namespace isolation for GPU
    Check if unprivileged user namespaces are restricted with 'cat /proc/sys/kernel/unprivileged_user_namespace_restricted' (1 = restricted, 0 = allowed). Also check for GPU access control lists or cgroups.
    Affected if Unprivileged user namespaces are allowed (value is 0) and untrusted users can access GPU resources
  4. Check for GPU memory mapping exposure
    Review system logs (journalctl, dmesg) for GPU driver warnings related to memory mapping, address conflicts, or integer overflow errors. Search with 'dmesg | grep -i gpu' and 'dmesg | grep -i address'.
    Affected if GPU driver logs show warnings about memory mapping errors, address collisions, or suspected integer overflows in GPU page tables
  5. Audit GPU compute job access
    Check if untrusted/local users can submit GPU compute jobs via 'slurm', 'docker --gpus', or similar job schedulers. Review /etc/security/limits.conf and cgroup settings for GPU resource access.
    Affected if Non-admin users can submit jobs that directly invoke GPU system calls or memory allocation

The environment is affected if a GPU driver is in use AND untrusted or non-privileged users have direct or indirect access to GPU device nodes, as the vulnerability requires a non-privileged user to trigger the improper GPU system calls.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 26.1 or later
Fixed in 26.1
Interim mitigation

Apply vendor-provided GPU driver updates that address the integer overflow in GPU memory mapping. Restrict untrusted users from GPU access until patches are applied.

Fix this in Ddk Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing16.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,760
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-34196 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-34196 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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