Google Android TIPC Virtio Device tipc_virtio_dev.c tipc_dev_probe off-by-one
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.4 | $5k-$25k | 0.00 |
Summary
A vulnerability was found in Google Android and classified as very critical. Affected by this issue is the function tipc_dev_probe of the file tipc_virtio_dev.c of the component TIPC Virtio Device. The manipulation results in off-by-one.
This vulnerability is cataloged as CVE-2026-57043. The attack must be initiated from a local position. There is no exploit available.
Applying a patch is advised to resolve this issue.
Details
A vulnerability, which was classified as very critical, was found in Google Android (the affected version is unknown). Affected is the function tipc_dev_probe of the file tipc_virtio_dev.c of the component TIPC Virtio Device. The manipulation with an unknown input leads to a off-by-one vulnerability. CWE is classifying the issue as CWE-193. A product calculates or uses an incorrect maximum or minimum value that is 1 more, or 1 less, than the correct value. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:
In tipc_dev_probe of tipc_virtio_dev.c, there is a possible way to corrupt memory via an off-by-one cleanup loop on probe failure due to a logic error. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation.
The advisory is shared for download at source.android.com. This vulnerability is traded as CVE-2026-57043 since 06/23/2026. The exploitability is told to be easy. The attack needs to be approached locally. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $5k-$25k (estimation calculated on 11/10/2026).
Applying a patch is able to eliminate this problem.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
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: 8.8VulDB Meta Temp Score: 8.4
VulDB Base Score: 8.8
VulDB Temp Score: 8.4
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: Off-by-oneCWE: CWE-193 / CWE-189
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
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/23/2026 CVE reserved11/10/2026 Advisory disclosed
11/10/2026 VulDB entry created
11/10/2026 VulDB entry last update
Sources
Vendor: google.comAdvisory: source.android.com
Status: Confirmed
CNA: Google_Devices
CVE: CVE-2026-57043 (🔒)
GCVE (CVE): GCVE-0-2026-57043
GCVE (VulDB): GCVE-100-434424
scip Labs: https://www.scip.ch/en/?labs.20150917
Entry
Created: 11/10/2026 20:57Changes: 11/10/2026 20:57 (58)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.