Local privilege escalation via permissive firmware mapping
Published Dec 16, 2022 · Updated Apr 17, 2025
Permissive memory allocation in Arm Trusted Firmware-A on affected Pixel devices allows local users to escalate privileges without interaction. The mmu_map_for_fw function in gs_ldfw_load.c maps firmware memory with permissions broad enough to bypass the intended mitigation. Local users need no additional execution privileges to reach the flaw, and the published record identifies no narrower consequence.
Summary
What happened
Permissive memory allocation in Arm Trusted Firmware-A on affected Pixel devices allows local users to escalate privileges without interaction. The mmu_map_for_fw function in gs_ldfw_load.c maps firmware memory with permissions broad enough to bypass the intended mitigation. Local users need no additional execution privileges to reach the flaw, and the published record identifies no narrower consequence.
The record
- CVE
- CVE-2022-42531
- Published
- Dec 16, 2022
- Updated
- Apr 17, 2025
- Vendor
- Arm
- Product
- Trusted Firmware-A
- Classifications
- CWE-770, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 16, 2022CVE publishedPublication date reported by the CVE source.
- Apr 17, 2025Record 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