---
id: "CVE-2026-59574"
page: "https://infrastack.ai/live/CVE-2026-59574"
kind: "vulnerability"
aliases: ["CVE-2026-59574"]
title: "Android firmware log code: out-of-bounds read and write from bad bounds check"
severity: "unknown"
cvss: null
epss: null
exploited: false
status: "open"
category: "other"
products: [{"name": "hal_fwlog", "fixed": [], "affected": "", "ecosystem": "vendor"}]
ecosystems: ["vendor"]
tags: ["android", "firmware-logging", "other"]
not_affected_if: []
published_at: "2026-11-10T20:19:28+00:00"
first_seen_at: "2026-11-10T20:46:12+00:00"
updated_at: "2026-11-10T20:50:07+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-59574", "first_seen_at": "2026-11-10T20:46:12+00:00"}]
exploit_sources: []
---

# Android firmware log code: out-of-bounds read and write from bad bounds check

Link for people: https://infrastack.ai/live/CVE-2026-59574 (this .md is for agents)

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.

_Summary, check and fix written by a model from the sources; labelled as such._

## Affected

- vendor:hal_fwlog affected range not listed fixed no fixed version listed

## Timeline

- 2026-11-10T20:46:12+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-59574

## From 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.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_