published 10 Nov 2026 · updated 13 Nov 2026
In notifyPollingLoopFrames of hal_fwlog.cc, there is a possible way to trigger an out of bounds read and write when formatting firmware log…
2.4LowCVSS 2.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 notifyPollingLoopFrames of hal_fwlog.cc, there is a possible way to trigger an out of bounds read and write when formatting firmware log notifications due to an incorrect bounds check. This could lead to physical information disclosure 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
10.0CriticalPublic exploit
10.0CriticalPublic exploit
10.0CriticalPublic exploit
10.0CriticalPublic exploit
Embed
A live severity badge for an advisory, README or ticket