Track vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
2.4
CVE-2026-59574: Google firmware log can read/write beyond memory
CVE-2026-59574 · published 21 days ago
Summary
The part of Google's software that formats firmware log messages can miscalculate how much space is needed, causing it to read or write past the intended area. This could allow an attacker to see data they shouldn't without needing special permissions or user interaction. Update the software to the latest version where the bounds check has been fixed.
What to do
- Update google :unknown: to version Pixel-family specific:2026-11-05.
Affected software
| Ecosystem | Vendor | Product | Affected versions |
|---|---|---|---|
| – | android | Android kernel | |
| Android | :unknown: |
>= Pixel-family specific:0, < Pixel-family specific:2026-11-05 Fix: upgrade to Pixel-family specific:2026-11-05
|
Original advisory text
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 coul...
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.
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
2.4
Low
Type
CWE-119Buffer Overflow
CWE-125Out-of-bounds Read
CWE-787Out-of-bounds Write
Timeline
Published1 Nov 2026
Updated22 Nov 2026
First seen2 Nov 2026
Track software like this
Free during beta