HarborGuardharborguardDatabase
Back to search
HIGHCVE-2026-0137Published Modified CNA Google_Devices

CVE-2026-0137: In edgetpu_sync_fence_group_shutdown() of edgetpu-dmabuf

In edgetpu_sync_fence_group_shutdown() of edgetpu-dmabuf.c, there is a possible elevation of privilege due to a use after free. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation.

Metrics

CVSS v3.1
7.8
Severity
HIGH
Fixed in
Affected Products
1

Get notified

Email me when this CVE is updated: new fix versions, severity changes, or any record change.

HarborGuard Analysis

Synopsis

CVE-2026-0137 is a use-after-free vulnerability in the Android kernel's Edge TPU DMA buffer management, specifically in the edgetpu_sync_fence_group_shutdown() function of edgetpu-dmabuf.c. The flaw is exploitable locally by an attacker who already holds a low-privilege account on the device, requiring no network access or victim interaction. Successful exploitation gives the attacker full read, write, and execution control at the system level, enabling privilege escalation to root or equivalent. HarborGuard is tracking this advisory and will make a patched-image rebuild available the moment upstream publishes a fix.

HarborGuard Coverage

Detection

Detection of CVE-2026-0137 is available across every HarborGuard environment: the CVE is ingested from upstream feeds within minutes of publication and matched against all customer images, including custom-built Android kernel or device images, in both registry scans and CI pipeline checks.

Available
Triage

HarborGuard scores this CVE at CVSS 7.8 HIGH using the published v3.1 vector and weights it against each customer environment's compliance policy, routing findings to the appropriate team inbox with full vector detail for prioritization.

Available
Patch

No upstream fix version has been published for this CVE. HarborGuard re-checks the advisory on every ingest cycle and will make a patched-image rebuild available automatically the moment Google publishes a remediated kernel version.

Pending upstream

Exploit Conditions

  • Network reachabilityNot required

    The attacker needs an existing shell or process on the host; no network exposure is required.

  • AuthenticationRequired

    Any low-privilege account on the device is sufficient; the attacker does not need administrative or root credentials to trigger the vulnerability.

  • Victim interactionNot required

    No user action is required; the attacker can exploit the flaw entirely on their own.

  • Attack complexityDetail

    The exploit is reliable and condition-free, requiring no race conditions, specific memory layouts, or other environmental factors to succeed.

Blast Radius

  • Attacker escalates from a low-privilege process to System-level execution, gaining full control over the Android kernel context.
  • Reads arbitrary kernel memory, exposing credentials, session tokens, encryption keys, and other sensitive data held in kernel space.
  • Writes to arbitrary kernel memory, allowing persistent modification of kernel data structures, security policies, or stored application data.
  • Crashes or destabilizes the kernel, causing device reboot or sustained denial of service for all processes on the host.

How HarborGuard Handles This

Available on HarborGuard: this CVE is actively monitored with no upstream fix currently published. For affected environments, HarborGuard surfaces the finding with its full CVSS 7.8 HIGH score and vector detail so teams can prioritize compensating controls immediately. Recommended mitigations while awaiting a patch include restricting container or process capabilities to prevent untrusted code from reaching the Edge TPU DMA buffer path (for example, dropping CAP_SYS_ADMIN and related capabilities in container security contexts), applying SELinux or seccomp policies to block access to the affected ioctl surface, and isolating workloads that interact with Edge TPU hardware behind stricter namespace boundaries. HarborGuard will automatically make a patched-image rebuild available and, for customers with auto-remediation enabled, will trigger a rebuild, regression-test run, and a PR opened against affected workloads as soon as Google publishes a remediated kernel version.

See how HarborGuard automates this
Affected packages
  • Google / Android
    Android kernel
CVSS Vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H