CVE-2026-22164
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 corrupt kernel heap memory. By creating resources of certain types and presenting a set of parameters to the affected interface the exploit can be used to corrupt kernel memory.
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 vulnerability in GPU system call handling allows non-privileged user-space applications to make improper GPU driver calls that corrupt kernel heap memory. By allocating specific resource types and passing certain parameters to the affected interface, an attacker can trigger memory corruption in the kernel heap.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 softwareRun 'lspci | grep -i gpu' on Linux or check Device Manager on Windows to list GPU hardware and drivers. For software-only GPU virtualization, check installed packages with 'dpkg -l | grep -i gpu' or 'rpm -qa | grep -i gpu' on Linux.Affected if GPU drivers, GPU virtualization software, or GPU-accelerated containers are installed on the system
-
Determine GPU driver versionUse vendor-specific commands: NVIDIA: 'nvidia-smi' or 'cat /proc/driver/nvidia/version'; AMD: 'cat /sys/class/drm/card0/device/version'; Intel: 'cat /sys/class/drm/card0/device/gt_version'. Compare the installed version to any vendor-advisory version ranges once released.Affected if The installed GPU driver version falls within an affected range (when patches are released, vendors will publish specific version numbers)
-
Check GPU interface accessibilityVerify if unprivileged users can access GPU device nodes: 'ls -la /dev/dri/*' on Linux or check permissions via Device Manager. For containerized environments, verify GPU device pass-through configuration with 'docker ps' and 'docker inspect'.Affected if Unprivileged users have direct or indirect access to GPU devices without additional access controls
-
Audit GPU system call activityMonitor for suspicious GPU system calls using auditing frameworks: 'auditd' rules for /dev/dri/* access, or 'strace -f -e ioctl' on known GPU applications. Review logs for repeated ioctl calls with unusual parameters.Affected if Excessive or anomalous GPU ioctl calls are observed from user-space applications, especially those creating unusual resource allocations
The environment is affected if GPU software is installed and unprivileged users can access the GPU interface, as the vulnerability requires making improper GPU system calls to corrupt kernel memory.
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 patches or driver updates for affected GPU hardware. Consider restricting or monitoring GPU resource allocation from untrusted applications until patches are applied.
- 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-22164 — 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-22164 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