Google Android gs_ldfw_load.c mmu_map_for_fw allocation of resources
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $0-$5k | 0.00 |
Summary
A vulnerability described as problematic has been identified in Google Android. Affected by this issue is the function mmu_map_for_fw of the file gs_ldfw_load.c. The manipulation results in allocation of resources.
This vulnerability was named CVE-2022-42531. The attack needs to be approached locally. There is no available exploit.
It is advisable to implement a patch to correct this issue.
Details
A vulnerability, which was classified as problematic, was found in Google Android (Smartphone Operating System) (unknown version). Affected is the function mmu_map_for_fw of the file gs_ldfw_load.c. The manipulation with an unknown input leads to a allocation of resources vulnerability. CWE is classifying the issue as CWE-770. The product allocates a reusable resource or group of resources on behalf of an actor without imposing any restrictions on the size or number of resources that can be allocated, in violation of the intended security policy for that actor. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:
In mmu_map_for_fw of gs_ldfw_load.c, there is a possible mitigation bypass due to Permissive Memory Allocation. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-231500967References: N/A
The weakness was presented 12/19/2022 as A-231500967. The advisory is shared for download at source.android.com. This vulnerability is traded as CVE-2022-42531 since 10/07/2022. There are known technical details, but no exploit is available.
Applying a patch is able to eliminate this problem.
Once again VulDB remains the best source for vulnerability data.
Product
Type
Vendor
Name
License
Website
- Vendor: https://www.google.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.5VulDB Meta Temp Score: 6.4
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.8
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Allocation of resourcesCWE: CWE-770 / CWE-400 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
0-Day Time: 🔍
Timeline
10/07/2022 🔍12/19/2022 🔍
12/19/2022 🔍
04/17/2025 🔍
Sources
Vendor: google.comAdvisory: A-231500967
Status: Confirmed
CVE: CVE-2022-42531 (🔍)
GCVE (CVE): GCVE-0-2022-42531
GCVE (VulDB): GCVE-100-216228
scip Labs: https://www.scip.ch/en/?labs.20150917
Entry
Created: 12/19/2022 09:22Updated: 04/17/2025 23:24
Changes: 12/19/2022 09:22 (41), 04/17/2025 23:24 (27)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.