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
More Stories
Erlang/OTP RCE (CVE-2025-32433)
What is the Vulnerability? A critical SSH vulnerability has recently been identified in the Erlang/Open Telecom Platform (OTP). The vulnerability,...
digikam-8.6.0-4.fc40
FEDORA-2025-97687e7f68 Packages in this update: digikam-8.6.0-4.fc40 Update description: update internal Libraw to 2025/03/17 snapshot Read More
digikam-8.6.0-4.fc41
FEDORA-2025-5bbbb2df79 Packages in this update: digikam-8.6.0-4.fc41 Update description: update internal Libraw to 2025/03/17 snapshot Read More
digikam-8.6.0-4.fc42
FEDORA-2025-1c1e378468 Packages in this update: digikam-8.6.0-4.fc42 Update description: update internal Libraw to 2025/03/17 snapshot Read More
epiphany-47.6-1.fc41
FEDORA-2025-164c668d6a Packages in this update: epiphany-47.6-1.fc41 Update description: Update to 47.6, notably fixing CVE-2025-3839 Read More
epiphany-48.2-1.fc42
FEDORA-2025-efbe201596 Packages in this update: epiphany-48.2-1.fc42 Update description: Update to 48.2, notably fixing CVE-2025-3839 Read More