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