dbcve.org
AndroidOperating system · Google

CVE-2026-0095

HIGH · 8.0 CVSS v3.1 Published 2026-06-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
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 l2c_fcr_clone_buf of l2c_fcr.cc, there is a possible way to trigger controlled heap corruption within the privileged Bluetooth process due to an integer overflow. 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

An integer overflow vulnerability exists in the l2c_fcr_clone_buf function within the Bluetooth stack (l2c_fcr.cc). The overflow allows controlled heap corruption in the privileged Bluetooth process, enabling local privilege escalation without user interaction.

MitigationImplement proper integer overflow validation on buffer size calculations in l2c_fcr_clone_buf before memory allocation operations; ensure all arithmetic involving buffer lengths is validated against maximum allowable sizes.

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:= 14.0= 15.0= 16.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
Adjacent
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:L/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. Check Android OS version
    Navigate to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shell
    Affected if Version equals 14.0, 15.0, or 16.0 exactly (the affected versions listed)
  2. Confirm Bluetooth hardware is present
    Check if the device has Bluetooth capability via Settings > Bluetooth, or run 'getprop ro.bluetooth.library.name' via ADB to verify the Bluetooth stack is available
    Affected if Bluetooth stack is present on the device
  3. Verify L2CAP Flow Control Reassemble functionality exists
    This is an internal component of the Android Bluetooth stack (l2c_fcr.cc) handling L2CAP FCR operations - it cannot be disabled or verified through user-accessible settings
    Affected if Bluetooth is available on a device running an affected Android version

A device is affected if it runs Android version 14.0, 15.0, or 16.0 and has Bluetooth hardware present, as the integer overflow exists in the l2c_fcr_clone_buf function within the L2CAP Flow Control Reassemble implementation in the Bluetooth stack.

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

Implement proper integer overflow validation on buffer size calculations in l2c_fcr_clone_buf before memory allocation operations; ensure all arithmetic involving buffer lengths is validated against maximum allowable sizes.

Recommended fix Moderate confidence

Android 14.0, 15.0, and 16.0 with the latest security patch level (check Android Security Bulletins for the specific patch date containing this fix)

  1. Check the Android Security Bulletin for the month this CVE was patched to identify the specific security patch level containing the fix
  2. Apply the latest Android security update for your device (Settings > Security > Security update > Check for update)
  3. Verify the patch level matches or exceeds the security patch level that addresses CVE-2026-0095
  4. For enterprise or managed devices, ensure mobile device management (MDM) policies push the latest security patches
Caveat Standard Android security updates are cumulative and typically do not introduce breaking changes; ensure device compatibility before broad deployment in enterprise environments

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

Fix this in Android Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing16.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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