In __pkvm_load_tracing of trace.c, there is a possible out-of-bounds write due to an incorrect bounds check.
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
Do first: Workaround: The facts do not describe a workaround. Until a fix is installed, no specific mitigation is confirmed here, so check the Android security bulletin for guidance.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 6/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
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.
What to do
Workaround: The facts do not describe a workaround. Until a fix is installed, no specific mitigation is confirmed here, so check the Android security bulletin for guidance.
Timeline
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- CVE published
- First seen by cve.now1 day
- Record last updated
Affected versions
- Google Android
Version range not reported
Evidence 3
- Link
- Link
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-58824
What does this mean?
The bug is an out-of-bounds write in the pKVM tracing setup code in trace.c, caused by an incorrect bounds check. The check does not correctly limit where data is written when pKVM trace buffers are initialised.Source: android.googlesource.com
Am I affected, and how do I check?
The facts identify Google Android as the product and say the issue occurs when pKVM trace buffers are being initialised, but they do not list specific affected versions. Check the Android security bulletin for the version and patch level your device runs.Source: android.googlesource.com
What should I do about it?
The facts do not name a fixed version or patch, so no specific upgrade target can be given. Install the latest Android security update from your device vendor and follow the Android security bulletin for the fix.Source: android.googlesource.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What if there's no patch?
The facts do not describe a workaround. Until a fix is installed, no specific mitigation is confirmed here, so check the Android security bulletin for guidance.Source: android.googlesource.com