CVE-2025-22411: Bluetooth Module Vulnerability Leading to Remote Code Execution

Summary

01/03/2025
Yes i
Critical
Not published

CVE-2025-22411: In process_service_attr_rsp of sdp_discovery.cc, there is a possible use after free due to a logic error in the code. Affects platform/packages/modules/Bluetooth across 2 version ranges.

>= 15:0, < 15:2025-03-01 >= 15-next:0, < 15-next:2025-03-01

Fixed in 15-next:2025-03-01. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The Bluetooth module in the Android ecosystem is responsible for enabling wireless communication between devices. It supports various profiles and protocols, allowing for seamless connectivity and data exchange. However, this module has been identified to have a critical vulnerability that could allow an attacker to execute arbitrary code remotely, posing significant security risks to users.

Vulnerability Detail

The vulnerability arises from a use-after-free error in the 'process_service_attr_rsp' function within the 'sdp_discovery.cc' file. This logic error can be exploited by an adjacent attacker to execute arbitrary code without requiring additional privileges or user interaction. The potential ramifications include unauthorized access to sensitive data and control over the affected device, making it a critical security concern.

How To Fix

Minimum fixed version

15-next:2025-03-01

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

Currently, no specific workarounds are provided for this vulnerability. It is recommended to apply the patch as soon as it becomes available to mitigate the risk.

Conclusion

The CVE-2025-22411 vulnerability in the Android Bluetooth module poses a significant risk due to its potential for remote code execution. Users are strongly advised to update to the patched version to mitigate this risk and protect their devices from exploitation.

See every vulnerability recorded for platform/packages/modules/Bluetooth →

Share this vulnerability

FAQ

CVE-2025-22411 is a critical vulnerability in the Bluetooth module of Android that allows remote code execution due to a use-after-free error.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

If you cannot update your Bluetooth module, it is advisable to limit Bluetooth connectivity and avoid pairing with unknown devices until a patch is applied.

No, user interaction is not needed for exploitation, making this vulnerability particularly dangerous.

The consequences include unauthorized access to the device, potential data breaches, and the ability for attackers to execute arbitrary code remotely.

Related vulnerabilities

Recent vulnerabilities recorded for platform/packages/modules/Bluetooth.

How To Fix

Minimum fixed version

15-next:2025-03-01

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback