CVE-2026-58824
highIn __pkvm_load_tracing of trace.c, there is a possible out-of-bounds write due to an incorrect bounds check.
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.
CVSS
8.4
8.4 (CVSS v3.1)
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Severity source: NVD CVSS v3.1 (134c704f-9b21-4f2e-91b3-4a467353bcc0)
Timeline (UTC)
Published: 2026-11-02 20:17
Modified: 2026-11-03 16:17
NVD status: Awaiting Analysis
Last synced 1 day ago
Verified against the source API 2026-11-03 16:20 UTC
Exploitation
Not listed in CISA KEV (as of last catalog sync)
Absence from KEV does not mean a CVE is not exploited. Exploitation status: unknown (no authoritative evidence in our sources).
Affected products
Not reported by the source (unknown — not "none").
Weakness classification (CWE)
Source: NVD / CISA. “NVD-CWE-Other” and “NVD-CWE-noinfo” mean NVD could not assign a specific weakness.
Mitigation & advisories
No vendor advisory or patch reference tagged by NVD. Check the references below.
References
- https://android.googlesource.com/kernel/common/+/5a6735b89ba7c8684d36e2ecd9b02e834e97de9c security@android.com
- https://android.googlesource.com/kernel/common/+/8be8949794c96f10348fdd3d8dc7740fdfecd4e2 security@android.com
- https://source.android.com/docs/security/bulletin/2026/2026-11-01 security@android.com
Data sources
NVD CVE API 2.0 — fetched 2026-11-03 16:20 UTC · record ↗