dbcve.org
AndroidOperating system · Google

CVE-2026-0064

MEDIUM · 5.5 CVSS v3.1 Published 2026-06-17
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 multiple places, there is a possible persistent denial of service due to resource exhaustion. This could lead to local denial of service 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 local denial of service vulnerability exists in multiple locations due to resource exhaustion. The flaw allows an attacker to consume system resources (memory, file handles, CPU, etc.) without requiring any special privileges or user interaction, causing the affected system or application to become unresponsive or crash.

MitigationImplement proper resource management including explicit limits on resource allocation, thorough cleanup of resources after use, and monitoring/throttling mechanisms to prevent exhaustion. Apply any vendor-provided patches for the affected components.

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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
    Check the device or build settings to confirm the installed Android version is exactly 17.0. On the device, go to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shell.
    Affected if The installed Android version is 17.0 exactly
  2. Identify running system services
    Use 'ps -A' via ADB shell to list all running processes and identify services that may be consuming excessive resources (CPU, memory, file handles). Compare process counts and resource usage against normal baselines.
    Affected if Multiple system services are exhibiting unusually high resource consumption without an identifiable cause
  3. Check for file descriptor exhaustion
    Run 'cat /proc/sys/fs/file-nr' via ADB shell to check allocated versus free file descriptors. Values approaching the limit (typically 65535) indicate potential resource exhaustion.
    Affected if File descriptor usage is approaching system limits with no legitimate explanation
  4. Monitor memory consumption
    Check memory status with 'cat /proc/meminfo' via ADB shell or observe available memory via 'dumpsys meminfo'. Look for abnormally low free memory or high memory pressure.
    Affected if System memory is consistently depleted or memory pressure is elevated without heavy user app usage
  5. Review system crash logs
    Examine /data/logd/logcat or crash dump files in /data/crash_reports for recent entries. Look for patterns of service failures, ANRs (Application Not Responding), or unexpected process terminations.
    Affected if Multiple recent crashes or ANRs are logged, particularly involving system services

The device is affected if it runs Android version 17.0 and exhibits unexplained resource exhaustion symptoms such as high file descriptor usage, memory depletion, or system service crashes.

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

Implement proper resource management including explicit limits on resource allocation, thorough cleanup of resources after use, and monitoring/throttling mechanisms to prevent exhaustion. Apply any vendor-provided patches for the affected components.

Fix this in Android Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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