dbcve.org
AndroidOperating system · Google

CVE-2025-36893

MEDIUM · 5.5 CVSS v3.1 Published 2025-09-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/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 ReadTachyonCommands of gxp_main_actor.cc, there is a possible information leak due to uninitialized data. This could lead to local information disclosure 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 · high confidence

An uninitialized data read vulnerability exists in the ReadTachyonCommands function within gxp_main_actor.cc. The function reads uninitialized memory contents, allowing a local attacker to potentially disclose sensitive information from heap or stack memory without requiring any special privileges or user interaction.

MitigationInitialize all data structures and variables in the ReadTachyonCommands function before use. Apply vendor patches when available.

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

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 Google Android is in use
    Check system properties or /system/build.prop for 'ro.build.fingerprint' containing 'android' or 'Google' to confirm the device runs Google Android OS
    Affected if The device does not run Google Android OS - this vulnerability only affects Google Android
  2. Identify the gxp_main_actor component
    Search the filesystem for files named 'gxp_main_actor.cc' or libraries that may contain the ReadTachyonCommands function. Check /system/lib or /vendor/lib directories for relevant libraries
    Affected if The vulnerable component (gxp_main_actor.cc or associated binaries) is not present on the device
  3. Check if ReadTachyonCommands is accessible
    Examine whether the binary or library containing ReadTachyonCommands is loaded or executable on the system. This may require examining system logs or /proc/mounts for mounted partitions
    Affected if The component exists on the system and is loaded or executable

The environment is affected if the device runs Google Android and contains the vulnerable gxp_main_actor component with the ReadTachyonCommands function, which applies to all versions of Google Android as specified in the affected products.

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

Initialize all data structures and variables in the ReadTachyonCommands function before use. Apply vendor patches when available.

Recommended fix Moderate confidence

Android Security Patch Level containing CVE-2025-36893 fix (check Android Security Bulletins)

  1. 1. Check the Android Security Bulletin for the month this vulnerability was patched (CVE-2025-36893)
  2. 2. Identify the Security Patch Level (SPL) that includes the fix for this CVE
  3. 3. Verify your device's current Security Patch Level in Settings > About Phone > Security Patch Level
  4. 4. Update your device to a build that includes the Security Patch Level containing the fix
  5. 5. If your device is no longer receiving monthly security updates, consider upgrading to a device that receives regular security patches
Caveat Monthly security updates vary by device manufacturer; not all Android devices receive timely patches

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

Fix this in Android Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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