Local privilege escalation via unchecked SMMU identifiers
Published Dec 8, 2025 · Updated Feb 26, 2026
Out-of-bounds write in Google's Android kernel IOMMU code allows local users to elevate privileges through malformed SMMU stream identifiers. The smmu_alloc_l2_strtab and smmu_get_ste_ptr paths fail to reject a stream ID at or beyond the configured SID limit before indexing or allocating L2 stream-table storage. Exploitation requires an existing low-privileged local context, needs no user interaction, and can compromise kernel-enforced isolation.
Summary
What happened
Out-of-bounds write in Google's Android kernel IOMMU code allows local users to elevate privileges through malformed SMMU stream identifiers. The smmu_alloc_l2_strtab and smmu_get_ste_ptr paths fail to reject a stream ID at or beyond the configured SID limit before indexing or allocating L2 stream-table storage. Exploitation requires an existing low-privileged local context, needs no user interaction, and can compromise kernel-enforced isolation.
The record
- CVE
- CVE-2025-48624
- Published
- Dec 8, 2025
- Updated
- Feb 26, 2026
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-20, CWE-787, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 8, 2025CVE publishedPublication date reported by the CVE source.
- Feb 26, 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?
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