CVE-2025-0075
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 process_service_search_attr_req of sdp_server.cc, there is a possible way to execute arbitrary code due to a use after free. This could lead to remote code execution 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 process_service_search_attr_req function of sdp_server.cc in the Bluetooth SDP (Service Discovery Protocol) server. An attacker can trigger this memory corruption flaw to achieve remote code execution without requiring any user interaction or elevated privileges.
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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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 versionGo to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shellAffected if Version is exactly 15.0 (not 15.0.1 or higher)
-
Verify Bluetooth is enabledCheck Settings > Bluetooth > On/Off toggle, or run 'settings get global bluetooth_on' via ADB shellAffected if Bluetooth is turned ON (the SDP server is active when Bluetooth is enabled)
-
Confirm Bluetooth SDP service is runningRun 'dumpsys bluetooth_manager' or check for 'sdp-server' in process list via ADB shellAffected if The SDP service is active (running when Bluetooth is enabled on Android)
-
Check if device is in discoverable modeCheck Settings > Bluetooth > Device name visibility, or run 'getprop bluetooth.sdpscan' via ADB shellAffected if Device is discoverable or has SDP scanning enabled, increasing exposure to remote attackers
A device is affected if it runs Android version 15.0 (exact) and has Bluetooth enabled, as the vulnerable SDP server code is active whenever Bluetooth is on.
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 security patch for the affected Bluetooth stack implementation. If no patch is available, restrict Bluetooth accessibility via network filtering or disable Bluetooth on vulnerable systems until a fix is available.
Latest Android 15 security patch level (February 2025 Android Security Bulletin or later)
- Check for system updates on the Android 15.0 device and install the latest available Android security patch level.
- Verify the installed Android security patch level meets or exceeds the level that addresses CVE-2025-0075 (typically the February 2025 Android Security Bulletin or later).
- If the device manufacturer has not released an update containing the fix, consider using a device that receives timely security updates.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation16.0 h
- Testing12.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 $11,136.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-0075 — 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-0075 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