dbcve.org
DdkApplication · Imaginationtech

CVE-2026-41154

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 cause OOB kernel memory reads or writes through GPU API calls. When indexing pages larger than 4kB in the page freeing logic of the sparse memory implementation, incorrect buffer indexing leads to OOB access.

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 buffer indexing error exists in the sparse memory implementation's page freeing logic when handling pages larger than 4kB. Non-privileged users can trigger out-of-bounds kernel memory reads or writes through GPU API calls due to incorrect buffer calculations when indexing large pages.

MitigationApply vendor-supplied patches for the GPU driver and kernel components addressing the sparse memory page freeing logic. Consider restricting untrusted users' access to GPU APIs until the patch is deployed.

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 installed GPU driver and kernel version
    Run 'lsmod | grep -i gpu' or 'lspci | grep -i vga' to find GPU hardware, then check driver version with 'modinfo <driver_name>' or 'cat /sys/class/drm/*/device/version' if available. Also run 'uname -r' for kernel version.
    Affected if Driver or kernel version falls within known vulnerable ranges (if patches are available, unpatched versions are affected)
  2. Check if large page (huge pages) support is enabled
    Run 'cat /proc/meminfo | grep -i huge' to check for HugePages configured. Also check 'sysctl vm.nr_hugepages' to see if large pages are allocated.
    Affected if Large page support is enabled (vm.nr_hugepages > 0) and the unpatched driver handles these pages incorrectly
  3. Verify GPU API exposure to non-privileged users
    Check permissions on GPU device nodes with 'ls -la /dev/dri/*' or 'ls -la /dev/nvidia*'. Review /etc/security/limits.conf and PAM settings for GPU resource limits.
    Affected if Non-privileged (non-root) users have direct access to GPU device nodes without restrictions
  4. Inspect sparse memory usage in kernel
    Check kernel configuration for CONFIG_SPARSEMEM with 'cat /boot/config-$(uname -r) | grep SPARSEMEM'. Also check for 'cat /sys/kernel/mm/hugepages/' to see hugepage configuration.
    Affected if CONFIG_SPARSEMEM is enabled and large pages (>4KB) are in use
  5. Check for GPU compute API availability
    Look for CUDA, OpenCL, or Vulkan runtime files with 'which nvidia-smi' (for NVIDIA), 'clinfo' (for OpenCL), or check for Vulkan ICD files in /etc/vulkan/icd.d/ and /usr/share/vulkan/icd.d/.
    Affected if GPU compute APIs (CUDA/OpenCL/Vulkan) are exposed and accessible to untrusted users

User is affected if they have an unpatched GPU driver with large page support enabled and untrusted users have access to GPU device nodes or compute APIs.

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-supplied patches for the GPU driver and kernel components addressing the sparse memory page freeing logic. Consider restricting untrusted users' access to GPU APIs until the patch is deployed.

Fix this in Ddk 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 the upgrade done

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-41154 — 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-41154 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