Google Android mem_protect.c __host_check_page_state_range out-of-bounds write
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.8 | $25k-$100k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in Google Android. Affected by this issue is the function __host_check_page_state_range of the file mem_protect.c. The manipulation leads to out-of-bounds write.
This vulnerability is listed as CVE-2026-0030. The attack must be carried out locally. There is no available exploit.
Details
A vulnerability was found in Google Android (affected version unknown) and classified as critical. This issue affects the function __host_check_page_state_range of the file mem_protect.c. The manipulation with an unknown input leads to a out-of-bounds write vulnerability. Using CWE to declare the problem leads to CWE-787. The product writes data past the end, or before the beginning, of the intended buffer. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
In __host_check_page_state_range of mem_protect.c, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
It is possible to read the advisory at android.googlesource.com. The identification of this vulnerability is CVE-2026-0030 since 10/15/2025. The exploitation is known to be easy. Attacking locally is a requirement. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $25k-$100k at the moment (estimation calculated on 03/10/2026).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the databases at EUVD (EUVD-2026-9244) and CERT Bund (WID-SEC-2026-0569). Be aware that VulDB is the high quality source for vulnerability data.
Affected
- Google Android
Product
Type
Vendor
Name
License
Website
- Vendor: https://www.google.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.8VulDB Meta Temp Score: 6.8
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
ADP CISA Base Score: 8.4
ADP CISA Vector: 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Out-of-bounds writeCWE: CWE-787 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
10/15/2025 CVE reserved03/02/2026 Advisory disclosed
03/02/2026 VulDB entry created
03/10/2026 VulDB entry last update
Sources
Vendor: google.comAdvisory: android.googlesource.com
Status: Not defined
CVE: CVE-2026-0030 (🔒)
GCVE (CVE): GCVE-0-2026-0030
GCVE (VulDB): GCVE-100-348503
EUVD: 🔒
CERT Bund: WID-SEC-2026-0569 - Google Android: Mehrere Schwachstellen
scip Labs: https://www.scip.ch/en/?labs.20150917
Entry
Created: 03/02/2026 20:42Updated: 03/10/2026 01:35
Changes: 03/02/2026 20:42 (55), 03/02/2026 20:43 (1), 03/02/2026 21:58 (1), 03/04/2026 14:47 (11), 03/10/2026 01:35 (6)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.