No advisories yet.
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Mon, 16 Nov 2026 15:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Sun, 15 Nov 2026 00:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Tipc Virtio Driver Off-by-One Memory Corruption Enables Local Privilege Escalation |
Sat, 14 Nov 2026 06:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Google
Google android |
|
| Vendors & Products |
Google
Google android |
Fri, 13 Nov 2026 14:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-693 | |
| Metrics |
cvssV3_1
|
Thu, 12 Nov 2026 19:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Memory Corruption Leading to Local Privilege Escalation via Off‑By‑One Cleanup Loop in Android TIPC Virtio Driver | |
| Weaknesses | CWE-119 CWE-193 |
Thu, 12 Nov 2026 03:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Memory Corruption Leading to Local Privilege Escalation via Off‑By‑One Cleanup Loop in Android TIPC Virtio Driver | |
| Weaknesses | CWE-119 CWE-193 |
Tue, 10 Nov 2026 19:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| References |
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: Google_Devices
Published:
Updated: 2026-11-13T14:01:15.267Z
Reserved: 2026-06-23T16:29:58.945Z
Link: CVE-2026-57043
Updated: 2026-11-13T14:00:21.847Z
Status : Awaiting Analysis
Published: 2026-11-10T20:19:18.373
Modified: 2026-11-13T14:17:56.900
Link: CVE-2026-57043
No data.
OpenCVE Enrichment
Updated: 2026-11-15T00:15:03Z