Live › vulnerability › CVE-2026-58824
A bounds check in the __pkvm_load_tracing function of the kernel's trace.c is incorrect, allowing an out-of-bounds write. A local user could use it to escalate privileges without extra execution rights or user interaction.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-11-02 20:35 UTC. All times on this page are UTC.
Affects systems running a kernel with pKVM (protected KVM) tracing code, typically Android-style or arm64 virtualization setups. The sources do not say which kernel versions or configurations are vulnerable. Machines without pKVM tracing support can likely skip it, but the sources do not confirm this.
No product ranges from the sources yet.
Unknown from the sources.
No fix yet, per the sources.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-58824")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.