Google Android gasket_page_table.c gasket_alloc_coherent_memory memory corruption

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
4.0$0-$5k0.00

Summaryinfo

A vulnerability marked as critical has been reported in Google Android. This impacts the function gasket_alloc_coherent_memory of the file gasket_page_table.c. This manipulation causes memory corruption. This vulnerability is registered as CVE-2021-39735. The attack needs to be launched locally. No exploit is available. Applying a patch is the recommended action to fix this issue.

Detailsinfo

A vulnerability was found in Google Android (Smartphone Operating System) (the affected version is unknown). It has been declared as critical. Affected by this vulnerability is the function gasket_alloc_coherent_memory of the file gasket_page_table.c. The manipulation with an unknown input leads to a memory corruption vulnerability. The CWE definition for the vulnerability is CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. As an impact it is known to affect confidentiality, integrity, and availability.

The weakness was published 03/17/2022 as A-151455484. The advisory is shared at source.android.com. This vulnerability is known as CVE-2021-39735 since 08/23/2021. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 03/17/2022). It is expected to see the exploit prices for this product increasing in the near future.

Applying a patch is able to eliminate this problem.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.2
VulDB Meta Temp Score: 4.0

VulDB Base Score: 4.2
VulDB Temp Score: 4.0
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Memory corruption
CWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: No

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Patch
Status: 🔍

0-Day Time: 🔍

Timelineinfo

08/23/2021 🔍
03/17/2022 +206 days 🔍
03/17/2022 +0 days 🔍
03/19/2022 +2 days 🔍

Sourcesinfo

Vendor: google.com

Advisory: A-151455484
Status: Confirmed

CVE: CVE-2021-39735 (🔍)
GCVE (CVE): GCVE-0-2021-39735
GCVE (VulDB): GCVE-100-195325
scip Labs: https://www.scip.ch/en/?labs.20150917

Entryinfo

Created: 03/17/2022 08:08
Updated: 03/19/2022 16:39
Changes: 03/17/2022 08:08 (41), 03/19/2022 16:39 (1)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to know what is going to be exploited?

We predict KEV entries!