A bug in the Android kernel trace.c file allows an out-of-bounds read during rb_cpu_init because the bounds check is incorrect. This flaw can leak kernel memory contents to a local process without needing elevated privileges or privileged user interaction. The data exposed could include sensitive device information that otherwise remains protected.

The vulnerability affects the Android kernel repository managed by Google, but no specific kernel or Android release versions are listed in the advisory. Any device using the affected kernel code before a fix is installed is potentially vulnerable.

The exploit does not require user interaction or additional privileges, which means any local user process could read hidden kernel data. The EPSS score is unavailable, and the issue is not in the CISA KEV catalog, so the exact likelihood of exploitation is unknown. However, because the flaw is local and requires no special conditions, the risk to confidentiality is significant for affected devices.