CVE-2026-25270: Android Camera driver memory corruption in command buffer processing

CVE-2026-25270 · Severity: medium · CVSS 6.7 · Published 2026-10-06

The Android Camera driver contains a memory corruption vulnerability when processing command buffer requests with invalid length parameters. An attacker with local access to the device could exploit this flaw to corrupt memory, potentially leading to a device crash or arbitrary code execution with elevated privileges.

Technologies: Google Android. Vendors: Google.

Quick answers

Is CVE-2026-25270 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-25270 being exploited in the wild.
How severe is CVE-2026-25270?
Medium severity, with a CVSS score of 6.7, published 6 October 2026.
Which products and versions are affected?
Google Android.
Is there a fix for CVE-2026-25270?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-25270 attacked?
It is attacked with local access, in an operating system.
Am I affected by CVE-2026-25270?
Check whether you run Google Android. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability exists in the Android Camera driver's handling of command buffer requests where invalid length parameters are not properly validated before processing. This leads to out-of-bounds memory access or buffer overflow conditions. Exploitation requires local access to the camera device interface.

Affected products

  • Google Android

Timeline

  • 2026-10-06: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.