Local memory disclosure via incorrect bounds check
Published Mar 10, 2025 · Updated Mar 11, 2025
Out-of-bounds read in Google Android on Pixel devices before the 2025-03-05 patch level allows local users to disclose memory. The Trusty tipc_dev_ql dev_send function applies an incorrect bounds check, allowing a request to read beyond the intended buffer. Exploitation requires local access but no additional execution privileges or user interaction; the documented consequence is device-memory disclosure.
Summary
What happened
Out-of-bounds read in Google Android on Pixel devices before the 2025-03-05 patch level allows local users to disclose memory. The Trusty tipc_dev_ql dev_send function applies an incorrect bounds check, allowing a request to read beyond the intended buffer. Exploitation requires local access but no additional execution privileges or user interaction; the documented consequence is device-memory disclosure.
The record
- CVE
- CVE-2024-56184
- Published
- Mar 10, 2025
- Updated
- Mar 11, 2025
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-125, T1005
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 10, 2025CVE publishedPublication date reported by the CVE source.
- Mar 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?
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.
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