Unauthenticated code execution via incorrect audio bounds check
Published Dec 11, 2025 · Updated Dec 11, 2025
Out-of-bounds write in the Android kernel allows remote attackers to execute code through a crafted AoC audio produce request. AudioDecoder::HandleProduceRequest in audio_decoder.cc applies an incorrect bounds check before writing output, allowing the write to extend beyond its destination buffer. No authentication, prior privileges, or user interaction is required, and successful exploitation grants code execution on an affected Pixel device.
Summary
What happened
Out-of-bounds write in the Android kernel allows remote attackers to execute code through a crafted AoC audio produce request. AudioDecoder::HandleProduceRequest in audio_decoder.cc applies an incorrect bounds check before writing output, allowing the write to extend beyond its destination buffer. No authentication, prior privileges, or user interaction is required, and successful exploitation grants code execution on an affected Pixel device.
The record
- CVE
- CVE-2025-36937
- Published
- Dec 11, 2025
- Updated
- Dec 11, 2025
- Vendor
- Go standard library
- Product
- Android
- Classifications
- CWE-787
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 11, 2025CVE publishedPublication date reported by the CVE source.
- Dec 11, 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=Android kernel
What conditions does exploitation require?
What is affected?
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