dbcve.org
AndroidOperating system · Google

CVE-2026-0106

CRITICAL · 9.3 CVSS v3.1 Published 2026-02-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
98/100
Remediation priority · Urgent
No privileges 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
In vpu_mmap of vpu_ioctl, there is a possible arbitrary address mmap due to a missing bounds check. 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 confidence

A missing bounds check in the vpu_mmap function of the VPU (Video Processing Unit) driver allows an attacker to map arbitrary physical addresses into user space. This enables local privilege escalation as the attacker can manipulate kernel memory through the mmap interface without requiring any user interaction or additional execution privileges.

MitigationApply the vendor-provided patch that adds proper bounds validation to ensure only legitimate VPU memory regions can be mapped via mmap. Restrict access to the VPU device node (/dev/video* or equivalent) to trusted users until the patch is 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
AndroidOperating system
Affected:all versions

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
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/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 VPU device node
    Locate the VPU device node in /dev/ - common paths include /dev/video*, /dev/vpu, /dev/ion, or vendor-specific paths like /dev/video/.*. Use 'ls -la /dev/video* 2>/dev/null' or search for vpu in /dev/.
    Affected if A VPU device node exists and is accessible to the current user context.
  2. Check device node permissions
    Run 'ls -la' on the identified VPU device node to inspect permissions. If the device is world-readable/writable (mode 666) or group-readable/writable without trusted group membership, untrusted users can access it.
    Affected if The device node has permissions allowing access by untrusted users (e.g., mode 666, 660 with untrusted secondary groups).
  3. Confirm VPU driver is loaded
    Check if the VPU kernel driver is loaded by examining /proc/modules for vpu-related modules, or check /sys/module/ for vpu entries. Commands: 'lsmod | grep -i vpu' or 'ls /sys/module/ | grep -i vpu'.
    Affected if The VPU driver module is loaded into the kernel.
  4. Verify mmap capability exists
    Test whether the VPU device supports mmap by examining the driver internals if accessible, or by checking if the device node responds to mmap operations. This typically requires source code review of the vendor VPU driver.
    Affected if The VPU driver implements the mmap function handler, indicating the attack surface is present.

A user is affected if they have access to an accessible VPU device node (/dev/video* or equivalent) on an unpatched Android system where the VPU driver with the vulnerable vpu_mmap function is loaded.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-provided patch that adds proper bounds validation to ensure only legitimate VPU memory regions can be mapped via mmap. Restrict access to the VPU device node (/dev/video* or equivalent) to trusted users until the patch is applied.

Recommended fix Moderate confidence
  1. 1. Identify your Android device's current Security Patch Level via Settings > About Phone > Android Security Patch Level
  2. 2. Check the Android Security Bulletin for the month when this vulnerability was addressed - monitor source.android.com for the specific patch release notes
  3. 3. Apply the latest available Android Security Update for your device via Settings > System > System Update > Check for Updates
  4. 4. If your device manufacturer has not released a patch addressing this vulnerability, consider restricting access to untrusted apps and avoiding side-loading applications from unknown sources
  5. 5. For enterprise/managed devices, apply the corresponding Android Enterprise security recommendations and consider MDM policies to limit app permissions
Caveat Device must receive vendor-specific security update; many older Android devices may not receive patches for kernel driver vulnerabilities

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Android Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,120
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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