Local memory disclosure via incorrect wipe size
Published Mar 11, 2024 · Updated Mar 25, 2025
Incorrect buffer-size calculation in Google Android 13 allows local users to disclose memory through the Pixel bootloader. The wipe_ns_memory function in nsmemwipe.c uses an incorrectly calculated size while wiping namespace memory, causing the information exposure. Exploitation requires low-privileged local access, needs no user interaction, and has no reported data-modification or service-interruption impact.
Summary
What happened
Incorrect buffer-size calculation in Google Android 13 allows local users to disclose memory through the Pixel bootloader. The wipe_ns_memory function in nsmemwipe.c uses an incorrectly calculated size while wiping namespace memory, causing the information exposure. Exploitation requires low-privileged local access, needs no user interaction, and has no reported data-modification or service-interruption impact.
The record
- CVE
- CVE-2024-27237
- Published
- Mar 11, 2024
- Updated
- Mar 25, 2025
- Vendor
- Product
- Android
- Classifications
- CWE-131
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Mar 11, 2024CVE publishedPublication date reported by the CVE source.
- Mar 25, 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=13
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