CVE-2016-5195: Linux Kernel Race Condition
Linux Kernel · listed in the CISA catalog of actively exploited vulnerabilities since 2022-03-03.
- CVSS v3.1 (CVE record)
- 7.0
- high
- EPSS (exploit probability, 30 days)
- 84%
- higher than 99.6% of all CVEs
- Added to CISA KEV
- 2022-03-03
- US federal due date 2022-03-24
- Ubuntu priority
- high
CVE-2016-5195 explained
CVE-2016-5195, known as "Dirty COW", is a race condition in mm/gup.c in the Linux kernel. Incorrect handling of copy-on-write lets a local user write to a read-only memory mapping and gain privileges. It was exploited in the wild in October 2016 and is listed in the CISA Known Exploited Vulnerabilities catalog.
Impact
A local user with low privileges can gain elevated privileges by writing to memory mappings that should be read-only. No user interaction is needed. Exploitation requires local access and has high attack complexity, because it depends on winning a race. Successful exploitation can fully compromise confidentiality, integrity and availability of the affected system. The flaw affects Linux kernel 2.x through 4.x before 4.8.3.
Who is affected
The linux source package is affected. Ubuntu 14.04 LTS has a fix in 3.13.0-100.147. Ubuntu 16.04 LTS has a fix in 4.4.0-45.66. Both fixes are in the standard archive. Both releases are end of life, so they should be upgraded to a supported release. Further Ubuntu kernel flavours are listed on the page.
Written with AI from the data on this page and checked against it automatically.
Official description
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."
CISA required action: Apply updates per vendor instructions.
CISA notes
Ubuntu and Debian releases
A server is vulnerable if it has a package built from the listed source package installed in a version lower than the fixed version for its release.
Ubuntu 16.04 LTS·linux
ESM ended
Fixed: 4.4.0-45.66
Ubuntu 14.04 LTS·linux
ESM ended
Fixed: 3.13.0-100.147
4 more Ubuntu kernel flavours (cloud, HWE, low-latency, real-time …) – 4 release entries
- 16.04 linux-raspi2: 4.4.0-1029.36
- 16.04 linux-snapdragon: 4.4.0-1032.36
- 14.04 linux-lts-vivid: 3.19.0-73.81~14.04.1
- 14.04 linux-lts-xenial: 4.4.0-45.66~14.04.1
What to do
- Install the fixed
linuxkernel package for your release:3.13.0-100.147on Ubuntu 14.04 LTS or4.4.0-45.66on Ubuntu 16.04 LTS. - Check the page for other kernel flavours you run and update those too.
- Reboot into the updated kernel. The fix is not active until the system runs the new kernel.
- Confirm after reboot that the running kernel version matches or exceeds the fixed version.
- Plan upgrades of Ubuntu 14.04 LTS and 16.04 LTS systems to a supported release, since both are end of life.
Written with AI from the data on this page and checked against it automatically.
Check and fix on a server
Kernel fixes arrive as a new kernel package (new ABI) through the metapackages, so upgrade the whole system and boot into the new kernel.
1. Show the running kernel and the version of its package
uname -r && dpkg-query -W -f='${Version}\n' "linux-image-$(uname -r)"2. Compare with the fixed version for your release and kernel flavour from the table
I=INSTALLED_VERSION; F=FIXED_VERSION # replace both
dpkg --compare-versions "$I" lt "$F"; case $? in 0) echo vulnerable ;; 1) echo "fixed or newer" ;; *) echo "check the versions" ;; esac3. Install the new kernel, then reboot (or apply a livepatch)
sudo apt update && sudo apt full-upgrade && sudo rebootOn Debian, signed kernel images come from the linux-signed-* source packages; the version to compare is the same.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- No – each attack needs manual steps
- Technical impact
- Total – full control of the component or total information disclosure
Weakness: CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
Questions about CVE-2016-5195
- Can this be exploited remotely?
- No. The attack vector is local. An attacker needs a local account with low privileges on the system. However, it has been exploited in the wild and is in the CISA Known Exploited Vulnerabilities catalog, so treat it as urgent.
- Is installing the updated package enough?
- No. The fixed kernel only takes effect after a reboot. Until then, the system keeps running the vulnerable kernel.
- What does CISA require for this CVE?
- CISA added it to its catalog on 2022-03-03 with a US federal due date of 2022-03-24. The required action is to apply updates per vendor instructions. Known ransomware use is listed as unknown.
Written with AI from the data on this page and checked against it automatically.
References
Vendor
Other advisories
Trackers and catalogs
- Ubuntu CVE tracker
- Debian security tracker
- Ubuntu USN-3104-1
- Ubuntu USN-3104-2
- Ubuntu USN-3105-1
- Ubuntu USN-3105-2
- Ubuntu USN-3106-1
- Ubuntu USN-3106-2
- Ubuntu USN-3106-3
- Ubuntu USN-3106-4
- Ubuntu USN-3107-1
- Ubuntu USN-3107-2
- Advisory (h20566.www2.hpe.com)
- Advisory (dirtycow.ninja)
- Advisory (kc.mcafee.com)
- Advisory (arista.com)
- CVE record (cve.org)
- NVD
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-22. Always confirm with the vendor's or distribution's advisory before patching.