dbcve.org
Use After FreeWeakness · CWE-416

CVE-2026-41158

HIGH · 7.8 CVSS v3.1 Published 2026-06-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

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 GPU system calls to write to arbitrary freed physical pages. Physical memory allocated and freed, without the deferred free mechanism can lead to those resources being used for read/write by the GPU after the kernel module has freed the resource.

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 GPU driver vulnerability where physical memory pages are freed by the kernel module without using deferred free mechanisms, allowing non-privileged users to conduct GPU system calls that can read from or write to these now-freed physical pages. This represents a use-after-free condition at the physical memory level, enabling potential privilege escalation and arbitrary memory corruption.

MitigationImplement proper deferred free mechanisms in the GPU kernel module to ensure physical memory pages are not accessible to userspace after being freed, or apply vendor-provided driver patches that address this memory management flaw.

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 checks

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

  1. Identify the GPU hardware and driver in use
    Run 'lspci | grep -i vga' or 'lspci | grep -i display' to list GPU hardware, then check the loaded kernel driver with 'ls -la /sys/bus/pci/drivers/' or 'lsmod | grep -i video'
    Affected if A GPU driver is loaded but its version cannot be determined or is unknown
  2. Determine the installed GPU driver version
    For NVIDIA: run 'nvidia-smi' or check 'cat /proc/driver/nvidia/version'. For AMD: run 'lsmod | grep amdgpu' and check driver version via 'modinfo amdgpu'. For Intel: check 'modinfo i915'
    Affected if The driver version is older than the version that addresses this CVE (as indicated by vendor security advisories)
  3. Verify if non-privileged users can access GPU system calls
    Check /dev/dri/* permissions with 'ls -la /dev/dri/*' and verify group membership. Also check if GPU acceleration is available to standard users by testing with a non-root account
    Affected if Non-privileged users have direct access to GPU device nodes and can execute GPU-related system calls
  4. Check for GPU memory management configuration
    Inspect kernel module parameters for memory handling: 'cat /sys/module/*/parameters/*' (where * matches your GPU driver). Look for parameters related to memory allocation, paging, or deferred free mechanisms
    Affected if The driver lacks deferred free mechanism parameters or uses immediate page freeing
  5. Review kernel logs for GPU memory-related errors
    Run 'dmesg | grep -iE "(gpu|nvidia|amd|intel|i915|amdgpu)" | tail -50' to check for any memory management warnings, use-after-free indicators, or driver-specific error messages
    Affected if Kernel logs show memory corruption, use-after-free warnings, or unexpected driver behavior related to physical page management

Your environment is affected if you are running a GPU driver whose version is older than the patched version AND non-privileged users have access to GPU system calls, allowing them to potentially exploit the use-after-free condition in physical memory management.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper deferred free mechanisms in the GPU kernel module to ensure physical memory pages are not accessible to userspace after being freed, or apply vendor-provided driver patches that address this memory management flaw.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-41158 — 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-41158 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