CVE-2026-0163
published 2026-08-04CVE-2026-0163: In multiple functions of vpu_ioctl.c, there is a possible use after free due to a use after free. This could lead to remote escalation of privilege with no…
PriorityP358critical9.8CVSS 3.1
AVNACLPRNUINSUCHIHAH
EPSS
0.52%
42.8th percentile
In multiple functions of vpu_ioctl.c, there is a possible use after free due to a use after free. This could lead to remote escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
Affected
1 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| android | — | — |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
In multiple functions of vpu_ioctl.c, there is a possible use after free due to a use after free.
ghsa_unreviewed·2026-08-04
CVE-2026-0163 [CRITICAL] CWE-416 In multiple functions of vpu_ioctl.c, there is a possible use after free due to a use after free.
In multiple functions of vpu_ioctl.c, there is a possible use after free due to a use after free. This could lead to remote escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
VulDB
Google Android VPU vpu_ioctl.c use after free
vuldb·2026-08-04·CVSS 9.8
CVE-2026-0163 [CRITICAL] Google Android VPU vpu_ioctl.c use after free
A vulnerability classified as very critical has been found in Google Android. Affected is an unknown function of the file vpu_ioctl.c of the component VPU. Performing a manipulation results in use after free.
This vulnerability was named CVE-2026-0163. The attack may be initiated remotely. There is no available exploit.
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
2026-08-04
Published