Integer overflow in Google Android

CVE-2026-0095

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.

Vulnerability class: Integer Overflow

Published · last modified .

CVSS v3 metric

CVSS v3 base score 8.0 (High). Vector: CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.

EPSS exploit prediction

EPSS: 0.001 (1.0th percentile), scored .

Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 1st percentile — 1.0% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.

EPSS trend (30 days)EPSS over the last 30 days for CVE-2026-0095: held from 0.001 to 0.001.

EPSS over last 30 days · oldest: 0.001 · newest: 0.001 · change: 0.000

Affected products

Weakness classification (CWE)

References

Frequently asked questions

What is CVE-2026-0095?
CVE-2026-0095 is a high-severity vulnerability in Google Android, classified under Integer Overflow or Wraparound. CVSS score: 8.0/10. Published 2026-06-01.
How severe is CVE-2026-0095?
High severity. CVSS v3 base score is 8.0 out of 10.