Use-After-Free (UAF) Vulnerability Exists
Source GCVE Database
Not known to be exploited.
Data as of 2 Nov 2026, 22:16 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or noneExploitation evidence
Disclosed: evidence found.
CVE published 2 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| GoogleAndroid | Affected
| Fixed in– |
Description
A Use-After-Free (UAF) vulnerability in the EVS HAL allows a privileged client to free a buffer_handle_t while it is still in use by the producer thread. This race condition can lead to manipulation of freed heap memory and potential leakage of file descriptors from the EVS HAL process.