dbcve.org
AndroidOperating system · Samsung

CVE-2025-21002

MEDIUM · 5.5 CVSS v3.1 Published 2025-07-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

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 · unedited
Improper access control in LeAudioService prior to SMR Jul-2025 Release 1 allows local attackers to manipulate broadcasting Auracast.

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 · moderate confidence

This is an improper access control vulnerability in Android's LeAudioService (Bluetooth Low Energy Audio service) that allows local attackers to manipulate Auracast broadcast functionality. The vulnerability exists because the service lacks proper authorization checks before allowing broadcast manipulation, enabling any local user or application to interfere with Bluetooth audio broadcasting that should be restricted.

MitigationApply the SMR Jul-2025 Release 1 security patch which contains the fixed LeAudioService with proper access control enforcement for Auracast broadcast operations.

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
AndroidOperating system
Affected:= 14.0= 15.0

CVSS 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Android version is 14.0 or 15.0
    Go to Settings > About Phone and verify the Android version. Alternatively, run 'getprop ro.build.version.release' via ADB shell.
    Affected if The device is running Android version 14.0 or 15.0 (any build within these major versions).
  2. Verify security patch level
    Go to Settings > About Phone > Software Information and check the Security patch level date. Alternatively, run 'getprop ro.build.version.security_patch' via ADB shell.
    Affected if The security patch level is earlier than July 2025 (SMR Jul-2025 Release 1) or the field is blank/unknown.
  3. Check if LeAudio/Auracast feature is enabled
    Open Settings > Bluetooth > look for Auracast or LE Audio settings. On supported devices, Auracast may appear as a broadcast option in the Bluetooth audio settings or quick settings panel.
    Affected if The device supports and has enabled Auracast or Bluetooth LE Audio broadcasting functionality.
  4. Confirm LeAudioService is present
    Check if the LeAudioService APK exists on the system. Run 'pm list packages | grep leaudio' via ADB shell to verify the Bluetooth LE Audio service package is installed.
    Affected if The LeAudioService package is installed on the device (standard on Android 14+ devices with Bluetooth capability).

A device is affected if it runs Samsung Android 14.0 or 15.0, has a security patch level earlier than July 2025, and has LeAudio/Auracast functionality available or enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the SMR Jul-2025 Release 1 security patch which contains the fixed LeAudioService with proper access control enforcement for Auracast broadcast operations.

Recommended fix High confidence

SMR Jul-2025 Release 1 (July 2025 Android Security Patch Level)

  1. Check current Android security patch level on the device (Settings > Security > Security update > Security patch level)
  2. Verify the device is running Android 14.0 or 15.0
  3. Apply the July 2025 Samsung security update (SMR Jul-2025 Release 1) via Settings > Software update > Download and install
  4. After update, confirm security patch level shows July 2025 or later

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Android Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,504.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-21002 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-21002 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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