Local privilege escalation via kernel unmap race
Published Sep 15, 2026 · Updated Sep 15, 2026
Memory corruption in the Android kernel allows local users to elevate privileges by triggering a race in shared-memory unmapping. The handle_unmap_req function in tipc_virtio_dev.c processes racing unmap requests in a way that permits memory corruption during teardown. Exploitation requires local code execution on an affected Pixel-family device, but no additional privileges or user interaction.
Summary
What happened
Memory corruption in the Android kernel allows local users to elevate privileges by triggering a race in shared-memory unmapping. The handle_unmap_req function in tipc_virtio_dev.c processes racing unmap requests in a way that permits memory corruption during teardown. Exploitation requires local code execution on an affected Pixel-family device, but no additional privileges or user interaction.
The record
- CVE
- CVE-2026-56923
- Published
- Sep 15, 2026
- Updated
- Sep 15, 2026
- Vendor
- Product
- Android
- Classifications
- T1404
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 15, 2026CVE publishedPublication date reported by the CVE source.
- Sep 15, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=Android kernel
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo