VDB
ASB-A-255601934
ASB-A-255601934
PUBLISHED
Record from OSV · Published September 1, 2025
In multiple locations, there is a possible way to impersonate and MitM a device across session by only compromising one session key due to an insecure protocol design on Bluetooth Legacy Secure Connection (LSC). This could lead to remote escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| platform/packages/modules/Bluetooth | source.android.com | 16-next:2025-09-01, 15:2025-09-01, 14:2025-09-01, 13:2025-09-01 |
Affected products
| Vendor | Product | Versions |
|---|---|---|
| platform | packages/modules/Bluetooth | 16-next:0, 16-next, 15:0 |
Timeline
- Sep 1, 2025 CVE Published
- Aug 7, 2026 CVE Updated
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln ASB-A-255601934
vulnetix vdb fixes ASB-A-255601934Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/ASB-A-255601934/fixes/registry"The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart