Persistent device impairment via production debug code
Published Jun 13, 2024 · Updated Mar 20, 2025
Denial of service in Android kernel Telephony on supported Pixel devices allows local users to impair device use without user interaction. The nonpublic Telephony issue leaves test or debugging code enabled in a production build, but Google has not disclosed the code path or trigger. Local low-privileged access is sufficient, and exploitation persistently impairs device use without reported data disclosure or modification.
Summary
What happened
Denial of service in Android kernel Telephony on supported Pixel devices allows local users to impair device use without user interaction. The nonpublic Telephony issue leaves test or debugging code enabled in a production build, but Google has not disclosed the code path or trigger. Local low-privileged access is sufficient, and exploitation persistently impairs device use without reported data disclosure or modification.
The record
- CVE
- CVE-2024-32912
- Published
- Jun 13, 2024
- Updated
- Mar 20, 2025
- Vendor
- Product
- Android
- Classifications
- CWE-400, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 13, 2024CVE publishedPublication date reported by the CVE source.
- Mar 20, 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.
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