Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Fri, 17 Apr 2026 23:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Local Privilege Escalation via Arbitrary mmap in Android vpu_ioctl |
Thu, 12 Feb 2026 18:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
Tue, 10 Feb 2026 17:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:o:google:android:-:*:*:*:*:*:*:* |
Fri, 06 Feb 2026 12:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Google
Google android |
|
| Vendors & Products |
Google
Google android |
Fri, 06 Feb 2026 00:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
Thu, 05 Feb 2026 21:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-119 CWE-125 CWE-787 |
|
| Metrics |
cvssV3_1
|
Thu, 05 Feb 2026 20:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | In vpu_mmap of vpu_ioctl, there is a possible arbitrary address mmap due to a missing bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation. | |
| References |
|
Status: PUBLISHED
Assigner: Google_Devices
Published:
Updated: 2026-02-26T15:04:17.593Z
Reserved: 2025-10-23T08:42:57.001Z
Link: CVE-2026-0106
Updated: 2026-02-05T20:40:40.613Z
Status : Modified
Published: 2026-02-05T21:15:52.597
Modified: 2026-02-19T18:24:53.930
Link: CVE-2026-0106
No data.
OpenCVE Enrichment
Updated: 2026-04-17T23:00:12Z