CVE-2026-55319 · Infrastructure
NO FIX YET
A flaw in the kernel's thread_free routine can corrupt kernel heap metadata when thread creation fails. A local app or process could use this to escalate privileges to kernel level without extra permissions or user interaction.
first public Nov 10, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Local code on a device running the affected kernel can trigger the corruption; the sources do not name the affected versions or devices. Systems that cannot patch the kernel should treat local untrusted code as a risk until a vendor fix is confirmed.
Who cares android, kernel, linux
Unknown from the sources.
No fix yet, per the sources.
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.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.