published 10 Nov 2026 · updated 13 Nov 2026
In multiple functions of mpu.c, there is a possible way to execute code from non-secure memory in the security coprocessor due to an…
8.4HighCVSS 8.4EPSS 0%
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. No fixed version is recorded.
In multiple functions of mpu.c, there is a possible way to execute code from non-secure memory in the security coprocessor due to an insecure default value. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Android | =Android kernel |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Google, strongest first
Embed
A live severity badge for an advisory, README or ticket