Skip to main content
VulnerabilityPublished

CVE-2026-59048: In rb_cpu_init of trace.c, there is a possible out-of-bounds read due to an incorrect bounds check

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-59048· Medium

Not known to be exploited.

Data as of 2 Nov 2026, 22:30 UTC

Severity
Medium

Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
GoogleAndroidAffected
  • =Android kernel
Fixed in–

Description

CVE-2026-59048 is a vulnerability in the rb_cpu_init function of trace.c involving a possible out-of-bounds read caused by an incorrect bounds check. This flaw can lead to local information disclosure without requiring additional execution privileges or user interaction.

References

Community reviews

Loading reviews…