# CVE-2026-59048: CVE-2026-59048

Status: published. Published: 2026-11-02. Updated: 2026-11-02.

In rb_cpu_init of trace.c, there is a possible out-of-bounds read due to an incorrect bounds check. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Google / Android: Android kernel (affected). Source: CNA: google_android

## Severity and prioritization

- CISA KEV: No listing in collected sources

- EPSS: Not available

- SSVC: Not available

- Weaknesses: Not reported

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://android.googlesource.com/kernel/common/+/e46b3a946c957ab463a8abf9333dea702e8a485e (CNA: google_android)

- https://android.googlesource.com/kernel/common/+/5e31aa53a963b254ddac8a88b48e5b64cfc38eea (CNA: google_android)

- https://source.android.com/docs/security/bulletin/2026/2026-11-01 (CNA: google_android)

## Provenance

- CNA: google_android: https://www.cve.org/CVERecord?id=CVE-2026-59048; retrieved 2026-11-02; source updated 2026-11-02

Revision: bcb2858273c82ad3063c2220dfacdf01d90d1cc24b15ee6762a9d3f24fb00567

Canonical: https://y2.dev/cve/CVE-2026-59048

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.