CVE-2026-0095: Integer Overflow
In l2cfcrclonebuf of l2cfcr.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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Compensating control
If possible, disable the Bluetooth service or Bluetooth hardware until a vendor patch is available. Restrict which local accounts and processes can interact with the privileged Bluetooth process (e.g., via local access controls, SELinux/AppArmor policies, or limiting group membership) to reduce risk of local exploitation.
- Operational
Limit local user privileges and audit local account activity on affected systems; monitor for indicators of local privilege escalation impacting the Bluetooth process and apply vendor updates or patches as soon as they become available.
Event History
Frequently Asked Questions
What is the severity of CVE-2026-0095?
CVE-2026-0095 has a severity rating of high, with a CVSS score of 8.
How do I fix CVE-2026-0095?
To address CVE-2026-0095, update your Google Android software to the latest version provided by the vendor.
What systems are affected by CVE-2026-0095?
CVE-2026-0095 affects Google Android devices using the Bluetooth stack.
What kind of vulnerability is CVE-2026-0095?
CVE-2026-0095 is identified as an integer overflow vulnerability that can lead to controlled heap corruption.
Can CVE-2026-0095 be exploited without user interaction?
Yes, CVE-2026-0095 can be exploited locally without needing any user interaction.