Skip to main content
← Vulnerabilities

The vulnerability is a heap out-of-bounds read in the EVS HAL's `getStreamList()` method.

Affects Google Android's EVS HAL getStreamList() method, fixed in Android 14, 15, 16, 16-qpr2 and 17.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

—Not rated
Exploited
No known exploitation
Fix
Fixed in 14, 15, 16, 16-qpr2, 17
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 14, 15, 16, 16-qpr2, 17.

Published
Last modified
Published
Not listed in CISA KEV
0/100 · provisional
Unclear
Fix
Fixed in 14, 15, 16, 16-qpr2, 17
None on Exploit-DB, Metasploit or GitHub

Summary

The affected software is the Exposure Video Service (EVS) hardware abstraction layer in Android, which handles camera stream enumeration. An attacker who can supply crafted camera metadata could trigger an out-of-bounds read in the HAL process's memory, potentially leaking sensitive information such as pointers and buffer handles.

Read the original description

The vulnerability is a heap out-of-bounds read in the EVS HAL's `getStreamList()` method. An attacker can craft a `CameraDesc.metadata` byte array, which is parsed without validation, leading to an out-of-bounds read at an attacker-controlled offset within the HAL process's heap. The read data is then exfiltrated back to the attacker, potentially leaking sensitive information like pointers and buffer handles.

What to do

  • Upgrade to a fixed version: 14, 15, 16, 16-qpr2, 17.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • Google Android

    17, 16-qpr2, 16, 15, 14

Evidence 1

  1. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

FAQ

Questions about CVE-2026-58924

What does this mean?

The EVS HAL's getStreamList() method reads memory past the end of a heap buffer. The advisory classifies the impact as information disclosure.Source: source.android.com

Am I affected, and how do I check?

The checked facts do not list affected version ranges, only the versions that carry the fix: Android 14, 15, 16, 16-qpr2 and 17. To check a device, open Settings > About phone and read the Android version and security patch level.Source: source.android.com

What should I do about it?

Update the device to an Android build that includes the fix, starting from Android 14, 15, 16, 16-qpr2 or 17, and install the latest security patch.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