CVE-2026-49933
In handle_le_monitor_device_event of msft.cc, there is a possible control-flow hijack in the...
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.
Attack profile
How easy it is to exploit
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
What an attacker can affect
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Exploit likelihood
What each source reports
CVE List Score used
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.
- Record
CVE-2026-49933- CVSS 3.1
- 7.8 High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - Weakness
- CWE-824
- Updated
- 2026-11-02
EUVDEUVD-2026-92603
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.
- Record
EUVD-2026-92603- CVSS 3.1
- 7.8 High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
GitHub AdvisoriesGHSA-pgf5-jg2x-qwcp
In handle_le_monitor_device_event of msft.cc, there is a possible control-flow hijack in the...
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.
- Record
GHSA-pgf5-jg2x-qwcp- CVSS 3.1
- 7.8 High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - Weakness
- CWE-824
- Updated
- 2026-11-02
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.
- Record
CVE-2026-49933- CVSS 3.1
- 7.8 High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - Weakness
- CWE-824
- Updated
- 2026-11-02
OSVASB-A-522372651 No score
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.
- Record
ASB-A-522372651- Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
platform/packages/modules/BluetoothAndroid |
17-next:0 up to 17-next:2026-10-01, plus listed versions 17-next |
17-next:2026-10-01 |
platform/packages/modules/BluetoothAndroid |
16:0 up to 16:2026-10-01, plus listed versions 16 |
16:2026-10-01 |
platform/packages/modules/BluetoothAndroid |
16-qpr2:0 up to 16-qpr2:2026-10-01, plus listed versions 16-qpr2 |
16-qpr2:2026-10-01 |
platform/packages/modules/BluetoothAndroid |
17:0 up to 17:2026-10-01, plus listed versions 17 |
17:2026-10-01 |
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | CVE List, EUVD, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2026-49933 is a high vulnerability (CVSS 7.8) in Google Android, published October 1, 2026. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.07%, the 0th percentile. Fixed in platform/packages/modules/Bluetooth 17-next:2026-10-01.