CVE-2025-36934
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 bigo_worker_thread of private/google-modules/video/gchips/bigo.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 bigo_worker_thread function of the bigo.c driver (private/google-modules/video/gchips/bigo.c) creates a use-after-free vulnerability. An attacker with local access can exploit this race to achieve privilege escalation without requiring user interaction or additional 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.
-
Confirm the bigo driver is present on the deviceCheck if the bigo kernel module exists or is built into the running kernel. On Android, examine /proc/modules for 'bigo' or check /sys/module/ for a bigo directory. Alternatively, look for the driver in /dev/ or through 'lsmod' if the module is loaded.Affected if The bigo driver is loaded or built into the kernel and the device is running any unpatched Android version.
-
Identify the Android system versionRun 'getprop ro.build.version.release' or check Settings > About Phone > Android version to determine the installed Android release.Affected if The Android version is any release and no vendor patch for this CVE has been applied.
-
Check if the device receives vendor security updatesVerify the last security patch level by running 'getprop ro.build.version.security_patch' or checking Settings > About Phone > Security patch level.Affected if The security patch level is earlier than the date when Google released the fix for CVE-2025-36934.
-
Determine if bigo_worker_thread is reachableExamine if any application or service actively uses video/GChips functionality that would trigger the bigo driver worker thread. Check running processes and any video capture or Google Chips-related services.Affected if The bigo driver is loaded and actively handling worker thread operations, enabling the race condition window.
The environment is affected if the bigo driver is present on the Android device and the installed Android version or security patch level predates the vendor fix for this race condition vulnerability.
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 patch to fix the race condition in the bigo driver, likely involving proper synchronization primitives around the freed memory access.
- 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-2025-36934 — 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-2025-36934 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