Local privilege escalation via S2MPU mitigation bypass
Published Apr 5, 2024 · Updated Feb 28, 2026
Privilege escalation in the S2MPU component of Google Android kernel builds allows local users to gain elevated privileges without interaction. The pblS2mpuResume function in s2mpu.c processes resume-time mitigation state with a logic error that leaves the intended S2MPU protection bypassable. Exploitation requires local low-privilege code execution on affected Pixel hardware and grants privileges beyond those already held.
Summary
What happened
Privilege escalation in the S2MPU component of Google Android kernel builds allows local users to gain elevated privileges without interaction. The pblS2mpuResume function in s2mpu.c processes resume-time mitigation state with a logic error that leaves the intended S2MPU protection bypassable. Exploitation requires local low-privilege code execution on affected Pixel hardware and grants privileges beyond those already held.
The record
- CVE
- CVE-2024-29741
- Published
- Apr 5, 2024
- Updated
- Feb 28, 2026
- Vendor
- Product
- Android
- Classifications
- CWE-269, T1068
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Apr 5, 2024CVE publishedPublication date reported by the CVE source.
- Feb 28, 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
- Affected versionversion=Android kernel
What conditions does exploitation require?
What is affected?
Published CVSS scores
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