CVE-2026-0112
Use-After-Free in vpu_ioctl.c Causes Local Privilege Escalation
Publication date: 2026-03-10
Last updated on: 2026-03-11
Assigner: Google Devices
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| android | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-416 | The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer. |
| CWE-362 | The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability occurs in the vpu_open_inst function within the vpu_ioctl.c file, where a race condition can cause a use after free error.
A use after free means that the program tries to use memory after it has been freed, which can lead to unpredictable behavior or exploitation.
How can this vulnerability impact me? :
This vulnerability could allow a local attacker to escalate their privileges without needing any additional execution privileges.
Exploitation does not require any user interaction, making it potentially easier for an attacker to leverage.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
I don't know