CVE-2016-5195: Dirty COW
- Vendors
- NetAppDebian ProjectRed HatFedora ProjectLinuxPalo Alto NetworksCanonical
Dirty COW is a local privilege-escalation vulnerability in the Linux kernel's memory-management subsystem affecting Linux kernel versions 2.x through 4.x before 4.8.3, unless a vendor fix has been backported. Incorrect synchronization of copy-on-write handling allows an unprivileged process to race memory-management operations and write to a read-only memory mapping. Attackers can use this capability to modify otherwise protected root-owned files or setuid executables and obtain root privileges. Linux-based Android devices are also affected when their kernels lack the fix. Exploitation in the wild was documented in October 2016.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation can compromise system confidentiality, integrity, and availability by elevating an unprivileged local process to root. Attackers can alter protected executables or authentication data, access sensitive information, disable security controls, and establish privileged persistence. Observed Android exploitation has enabled root backdoors, security-policy bypasses, concealed payment fraud, and spyware access to communications. These follow-on effects depend on the exploit and platform security context.
Mitigation
If you can’t patch tonight, do this now.
Until patched, restrict untrusted local access and execution, disable unnecessary services that could provide an initial foothold, and enforce least privilege. On Android, limit application installation to trusted sources and retain application-protection controls. These measures reduce exposure but do not correct the kernel race condition or reliably prevent exploitation by code already executing locally.
Remediation
Patch, then assume compromise.
Install the Linux distribution or device vendor's kernel update addressing CVE-2016-5195. Upstream Linux 4.8.3 contains the fix; older version numbers may also be secure when the vendor has backported it. Reboot into the patched kernel and verify that the running kernel includes the correction. For Android and embedded products, obtain the applicable firmware or security update from the manufacturer or carrier.
Exploits
26 exploits validated by Mallory's analysis. Hidden: 13 rejected by Mallory's analysis as not a working exploit; 6 not yet analyzed, such as Exploit-DB entries. Showing the 25 most capable, earliest first.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2016-5195 exploited in the wild?
- Yes. As of Nov 18, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Mar 3, 2022.
- Is there a public exploit for CVE-2016-5195?
- Yes. Mallory tracks 26 public exploits or proofs of concept for CVE-2016-5195, the earliest disclosed Oct 21, 2016.
- Is there a patch for CVE-2016-5195?
- Install the Linux distribution or device vendor's kernel update addressing CVE-2016-5195. Upstream Linux 4.8.3 contains the fix; older version numbers may also be secure when the vendor has backported it.
- What products are affected by CVE-2016-5195?
- Linux Kernel, NetApp Cloud Backup, Debian Project Debian Linux, Red Hat Enterprise Linux Aus, Red Hat Enterprise Linux Eus, and 13 more.
- How severe is CVE-2016-5195?
- CVE-2016-5195 has a CVSS v3.1 score of 7.0 (High) and an EPSS score of 83.5% (100th percentile) as of Nov 18, 2026.
Recent activity
49 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.