VDB
ASB-A-443742829
ASB-A-443742829
PUBLISHED
Record from OSV · Published December 1, 2025
In setDisplayName of AssociationRequest.java, there is a possible way to cause CDM associations to persist after the user has disassociated them due to improper input validation. This could lead to local 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/frameworks/base | source.android.com | 16-qpr2-next:2025-12-01, 16:2025-12-01, 15:2025-12-01, 14:2025-12-01 |
Affected products
| Vendor | Product | Versions |
|---|---|---|
| platform | frameworks/base | 16-qpr2-next:0, 16-qpr2-next:0, 16-qpr2-next |
Timeline
- Dec 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-443742829
vulnetix vdb fixes ASB-A-443742829Or 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-443742829/fixes/registry"The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart