Local information disclosure via unchecked gralloc4 write
Published Sep 5, 2025 · Updated Sep 5, 2025
Out-of-bounds write in Android 16 gralloc4 allows local users to disclose information through a missing bounds check. The gralloc4 code fails to verify a buffer boundary before writing, allowing memory outside the intended allocation to be overwritten. Exploitation requires low-privileged local access, needs no user interaction or additional execution privileges, and is reported to expose information without integrity or availability impact.
Summary
What happened
Out-of-bounds write in Android 16 gralloc4 allows local users to disclose information through a missing bounds check. The gralloc4 code fails to verify a buffer boundary before writing, allowing memory outside the intended allocation to be overwritten. Exploitation requires low-privileged local access, needs no user interaction or additional execution privileges, and is reported to expose information without integrity or availability impact.
The record
- CVE
- CVE-2025-32316
- Published
- Sep 5, 2025
- Updated
- Sep 5, 2025
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-787
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 5, 2025CVE publishedPublication date reported by the CVE source.
- Sep 5, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=16
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo