No advisories yet.
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Mon, 05 Oct 2026 23:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Control-Flow Hijack via Uninitialized Pointer in Android Bluetooth Daemon |
Mon, 05 Oct 2026 22:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Uninitialized Pointer Dereference Enables Privilege Escalation in Android Bluetooth Daemon | |
| Weaknesses | CWE-665 |
Mon, 05 Oct 2026 20:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-824 | |
| Metrics |
cvssV3_1
|
Mon, 05 Oct 2026 20:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Uninitialized Pointer Dereference Enables Privilege Escalation in Android Bluetooth Daemon | |
| Weaknesses | CWE-665 |
Mon, 05 Oct 2026 20:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Google
Google android |
|
| Vendors & Products |
Google
Google android |
Mon, 05 Oct 2026 18:45:00 +0000
| 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 |
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: google_android
Published:
Updated: 2026-10-06T03:56:07.318Z
Reserved: 2026-06-02T14:45:32.236Z
Link: CVE-2026-49933
Updated: 2026-10-05T19:33:35.329Z
Status : Awaiting Analysis
Published: 2026-10-05T19:17:20.983
Modified: 2026-10-06T14:49:40.823
Link: CVE-2026-49933
No data.
OpenCVE Enrichment
Updated: 2026-10-05T23:30:15Z