CVE-2026-0106

9.3 CRITICAL

πŸ“‹ TL;DR

This vulnerability allows local attackers to map arbitrary memory addresses due to missing bounds checking in the vpu_mmap function. This can lead to local privilege escalation without requiring user interaction. Affects Android devices with vulnerable VPU drivers.

πŸ’» Affected Systems

Products:
  • Android devices with VPU drivers
Versions: Android versions prior to February 2026 security patch
Operating Systems: Android
Default Config Vulnerable: ⚠️ Yes
Notes: Specifically affects Pixel devices and potentially other Android devices using similar VPU implementations.

⚠️ Risk & Real-World Impact

πŸ”΄

Worst Case

Complete system compromise with root privileges, allowing attackers to install persistent malware, access all user data, and control device functions.

🟠

Likely Case

Local privilege escalation enabling unauthorized access to sensitive data and system resources from a compromised user context.

🟒

If Mitigated

Limited impact if proper SELinux policies and kernel hardening are in place, potentially containing the escalation within sandboxed environments.

🌐 Internet-Facing: LOW - This is a local vulnerability requiring local access to the device.
🏒 Internal Only: HIGH - Any compromised user account on affected devices can exploit this to gain root privileges.

🎯 Exploit Status

Public PoC: βœ… No
Weaponized: UNKNOWN
Unauthenticated Exploit: βœ… No
Complexity: MEDIUM

Requires local access but no user interaction. Exploitation involves crafting specific ioctl calls to trigger the vulnerable mmap operation.

πŸ› οΈ Fix & Mitigation

βœ… Official Fix

Patch Version: February 2026 Android Security Patch

Vendor Advisory: https://source.android.com/security/bulletin/pixel/2026-02-01

Restart Required: Yes

Instructions:

1. Check for system updates in Settings > System > System update. 2. Install February 2026 security patch. 3. Reboot device to apply kernel updates.

πŸ”§ Temporary Workarounds

Restrict VPU driver access

linux

Limit access to VPU device nodes using SELinux policies or file permissions

chmod 600 /dev/vpu*
chown root:root /dev/vpu*

🧯 If You Can't Patch

  • Implement strict application sandboxing and SELinux policies to limit damage from privilege escalation
  • Monitor for unusual process behavior and privilege escalation attempts using security monitoring tools

πŸ” How to Verify

Check if Vulnerable:

Check Android security patch level in Settings > About phone > Android version. If before February 2026, device is vulnerable.

Check Version:

adb shell getprop ro.build.version.security_patch

Verify Fix Applied:

Verify security patch level shows 'February 1, 2026' or later in Settings > About phone > Android version.

πŸ“‘ Detection & Monitoring

Log Indicators:

  • Unusual ioctl calls to /dev/vpu devices
  • Process privilege escalation from user to root context
  • Kernel crash logs related to memory mapping

Network Indicators:

  • None - this is a local vulnerability

SIEM Query:

process:privilege_escalation AND device:/dev/vpu* OR kernel:segfault AND module:vpu

πŸ”— References

πŸ“€ Share & Export