Google Android: Local privilege escalation in Bluetooth stack
Summary
A flaw in the msft.cc handler of the Android Bluetooth stack can dereference an uninitialized pointer in the privileged Bluetooth process. A local attacker with low privileges and no user interaction could potentially hijack control flow and escalate privileges on the device. The bulletin lists the issue as a Critical DoS, which conflicts with the CVE description, so the type should be verified.
Affected
- Android 16
- Android 16-qpr2
- Android 17
Android 15 and older are not listed for this CVE.
Fixed in
- Security patch level 2026-10-01 or later (Android Security Bulletin October 2026)
Unknown: exact fixed AOSP build per branch.
Workaround
Unknown. No workaround was found in the sources.
Exploitation
- No in-the-wild exploitation reported.
- No public proof of concept found.
- CISA SSVC: Exploitation none, Automatable no, Technical Impact total.
Our recommendation
- Push the 2026-10-01 or newer patch level via MDM and verify the patch level of each device.
- Prioritise managed devices on Android 16 or 17; devices on Android 15 or older are not listed for this CVE.
- Where Bluetooth is not needed on managed devices, disable it or restrict it via MDM until patched.
- Note the type conflict (DoS in the bulletin vs. control-flow hijack/EoP in the CVE text) and track the NVD entry and AOSP links.
Public exploits
PoC-in-GitHub, Metasploit and Exploit-DB list nothing for this CVE.
Research sources
- Android Security Bulletin October 2026 source.android.com
- Pixel Update Bulletin October 2026 source.android.com
- Feedly: Android Security Bulletin October 2026 feedly.com
- Vulners: PT-2026-106149 vulners.com
- HOL Guard: CVE-2026-49933 CISA ADP Vulnrichment hol.org
- Daily Security Review: Android October 2026 update dailysecurityreview.com
Researched and written up in English and German by an AI (Claude by Anthropic) based on NVD, CISA, EPSS and the sources listed. The vendor information is authoritative. Researched on 2 Nov 2026, 06:33.
Original description (NVD)
In handle_le_monitor_device_event of msft.cc, there is a possible control-flow hijack in the privileged bluetooth process due to an uninitialized pointer dereference. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
NVD references (1)
Sources
The tracker combines official, freely usable data sources – updated continuously:
- NVD (NIST) – CVEs, rating (CVSS), affected products
- CISA KEV – vulnerabilities confirmed by CISA as actively exploited
- CISA Vulnrichment – CISA assessment (SSVC) in the official CVE record
- FIRST EPSS – probability of exploitation
- Microsoft MSRC – Patch Tuesday: vulnerabilities, severity, updates
- PoC-in-GitHub – public proof-of-concept repositories
- Metasploit (Rapid7) – modules of the Metasploit Framework
- Exploit-DB (OffSec) – archive of public exploits (links only)
- Patch days: official vendor pages (linked per vendor) (Vendor patch days)
This product uses data from the NVD API but is not endorsed or certified by the NVD. EPSS data © FIRST.org.
Affected? We can help.
We check whether your systems are affected, install updates and close the gap – continuously with the System Health Checker if you wish.