Adjacent code execution via post-free buffer length read
Published Sep 4, 2025 · Updated Feb 26, 2026
Use-after-free in Android 15 and 16 Bluetooth allows remote authenticated users to execute code via adjacent Bluetooth traffic. SendPacketToPeer logs p_buf->len after L2CA_SendFixedChnlData can free p_buf, causing a dangling-pointer read. Exploitation requires a low-privilege adjacent peer and no user interaction; successful exploitation compromises the device.
Summary
What happened
Use-after-free in Android 15 and 16 Bluetooth allows remote authenticated users to execute code via adjacent Bluetooth traffic. SendPacketToPeer logs p_buf->len after L2CA_SendFixedChnlData can free p_buf, causing a dangling-pointer read. Exploitation requires a low-privilege adjacent peer and no user interaction; successful exploitation compromises the device.
The record
- CVE
- CVE-2025-48539
- Published
- Sep 4, 2025
- Updated
- Feb 26, 2026
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-416, T1658
- Attack vector
- adjacent
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 4, 2025CVE publishedPublication date reported by the CVE source.
- Feb 26, 2026Record 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=15
- 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.
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