Remote code execution via post-send buffer access
Published Aug 26, 2025 · Updated Aug 27, 2025
Use-after-free in Android 15 Bluetooth RFCOMM allows remote attackers to execute arbitrary code without user interaction. In rfc_check_send_cmd in rfc_utils.cc, L2CA_DataWrite can free a dequeued command buffer before an error log reads its len field; the patch saves the length before the call. The vulnerable path is in Bluetooth RFCOMM; exploitation needs neither authentication nor user interaction and grants code execution in the affected process.
Summary
What happened
Use-after-free in Android 15 Bluetooth RFCOMM allows remote attackers to execute arbitrary code without user interaction. In rfc_check_send_cmd in rfc_utils.cc, L2CA_DataWrite can free a dequeued command buffer before an error log reads its len field; the patch saves the length before the call. The vulnerable path is in Bluetooth RFCOMM; exploitation needs neither authentication nor user interaction and grants code execution in the affected process.
The record
- CVE
- CVE-2025-22408
- Published
- Aug 26, 2025
- Updated
- Aug 27, 2025
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-416, T1658, T1664
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 26, 2025CVE publishedPublication date reported by the CVE source.
- Aug 27, 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=15
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.
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