dbcve.org
AndroidOperating system · Samsung

CVE-2025-21001

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 stop 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 · high confidence

Improper access control in LeAudioService allows local attackers to stop Auracast broadcasting. The vulnerability exists because the service does not properly validate that callers have appropriate permissions before executing broadcast control operations, enabling any local user to disrupt Auracast functionality.

MitigationApply the SMR Jul-2025 Release 1 security patch which includes proper access control validation in LeAudioService to enforce authorization checks before allowing broadcast control 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. Check Android version
    Go to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shell
    Affected if The installed version is exactly 14.0 or 15.0
  2. Verify LeAudioService is present
    Check for the LeAudioService APK in /system/priv-app/ or /data/app/ directories, or run 'dumpsys package com.android.bluetooth' to verify the service exists
    Affected if LeAudioService is installed and running on the device
  3. Confirm Auracast broadcast capability
    Check Bluetooth settings for Auracast support, or inspect Bluetooth stack logs for Auracast-related configurations
    Affected if Auracast broadcast functionality is enabled or available on the device
  4. Identify if device is Samsung
    Check the device manufacturer via 'getprop ro.product.manufacturer' or 'getprop ro.build.version.security_patch' to confirm Samsung branding
    Affected if The device is a Samsung device running the affected Android versions

A Samsung Android device running version 14.0 or 15.0 with LeAudioService and Auracast capability enabled is affected by this improper access control vulnerability.

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 includes proper access control validation in LeAudioService to enforce authorization checks before allowing broadcast control operations.

Recommended fix High confidence

Samsung SMR July-2025 Release 1 (or later)

  1. Check for system updates on your Samsung device running Android 14.0 or 15.0
  2. Navigate to Settings > Software Update > Download and install
  3. Ensure the installed update includes the July 2025 SMR (Samsung Monthly Release) security patch
  4. Verify the patch is applied by checking Settings > About phone > Software information > Security patch level

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

Fix this in Android Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-21001 — 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-21001 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