CVE-2026-0112
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 · uneditedIn vpu_open_inst of vpu_ioctl.c, there is a possible use after free due to a race condition. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
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 race condition in the vpu_open_inst function of the VPU (Video Processing Unit) kernel driver causes a use-after-free vulnerability. An attacker with local access can exploit this race to achieve privilege escalation without requiring additional execution privileges.
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 dataall versionsCVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:H/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check for VPU device nodesList contents of /dev directory for video* device files, or check vendor-specific VPU device files typically found in /dev/ (common paths include /dev/video*, /dev/vpu*, /dev/mxc_vpu*, or /dev/galcore depending on SoC vendor)Affected if VPU device nodes exist on the system - the vulnerable driver code path is present and the attack surface is available
-
Verify VPU kernel driver is loadedCheck /proc/modules or use 'lsmod' command to see if any VPU-related kernel modules are loaded (common module names include mxc_vpu, vpu, galcore, or vendor-specific VPU modules)Affected if A VPU kernel module is loaded in memory - the driver containing the vulnerable vpu_open_inst function is active
-
Check kernel/Android versionRun 'uname -a' or check /proc/version to identify the kernel version; check Android build info via 'getprop ro.build.version.release'Affected if The kernel and Android version have not been patched - since all Android versions are affected, any unpatched system is vulnerable
-
Inspect VPU driver for vulnerable functionIf accessible, examine the VPU kernel driver binary/module for the vpu_open_inst function symbol; on rooted devices, strings grep on the driver module or decompile to check for the race-prone code patternAffected if The vpu_open_inst function exists in the loaded driver without the race condition fix - the specific vulnerable code path is present
The system is affected if it has VPU hardware with accessible device nodes and the VPU kernel driver is present without the CVE-2026-0112 patch applied.
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 the vendor-provided security patch to the VPU driver; restrict access to VPU device nodes (/dev/video* or vendor-specific VPU device files) to minimize attack surface until patched.
- Consultation3.0 h
- Implementation6.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,992.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-0112 — 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-0112 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