published 5 Oct 2026 · updated 6 Oct 2026
In handle_le_monitor_device_event of msft.cc, there is a possible control-flow hijack in the privileged bluetooth process due to an…
7.8HighCVSS 7.8EPSS 0%
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. No fixed version is recorded.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Android | =16, =16-qpr2, =17 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Google, strongest first
10.0CriticalPublic exploit
10.0CriticalPublic exploit
10.0CriticalPublic exploit
10.0CriticalPublic exploit
Embed
A live severity badge for an advisory, README or ticket