Quick answers
- Is CVE-2026-57043 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-57043 being exploited in the wild.
- How severe is CVE-2026-57043?
- Informational severity, published 10 November 2026.
- Which products and versions are affected?
- Google Pixel firmware.
- Is there a fix for CVE-2026-57043?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-57043 attacked?
- It is attacked with local access, in device firmware.
- Am I affected by CVE-2026-57043?
- Check whether you run Google Pixel Firmware. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is an off-by-one error in the cleanup loop within tipc_dev_probe() of tipc_virtio_dev.c, triggered when device probe fails. This logic error allows out-of-bounds memory access during cleanup. The vulnerability requires local execution privileges and is exploitable without user interaction, enabling local privilege escalation to system level.
Affected products
- Google Pixel firmware
Timeline
- 2026-11-10: disclosed