dbcve.org
AndroidOperating system · Google

CVE-2024-25985

HIGH · 8.4 CVSS v3.1 Published 2024-03-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
89/100
Remediation priority · High
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 bigo_unlocked_ioctl of bigo.c, there is a possible UAF 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 Use-After-Free vulnerability exists in the bigo_unlocked_ioctl function of the bigo.c kernel driver due to a missing bounds check. This allows a local attacker to potentially reuse freed memory and escalate privileges to root without requiring any user interaction or additional privileges.

MitigationApply the vendor-supplied patch which adds proper bounds validation in the bigo_unlocked_ioctl handler to prevent UAF conditions; until a patch is available, consider disabling or restricting access to the affected 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:= 13.0

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Android version is 13.0
    Check the device settings under Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shell
    Affected if The Android version is exactly 13.0 (the only affected version listed)
  2. Identify if the bigo kernel driver is present
    Check for the presence of the bigo driver module or built-in driver. This may appear in kernel module listings, /sys/module/, or within the kernel image itself. On a rooted device, run 'lsmod | grep bigo' or search the kernel config for CONFIG_BIGO if available
    Affected if The bigo kernel driver exists in the system
  3. Confirm bigo_unlocked_ioctl entry point is accessible
    Check if the driver exposes a device node or interface that allows ioctl calls. Look for related device entries in /dev/ or check driver registration status via 'cat /proc/kallsyms | grep bigo_unlocked_ioctl' on a device with debug symbols
    Affected if The ioctl handler function is registered and callable
  4. Determine driver accessibility from user space
    Verify whether the driver is accessible to unprivileged applications. Check file permissions on any associated device nodes (typically /dev/bigo* or similar) using 'ls -la /dev/bigo*' if such nodes exist
    Affected if The driver interface is accessible without elevated privileges

A device is affected if it runs Android 13.0 and contains the bigo kernel driver with an accessible ioctl interface, allowing a local user to trigger the Use-After-Free condition.

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-supplied patch which adds proper bounds validation in the bigo_unlocked_ioctl handler to prevent UAF conditions; until a patch is available, consider disabling or restricting access to the affected driver.

Recommended fix Moderate confidence

Android 14 (or the latest supported Android version with latest security patch level)

  1. 1. Check the Android version currently installed on the device by navigating to Settings > About Phone > Android version
  2. 2. If the device is running Android 13.0, check for available system updates from the device manufacturer
  3. 3. Apply any available security updates or system updates that address the bigo.c driver vulnerability
  4. 4. If no update is available from the device manufacturer, consider upgrading to Android 14 if the device is supported for that upgrade
  5. 5. Verify the patch level after updating: go to Settings > About Phone > Security Patch Level
Caveat Upgrading to a new Android version may cause compatibility issues with some apps or cause data loss if not backed up first; some older devices may not receive the Android 14 upgrade

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

Fix this in Android Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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