Track vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
5.5
CVE-2026-41155: Google GPU secure memory can be tampered with
CVE-2026-41155 · published 4 days ago
Summary
The GPU’s secure memory area can be shared between different protected processes. An attacker who gains control of one process could leak data to another process or cause the other process’s images to become corrupted, potentially forcing the graphics hardware to reset. Apply any available patches from the vendor and limit privileged access to GPU resources.
What to do
- Update google :unknown: to version SoCVersion:2026-11-05.
Affected software
| Ecosystem | Vendor | Product | Affected versions |
|---|---|---|---|
| Android | :unknown: |
>= SoCVersion:0, < SoCVersion:2026-11-05 Fix: upgrade to SoCVersion:2026-11-05
|
Original advisory text
ASB-A-499033076
An attacker could cooperatively pass data from one secure GPU process to another secure GPU process through shared secure memory allocations in the kernel module. Additionally, an attacker could disrupt the operation of another secure GPU process leading to image corruption / GPU hardware recovery.
Sharing secure memory allocations among various GPU secure processes allows an attacker to corrupt shared resource affecting other users.
Sharing secure memory allocations among various GPU secure processes allows an attacker to corrupt shared resource affecting other users.
Internet-facing
60 days
Internal
At next upgrade
- Not known to be exploited
- Needs hands-on effort to exploit
- Gives an attacker partial control
Severity
5.5
Medium
Type
CWE-653Improper Isolation or Compartmentalization
Timeline
Published1 Nov 2026
Updated4 Nov 2026
First seen12 Jun 2026
Track software like this
Free during beta