Google Android Kernel Performance Subsystem 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.
6.9$5k-$25k0.00

Summaryinfo

A vulnerability described as critical has been identified in Google Android. Affected by this issue is some unknown functionality of the component Kernel Performance Subsystem. Executing a manipulation can lead to use after free. This vulnerability is registered as CVE-2015-8963. The attack needs to be launched locally. No exploit is available. A patch should be applied to remediate this issue.

Detailsinfo

A vulnerability was found in Google Android (Smartphone Operating System) (unknown version). It has been declared as critical. This vulnerability affects an unknown code block of the component Kernel Performance Subsystem. 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 kernel/events/core.c in the Linux kernel before 4.4 allows local users to gain privileges or cause a denial of service (use-after-free) by leveraging incorrect handling of an swevent data structure during a CPU unplug operation.

The weakness was published 11/07/2016 by Sasha Levin as Android Security Bulletin - November 2016 as confirmed security bulletin (Website). The advisory is available at source.android.com. This vulnerability was named CVE-2015-8963 since 10/03/2016. The exploitation appears to be difficult. 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 10/15/2024). It is expected to see the exploit prices for this product increasing in the near future.

The vulnerability scanner Nessus provides a plugin with the ID 95702 (openSUSE Security Update : the Linux Kernel (openSUSE-2016-1428)), 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 (95702) and SecurityFocus (BID 94207†). Similar entries are available at VDB-93466, VDB-93476, VDB-93458 and VDB-93459. 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.0
VulDB Meta Temp Score: 6.9

VulDB Base Score: 7.0
VulDB Temp Score: 6.7
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 7.0
NVD Vector: 🔍

CNA Base Score: 7.0
CNA 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: 95702
Nessus Name: openSUSE Security Update : the Linux Kernel (openSUSE-2016-1428)
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

10/03/2016 🔍
11/07/2016 +35 days 🔍
11/07/2016 +0 days 🔍
11/07/2016 +0 days 🔍
11/09/2016 +2 days 🔍
11/16/2016 +7 days 🔍
12/12/2016 +26 days 🔍
10/15/2024 +2864 days 🔍

Sourcesinfo

Vendor: google.com

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

CVE: CVE-2015-8963 (🔍)
GCVE (CVE): GCVE-0-2015-8963
GCVE (VulDB): GCVE-100-93490
SecurityFocus: 94207 - Linux Kernel CVE-2015-8963 Use After Free Remote Code Execution Vulnerability

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

Entryinfo

Created: 11/09/2016 14:43
Updated: 10/15/2024 22:24
Changes: 11/09/2016 14:43 (69), 05/28/2019 11:09 (12), 09/30/2022 14:59 (4), 10/15/2024 22:24 (25)
Complete: 🔍
Cache ID: 216:4A7:103

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Might our Artificial Intelligence support you?

Check our Alexa App!