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.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 15, 16, 16-qpr2, 17
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 15, 16, 16-qpr2, 17.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 0/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Fix
- Fixed in 15, 16, 16-qpr2, 17
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
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.
Read the original 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
Upgrade to a fixed version: 15, 16, 16-qpr2, 17.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Google Android
17, 16-qpr2, 16, 15
Evidence 1
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-58926
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: source.android.com
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: source.android.com
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: source.android.com
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: cve.now feed data