| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.5 | $0-$5k | 0.00 |
Summary
A vulnerability marked as very critical has been reported in Google Android. The affected element is an unknown function of the component Kernel Memory Subsystem. This manipulation causes race condition. This vulnerability is tracked as CVE-2016-5195. The attack is restricted to local execution. Moreover, an exploit is present. Applying a patch is the recommended action to fix this issue.
Details
A vulnerability was found in Google Android (Smartphone Operating System) (the affected version is unknown). It has been declared as very critical. Affected by this vulnerability is an unknown code of the component Kernel Memory Subsystem. The manipulation with an unknown input leads to a race condition vulnerability. The CWE definition for the vulnerability is CWE-362. The product contains a code sequence that can run concurrently with other code, and the code sequence requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence that is operating concurrently. As an impact it is known to affect confidentiality, integrity, and availability.
The bug was discovered 10/20/2016. The weakness was disclosed 11/07/2016 by Phil Oester as Android Security Bulletin - November 2016 as confirmed security bulletin (Website). The advisory is shared at source.android.com. This vulnerability is known as CVE-2016-5195 since 05/31/2016. The exploitation appears to be easy. An attack has to be approached locally. The exploitation doesn't need any form of authentication. Technical details are unknown but a public exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 01/29/2025). It is expected to see the exploit prices for this product increasing in the near future.
A public exploit has been developed in ANSI C. It is possible to download the exploit at securityfocus.com. It is declared as attacked. The vulnerability was handled as a non-public zero-day exploit for at least 4 days. During that time the estimated underground price was around $25k-$100k. The vulnerability scanner Nessus provides a plugin with the ID 94228 (OracleVM 3.4 : Unbreakable / etc (OVMSA-2016-0149) (Dirty COW)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family OracleVM Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 157314 (Oracle Enterprise Linux Security Update for kernel (ELSA-2016-2574)-Deprecated). The CISA Known Exploited Vulnerabilities Catalog lists this issue since 03/03/2022 with a due date of 03/24/2022:
Apply updates per vendor instructions.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 Exploit-DB (40839), Zero-Day.cz (151), Tenable (94228), SecurityFocus (BID 93793†) and SecurityTracker (ID 1037078†). The entries VDB-82951, VDB-82953, VDB-82963 and VDB-82965 are pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
License
Website
- Vendor: https://www.google.com/
CPE 2.3
CPE 2.2
Video

CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.5VulDB Meta Temp Score: 7.3
VulDB Base Score: 8.4
VulDB Temp Score: 8.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.0
NVD Vector: 🔍
CNA Base Score: 7.0
CNA 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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Race conditionCWE: CWE-362
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
Availability: 🔍
Access: Public
Status: Attacked
Programming Language: 🔍
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
KEV Added: 🔍
KEV Due: 🔍
KEV Remediation: 🔍
KEV Ransomware: 🔍
KEV Notice: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 94228
Nessus Name: OracleVM 3.4 : Unbreakable / etc (OVMSA-2016-0149) (Dirty COW)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍
OpenVAS ID: 65594
OpenVAS Name: Fedora Update for kernel FEDORA-2016-c8a0c7eece
OpenVAS File: 🔍
OpenVAS Family: 🔍
Saint ID: exploit_info/linux_dirty_cow_local_file_overwrite
Saint Name: Linux Dirty COW Local File Overwrite
Qualys ID: 🔍
Qualys Name: 🔍
Exploit-DB: 🔍
Zero-Day.cz: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Patch: git.kernel.org
Timeline
05/31/2016 🔍10/19/2016 🔍
10/20/2016 🔍
10/22/2016 🔍
10/24/2016 🔍
11/07/2016 🔍
11/07/2016 🔍
11/09/2016 🔍
11/10/2016 🔍
01/29/2025 🔍
Sources
Vendor: google.comAdvisory: Android Security Bulletin - November 2016
Researcher: Phil Oester
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2016-5195 (🔍)
GCVE (CVE): GCVE-0-2016-5195
GCVE (VulDB): GCVE-100-93517
OVAL: 🔍
CERT: 🔍
SecurityFocus: 93793 - Linux Kernel CVE-2016-5195 Local Privilege Escalation Vulnerability
SecurityTracker: 1037078
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 11/09/2016 14:43Updated: 01/29/2025 19:43
Changes: 11/09/2016 14:43 (94), 08/13/2019 09:29 (3), 09/30/2022 18:01 (5), 04/23/2024 12:06 (28), 07/07/2024 00:24 (2), 07/24/2024 16:40 (5), 09/09/2024 22:29 (1), 01/27/2025 06:41 (1), 01/29/2025 19:43 (10)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.