published 10 Nov 2026 · updated 13 Nov 2026
In ext_mem_obj_get_page of memss-mfw.c, there is a possible way to return an out of bounds physical address via an off-by-one check due to…
2.3LowCVSS 2.3EPSS 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 ext_mem_obj_get_page of memss-mfw.c, there is a possible way to return an out of bounds physical address via an off-by-one check due to an incorrect bounds check. This could lead to local information disclosure with System 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
10.0CriticalPublic exploit
10.0CriticalPublic exploit
10.0CriticalPublic exploit
10.0CriticalPublic exploit
Embed
A live severity badge for an advisory, README or ticket