Local privilege escalation via confused-deputy memory corruption
Published Sep 15, 2026 · Updated Sep 15, 2026
Memory corruption in the Android kernel allows local users with System execution privileges to escalate privileges without user interaction. Google identifies gmc_mb_msg_handler in gmc_mba.c as the confused-deputy locus that corrupts memory but does not disclose the faulty operation. Exploitation requires local access with System execution privileges; successful exploitation raises privileges beyond that context.
Summary
What happened
Memory corruption in the Android kernel allows local users with System execution privileges to escalate privileges without user interaction. Google identifies gmc_mb_msg_handler in gmc_mba.c as the confused-deputy locus that corrupts memory but does not disclose the faulty operation. Exploitation requires local access with System execution privileges; successful exploitation raises privileges beyond that context.
The record
- CVE
- CVE-2026-56879
- Published
- Sep 15, 2026
- Updated
- Sep 15, 2026
- Vendor
- Product
- Android
- Classifications
- T1068
- Attack vector
- local
- Privileges
- admin
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