published 2 Nov 2026 · updated 9 Nov 2026
In __pkvm_load_tracing of trace.c, there is a possible out-of-bounds write due to an incorrect bounds check
8.4HighCVSS 8.4EPSS 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 __pkvm_load_tracing of trace.c, there is a possible out-of-bounds write due to an incorrect bounds check. 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 | =Android kernel |
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