In multiple functions of mem_protect.c, there is a possible way to access hypervisor memory due to a memory access check in the wrong place. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation.
The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data.
Link | Tags |
---|---|
https://android.googlesource.com/kernel/common/+/b35a06182451f | patch |
https://android.googlesource.com/kernel/common/+/53625a846a7b4 | patch |
https://source.android.com/security/bulletin/2023-08-01 | patch vendor advisory |