CVE-2026-49933

Analyzed Analyzed - Analysis Complete

Bluetooth Process Control-Flow Hijack in msft.cc

Publication date: 2026-10-05

Last updated on: 2026-10-07

Assigner: Android (associated with Google Inc. or Open Handset Alliance)

Description

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-10-05

Last Modified

2026-10-07

Generated

2026-10-19

AI Q&A

2026-10-05

EPSS Evaluated

2026-10-18

NVD

CVE-2026-49933

EUVD

EUVD-2026-92603

Affected Vendors & Products

Vendor	Product	Version / Range
google	android	16.0
google	android	16.0
google	android	17.0

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-824	The product accesses or uses a pointer that has not been initialized.

Attack-Flow Graph

Executive Summary

This vulnerability is a control-flow hijack in the privileged Bluetooth process of Google Android. It occurs due to an uninitialized pointer dereference in the msft.cc file, specifically in the handle_le_monitor_device_event function. This flaw allows an attacker to manipulate the program's execution flow, potentially leading to unauthorized actions.

Detection Guidance

Detection requires analyzing the msft.cc component for uninitialized pointer dereferences in handle_le_monitor_device_event. Check system logs for bluetooth process crashes or unexpected behavior. Use debugging tools like AddressSanitizer to monitor memory access violations.

Impact Analysis

This vulnerability could allow a local attacker to escalate their privileges on the device. Since no additional execution privileges or user interaction are required, it poses a significant risk for unauthorized access to sensitive functions or data on the affected Android device.

Compliance Impact

This vulnerability could potentially lead to unauthorized local privilege escalation in a privileged Bluetooth process, which may result in unauthorized access to sensitive data. This could impact compliance with GDPR by risking unauthorized data access or processing, and with HIPAA by potentially exposing protected health information if exploited.

Mitigation Strategies

Apply the latest Android security patches immediately. Disable Bluetooth if not in use. Monitor for unusual privilege escalation attempts. Restrict Bluetooth permissions for untrusted applications.

Hi! I’m here to help you understand CVE-2026-49933. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70