CVE-2026-49933

Control-Flow Hijack via Uninitialized Pointer in Android Bluetooth Daemon

Published Oct 5, 2026 CVSS 3.1 · 7.8 High EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

A flaw in the msft.cc component of Android’s Bluetooth daemon allows an attacker to exploit an uninitialized pointer, leading to a control-flow hijack of the privileged bluetooth process. The resulting escalation can grant higher privilege to the attacker without the need for any user interaction. This vulnerability provides a clear privilege elevation path for local attackers, potentially enabling wide-ranging system compromises such as modifying system settings, installing malicious software, or accessing sensitive data.

Affected Systems

Google Android devices running the affected Bluetooth daemon, as referenced by the Android Security Bulletin for October 2026. The specific versions are not enumerated in the current data, but any device with the unpatched msft.cc implementation is vulnerable.

Risk and Exploitability

The exploitation requires local access to the device and no user interaction, meaning any malicious code already present on the system can trigger the escalation. The EPSS score is not available, and the vulnerability is not listed in the CISA KEV catalog. Because the vulnerability is local and does not require external network exposure, the attack vector is inferred to be local code execution. The CVSS score of 7.8 indicates a high severity, reinforcing the need for immediate remediation.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the Android security patch released in the October 2026 bulletin to fix the uninitialized pointer flaw in msft.cc.
  • If a patch is unavailable, disable the Bluetooth subsystem or restrict its use to prevent the daemon from running with elevated privileges.
  • Consider restricting local application permissions so that only trusted apps can interact with the Bluetooth daemon, mitigating the likelihood of exploitation by untrusted code.

Generated by OpenCVE AI on October 5, 2026 at 23:29 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
CPEs cpe:2.3:o:google:android:16.0:-:*:*:*:*:*:*
cpe:2.3:o:google:android:16.0:qpr2:*:*:*:*:*:*
cpe:2.3:o:google:android:17.0:-:*:*:*:*:*:*
Type Values Removed Values Added
Title Control-Flow Hijack via Uninitialized Pointer in Android Bluetooth Daemon
Type Values Removed Values Added
Title Uninitialized Pointer Dereference Enables Privilege Escalation in Android Bluetooth Daemon
Weaknesses CWE-665
Type Values Removed Values Added
Weaknesses CWE-824
Metrics cvssV3_1

{'score': 7.8, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}

ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Title Uninitialized Pointer Dereference Enables Privilege Escalation in Android Bluetooth Daemon
Weaknesses CWE-665
Type Values Removed Values Added
First Time appeared Google
Google android
Vendors & Products Google
Google android
Type Values Removed Values Added
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.
References
Weaknesses
  • CWE-824

    Access of Uninitialized Pointer

Sources

Status
PUBLISHED
Assigner
google_android
Published
Updated
Oct 6, 2026, 3:56 AM
Reserved
Jun 2, 2026, 2:45 PM
Status
Analyzed
Published
Oct 5, 2026, 7:17 PM
Modified
Oct 7, 2026, 1:14 PM