Google Android 16/16-qpr2/17 rw_ci.cc rw_ci_data_cback integer underflow
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $5k-$25k | 0.40- |
Summary
A vulnerability identified as problematic has been detected in Google Android 16/16-qpr2/17. This impacts the function rw_ci_data_cback of the file rw_ci.cc. The manipulation leads to integer underflow.
This vulnerability is uniquely identified as CVE-2026-55292. The attack is possible to be carried out remotely. No exploit exists.
It is suggested to install a patch to address this issue.
Details
A vulnerability, which was classified as problematic, has been found in Google Android 16/16-qpr2/17. This issue affects the function rw_ci_data_cback of the file rw_ci.cc. The manipulation with an unknown input leads to a integer underflow vulnerability. Using CWE to declare the problem leads to CWE-191. The product subtracts one value from another, such that the result is less than the minimum allowable integer value, which produces a value that is not equal to the correct result. Impacted is confidentiality. The summary by CVE is:
In rw_ci_data_cback of rw_ci.cc, there is a possible memory safety issue due to integer underflow. This could lead to remote information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.
The advisory is shared at source.android.com. The identification of this vulnerability is CVE-2026-55292 since 06/16/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 11/02/2026).
Applying a patch is able to eliminate this problem.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.google.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
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: Integer underflowCWE: CWE-191 / CWE-189
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
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: PatchStatus: 🔍
0-Day Time: 🔒
Timeline
06/16/2026 CVE reserved11/02/2026 Advisory disclosed
11/02/2026 VulDB entry created
11/02/2026 VulDB entry last update
Sources
Vendor: google.comAdvisory: source.android.com
Status: Confirmed
CNA: google_android
CVE: CVE-2026-55292 (🔒)
GCVE (CVE): GCVE-0-2026-55292
GCVE (VulDB): GCVE-100-429977
scip Labs: https://www.scip.ch/en/?labs.20150917
Entry
Created: 11/02/2026 21:08Changes: 11/02/2026 21:08 (58)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.