Quick answers
- Is CVE-2026-56930 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-56930 being exploited in the wild.
- How severe is CVE-2026-56930?
- Informational severity, published 10 November 2026.
- Which products and versions are affected?
- Google Android kernel before 2026-11-05 patch level.
- Is there a fix for CVE-2026-56930?
- Yes: fixed in Android security patch level 2026-11-05 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-56930 attacked?
- It is attacked with local access, in an operating system.
- Am I affected by CVE-2026-56930?
- Check whether you run Google Android kernel 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.
How to fix
- Fixed in: Android security patch level 2026-11-05 or later
Technical details
In smmu_find_ste of smmu.c, a confused deputy vulnerability allows stale TLB entries to persist across stream identifiers, breaking memory isolation boundaries. The attack is local, requires no special privileges, and results in privilege escalation by leveraging cached translations for unauthorized memory access.
Affected products
- Google Android kernel before 2026-11-05 patch level
Timeline
- 2026-11-10: disclosed
- 2026-11-05: patched