CVE-2026-0106
Arbitrary Address mmap Vulnerability in vpu_ioctl Enables Privilege Escalation
Publication date: 2026-02-05
Last updated on: 2026-02-19
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-125 | The product reads data past the end, or before the beginning, of the intended buffer. |
| CWE-119 | The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data. |
| CWE-787 | The product writes data past the end, or before the beginning, of the intended buffer. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in the vpu_mmap function of vpu_ioctl, where a missing bounds check allows for a possible arbitrary address memory mapping (mmap).
Because of this flaw, an attacker can perform a local escalation of privilege without needing any additional execution privileges or user interaction.
How can this vulnerability impact me? :
The vulnerability can lead to a local escalation of privilege, meaning an attacker with local access could gain higher privileges on the affected system.
This can result in full control over the system, including the ability to read, modify, or delete sensitive data, install malicious software, or disrupt system operations.
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