HAL_FWLOG · CVE-2026-59574 · Other
NO FIX YET
A bounds check in notifyPollingLoopFrames in hal_fwlog.cc is wrong, so formatting firmware log notifications can read and write outside allocated memory. The description says this could lead to physical information disclosure without extra privileges and without user interaction.
first public Nov 10, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Who cares android, firmware-logging
Unknown from the sources.
No fix yet, per the sources.
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.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.