CVE-2016-5195

CVE Published	2016-11-10
Related CWE(s)	CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
Related Vendor(s)	fedoraproject, redhat, linux, canonical, paloaltonetworks, netapp, debian
Related Product(s)	enterprise_linux_long_life, linux_kernel, enterprise_linux, oncommand_performance_manager, fedora, enterprise_linux_eus, cloud_backup, hci_storage_nodes, ubuntu_linux, enterprise_linux_aus, ontap_select_deploy_administration_utility, snapprotect, debian_linux, solidfire, pan-os, oncommand_balance, oncommand_unified_manager_for_clustered_data_ontap, enterprise_linux_tus
Exploitation Reported (CISA KEV)	2022-03-03
CVSS 3 Base Score	7.0 (HIGH)
CVSS 3 Attack Complexity	HIGH
CVSS 3 Attack Vector	LOCAL

Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect handling of a copy-on-write (COW) feature to write to a read-only memory mapping, as exploited in the wild in October 2016, aka "Dirty COW."

Cyber Threat Graph Context

Explore how this CVE relates to the wider threat graph

Threat Reports Related to CVE-2016-5195

Report

Earth Krahang Exploits Intergovernmental Trust to Launch Cross-Government Attacks

This article by researchers at Trend Micro discusses an Advanced Persistent Threat (APT) group they name Earth Krahang who have been observed ...

View Source

Associated CAPEC Patterns

Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions (CAPEC-29)

This attack targets a race condition occurring between the time of check (state) for a resource and the time of use of a resource. A typical example is file access. The adversary can leverage a file access race condition by "running the race", meaning that they would modify the resource between the first time the target program accesses the file and the time the target program uses the file. During that period of time, the adversary could replace or modify the file, causing the application to behave unexpectedly.

Leveraging Race Conditions (CAPEC-26)

The adversary targets a race condition occurring when multiple processes access and manipulate the same resource concurrently, and the outcome of the execution depends on the particular order in which the access takes place. The adversary can leverage a race condition by "running the race", modifying the resource and modifying the normal execution flow. For instance, a race condition can occur while accessing a file: the adversary can trick the system by replacing the original file with their version and cause the system to read the malicious file.

References