The path in this case is a little bit convoluted. The end result is that via an ioctl an untrusted app can control the ui32PageIndex offset in the expression:sPA.uiAddr = page_to_phys(psOSPageArrayData->pagearray[ui32PageIndex]);With the current PoC this crashes as an OOB read. However, given that the OOB read value is ending up as the address field of a struct I think i seems plausible that this could lead to an OOB write if the attacker is able to cause the OOB read to pull an interesting kernel address. Regardless if this is a read or write, it is a High severity issue in the kernel.Product: AndroidVersions: Android SoCAndroid ID: A-238904312
References
Link | Resource |
---|---|
https://source.android.com/security/bulletin/2022-09-01 | Vendor Advisory |
Configurations
Information
Published : 2022-09-13 13:15
Updated : 2022-09-16 11:50
NVD link : CVE-2021-0942
Mitre link : CVE-2021-0942
JSON object : View
CWE
CWE-125
Out-of-bounds Read
Products Affected
- android