# CVE-2026-56923: Google Pixel kernel race condition memory corruption in tipc_virtio_dev

Source: https://junglewise.ai/threats/cve-2026-56923-google-pixel-kernel-race-condition-memory-corruption-in-tipc  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-09-15. Updated: 2026-09-26  
License: CC BY 4.0 with a link back

CVE-2026-56923 · Severity: medium · CVSS 6.4 · Published 2026-09-15

A race condition vulnerability exists in the TIPC (Transparent Inter-Process Communication) virtualization driver component of Google Pixel devices' Linux kernel. An attacker with local access can exploit this memory corruption flaw to escalate privileges without requiring special permissions, potentially gaining full control over the device.

Technologies: [Google Android](https://junglewise.ai/threats/technologies/android), [Google Pixel Devices](https://junglewise.ai/threats/technologies/pixel-devices). Vendors: [Google](https://junglewise.ai/threats/vendors/google).

## Quick answers

**Is CVE-2026-56923 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-56923 being exploited in the wild.

**How severe is CVE-2026-56923?** Medium severity, with a CVSS score of 6.4, published 15 September 2026.

**Which products and versions are affected?** Google Pixel Devices Before 2026-09-05 patch level.

**Is there a fix for CVE-2026-56923?** A patch was published on 2026-09-05: Security patch level 2026-09-05 or later addresses this issue Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-56923 attacked?** It is attacked with local access.

**Am I affected by CVE-2026-56923?** Check whether you run Google Android or Google Pixel Devices at an affected version. 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

A race condition exists in the handle_unmap_req function of tipc_virtio_dev.c in the Linux kernel component used by Google Pixel devices. The vulnerability allows concurrent access to shared memory structures without proper synchronization, leading to memory corruption. An attacker with local code execution capability can trigger the race condition to cause corruption that results in privilege escalation to kernel-level access. The issue affects Pixel devices and is addressed in Android security patch level 2026-09-05 or later; the specific vulnerable code path requires no additional execution privileges beyond local code execution and does not require user interaction.

## Affected products

- Google Pixel devices Before 2026-09-05 patch level

## Timeline

- 2026-09-15: disclosed
- 2026-09-05: patched: Security patch level 2026-09-05 or later addresses this issue

## References

- [https://source.android.com/docs/security/bulletin/pixel/2026/2026-09-01](https://source.android.com/docs/security/bulletin/pixel/2026/2026-09-01)

## Related threats

- [Google Android Bluetooth buffer overflow in acquireMemory](https://junglewise.ai/threats/cve-2026-95405-in-acquirememory-of-bt-bqr-offload-cc-there-is-a-possible-way-to)
- [ST NFC HAL out-of-bounds write in global memory](https://junglewise.ai/threats/cve-2026-95400-in-stnfc-hal-write-of-hal-st21nfc-cc-there-is-a-possible-way-to)
- [Android HEVC decoder buffer overflow in sub_layer_hrd_parameters](https://junglewise.ai/threats/cve-2026-95397-in-sub-layer-hrd-parameters-of-hevc-decoder-there-is-a-possible)
- [Android framework memory exhaustion in message queue handling](https://junglewise.ai/threats/cve-2026-59632-in-respondreceivedmessage-of-mtsmessagecontroller-cpp-there-is-a)
- [Android use-after-free in UssiController connection listener](https://junglewise.ai/threats/cve-2026-59626-in-sendinfo-of-ussicontroller-cpp-there-is-a-possible-way-to)