dbcve.org
AndroidOperating system · Google

CVE-2026-0125

HIGH · 7.0 CVSS v3.1 Published 2026-06-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/100
Remediation priority · Elevated
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 multiple functions 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 confidence

A use-after-free vulnerability exists in multiple functions within the VPU (Video Processing Unit) kernel driver (vpu_ioctl.c). The flaw stems from a race condition that allows a local attacker to manipulate memory after it has been freed, potentially achieving privilege escalation without requiring additional execution privileges or user interaction.

MitigationApply the vendor-provided kernel driver patch that addresses the race condition and use-after-free in vpu_ioctl.c, then rebuild and deploy the updated kernel module/driver.

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

CVSS:3.1/AV:L/AC:H/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. Confirm the target system runs Google Android
    Verify the operating system is Google Android (e.g., check system properties, /system/build.prop, or uname -a output)
    Affected if The system is NOT running Google Android - other OSes are not affected by this CVE
  2. Determine if the VPU kernel driver is present
    Check for the presence of the VPU (Video Processing Unit) kernel driver module - look for driver files or kernel module references related to video processing unit (common paths include /system/lib/modules/, /vendor/lib/modules/, or check kernel config for CONFIG_VIDEO_VPU or similar)
    Affected if The VPU driver is NOT present on the system - the vulnerability only applies when this specific driver exists
  3. Identify the VPU driver version
    Query the installed VPU driver version through available system interfaces - this may include checking kernel module info (modinfo), driver sysfs entries, or vendor-specific APIs depending on the device
    Affected if Unable to determine driver version, or version is older than the patched release - the vulnerability exists in all versions per the CVE description
  4. Locate and inspect vpu_ioctl.c in the kernel or driver source
    If kernel source or driver source is accessible, search for vpu_ioctl.c and examine the ioctl functions for race condition handling between memory allocation and free operations (look for missing locking around use-after-free vulnerable code paths)
    Affected if The source file exists and lacks proper synchronization around the memory management operations described in the CVE
  5. Check driver configuration and exposure
    Verify whether the VPU driver is exposed to local users - check device node permissions (/dev/video*, /dev/vpu*), SELinux policies, and whether untrusted local processes can access the driver ioctl interfaces
    Affected if The driver is exposed to untrusted local users without additional sandboxing - the CVE requires local attacker access to exploit the race condition

The system is affected if it runs Google Android AND contains the VPU kernel driver, since the CVE states all Android versions with this driver are vulnerable to the use-after-free race condition in vpu_ioctl.c.

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

Apply the vendor-provided kernel driver patch that addresses the race condition and use-after-free in vpu_ioctl.c, then rebuild and deploy the updated kernel module/driver.

Fix this in Android Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,120
Get help mitigating

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

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