CVE-2026-55319

published 10 Nov 2026 · updated 13 Nov 2026

In thread_free of thread.c, there is a possible way to corrupt kernel heap metadata on thread creation failure due to memory corruption

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 thread_free of thread.c, there is a possible way to corrupt kernel heap metadata on thread creation failure due to memory corruption. 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

VendorProductVersionsFixed
GoogleAndroid=Android kernel

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Google, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-55319 severity on Zeptric[![CVE-2026-55319](https://zeptric.io/badge/cve/CVE-2026-55319.svg)](https://zeptric.io/cve/CVE-2026-55319)