Google Android Kernel File System use after free

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.
7.6$5k-$25k0.00

Summaryinfo

A vulnerability, which was classified as very critical, was found in Google Android. Affected is an unknown function of the component Kernel File System. Executing a manipulation can lead to use after free. This vulnerability is handled as CVE-2016-7911. It is possible to launch the attack on the local host. There is not any exploit available. A patch should be applied to remediate this issue.

Detailsinfo

A vulnerability classified as very critical was found in Google Android (Smartphone Operating System) (affected version not known). This vulnerability affects some unknown functionality of the component Kernel File System. The manipulation with an unknown input leads to a use after free vulnerability. The CWE definition for the vulnerability is CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:

Race condition in the get_task_ioprio function in block/ioprio.c in the Linux kernel before 4.6.6 allows local users to gain privileges or cause a denial of service (use-after-free) via a crafted ioprio_get system call.

The weakness was released 11/07/2016 as Android Security Bulletin - November 2016 as confirmed security bulletin (Website). The advisory is available at source.android.com. This vulnerability was named CVE-2016-7911 since 09/09/2016. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Successful exploitation requires user interaction by the victim. The technical details are unknown and an exploit is not available. The structure of the vulnerability defines a possible price range of USD $5k-$25k at the moment (estimation calculated on 09/30/2022). It is expected to see the exploit prices for this product increasing in the near future.

As 0-day the estimated underground price was around $25k-$100k. The vulnerability scanner Nessus provides a plugin with the ID 95705 (openSUSE Security Update : the Linux Kernel (openSUSE-2016-1431)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family SuSE Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 169577 (OpenSuSE Security Update for the Linux Kernel (openSUSE-SU-2016:3061-1)).

Applying a patch is able to eliminate this problem. A possible mitigation has been published immediately after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at Tenable (95705) and SecurityFocus (BID 94135†). Entries connected to this vulnerability are available at VDB-93476, VDB-93458, VDB-93459 and VDB-93460. Once again VulDB remains the best source for vulnerability data.

Productinfo

Type

Vendor

Name

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.8
VulDB Meta Temp Score: 7.6

VulDB Base Score: 7.8
VulDB Temp Score: 7.5
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 7.8
NVD Vector: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Use after free
CWE: CWE-416 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 95705
Nessus Name: openSUSE Security Update : the Linux Kernel (openSUSE-2016-1431)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 802886
OpenVAS Name: SuSE Update for Kernel openSUSE-SU-2016:3061-1 (Kernel)
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Patch
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍

Patch: git.kernel.org

Timelineinfo

09/09/2016 🔍
11/07/2016 +59 days 🔍
11/07/2016 +0 days 🔍
11/08/2016 +1 days 🔍
11/09/2016 +1 days 🔍
11/16/2016 +7 days 🔍
12/12/2016 +26 days 🔍
09/30/2022 +2118 days 🔍

Sourcesinfo

Vendor: google.com

Advisory: Android Security Bulletin - November 2016
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2016-7911 (🔍)
GCVE (CVE): GCVE-0-2016-7911
GCVE (VulDB): GCVE-100-93466
SecurityFocus: 94135 - Linux kernel Local Use After Free Multiple Denial of Service Vulnerabilities

scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍

Entryinfo

Created: 11/09/2016 14:43
Updated: 09/30/2022 14:08
Changes: 11/09/2016 14:43 (67), 05/28/2019 16:04 (13), 09/30/2022 14:08 (4)
Complete: 🔍
Cache ID: 216:C5B:103

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!