CVE-2025-22404
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn avct_lcb_msg_ind of avct_lcb_act.cc, there is a possible way to execute arbitrary code due to a use after free. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA use-after-free vulnerability exists in the avct_lcb_msg_ind function within avct_lcb_act.cc. The vulnerability allows local privilege escalation without requiring user interaction or additional execution privileges, as the attacker can exploit freed memory to execute arbitrary code.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 15.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Android versionRun 'adb shell getprop ro.build.version.release' or go to Settings > About Phone > Android versionAffected if The version returned is exactly 15.0
-
Identify Bluetooth stack componentsCheck if /system/lib/libbluetooth.so or similar AVCT libraries exist on the device via 'adb shell ls -la /system/lib/'Affected if Bluetooth libraries are present and the device runs Android 15.0
-
Verify AVCT module is loadedRun 'adb shell dumpsys bluetooth' to check if Bluetooth service is active and loaded modules are listedAffected if Bluetooth is enabled and the AVCT (Audio/Video Control Transport) module is loaded on an Android 15.0 device
The environment is affected only if running Android version exactly 15.0 with Bluetooth enabled and the AVCT Bluetooth module loaded.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedApply the vendor-provided patch for CVE-2025-22404 to address the use-after-free in avct_lcb_act.cc; if no patch is available, audit the memory management in the affected function to ensure all pointers are properly validated before use.
Android 15.1 or later / Android Security Patch Level 2025-03-01 or later
- Check your device's current Android version in Settings > About Phone > Android version
- Check your device's security patch level in Settings > About Phone > Security patch level
- If running Android 15.0, upgrade to Android 15.1 or later via Settings > System > Software update
- Alternatively, ensure you have installed the latest Android security update (2025-03 or later) which should contain the fix for this vulnerability
- Verify the fix by confirming the security patch level is March 2025 or later after updating
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,024.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-22404 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-22404 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data