CVE-2016-0728
A public proof of concept exists; no exploitation attested.
- Published2016-02-08
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
The join_session_keyring function in security/keys/process_keys.c in the Linux kernel before 4.4.1 mishandles object references in a certain error case, which allows local users to gain privileges or cause a denial of service (integer overflow and use-after-free) via crafted keyctl commands.
Timeline
dates in UTC- 2016-02-0803:59CVE publishedNVD
- 2026-10-2319:23First public proof of conceptPoC-in-GitHub
Observed activity
isMalicious corpus · updated 2026-10-23 18:48 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2016-0728?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2016-0728?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 4.0 | = 4.0 | no fix published | NVD |
| 4.0 | = 4.0.1 | no fix published | NVD |
| 4.0 | = 4.0.2 | no fix published | NVD |
| 4.0 | = 4.0.3 | no fix published | NVD |
| 4.0 | = 4.0.4 | no fix published | NVD |
| 4.1 | = 4.1 | no fix published | NVD |
| 4.1 | = 4.1.2 | no fix published | NVD |
| 4.2 | = 4.2 | no fix published | NVD |
| 4.2 | = 4.2.1 | no fix published | NVD |
| 4.2 | = 4.2.2 | no fix published | NVD |
| 4.3 | = 4.3 | no fix published | NVD |
| 4.3 | = 4.3.1 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 4.4 | ≥ 4.4, < 4.4.1 | 4.4.1 | NVD |
| 4.x | ≥ 4.2, < 4.3.4 | 4.3.4 | NVD |
| 4.1 | ≥ 3.19, < 4.1.16 | 4.1.16 | NVD |
| 3.x | ≥ 3.17, < 3.18.26 | 3.18.26 | NVD |
| 3.x | ≥ 3.15, < 3.16.35 | 3.16.35 | NVD |
| 3.x | ≥ 3.13, < 3.14.59 | 3.14.59 | NVD |
| 3.x | ≥ 3.11, < 3.12.53 | 3.12.53 | NVD |
| 3.x | ≥ 3.8, < 3.10.95 | 3.10.95 | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 12.4 | = 12.04 | no fix published | NVD |
| 14.4 | = 14.04 | no fix published | NVD |
| 15.4 | = 15.04 | no fix published | NVD |
| 15.10 | = 15.10 | no fix published | NVD |
2 more products in the sources.
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
Advisories and patches
- git.kernel.orgVendor Advisory
- source.android.comVendor Advisory
- www.kernel.orgVendor Advisory
Detection
read 2026-10-23 19:23 UTC- Nuclei template
- none so far ProjectDiscovery
- Proof-of-concept repositories
- 9 repositories, unverifiedkennetham/cve_2016_0728nardholio/cve-2016-0728googleweb/CVE-2016-0728neuschaefer/cve-2016-0728-testbedbittorrent3389/cve-2016-0728 PoC-in-GitHub
Sources
- NVDCVSS 3.17.8read 2026-10-23
- NVDCVSS 2.07.2read 2026-10-23
- FIRST EPSSEPSS score3.4 %2026-10-22
- PoC-in-GitHubproof of concept9read 2026-10-23
- Exploit-DBdetectionread 2026-10-23
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Published
- 2016-02-08
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2016-0728?
Is CVE-2016-0728 actively exploited?
What is the CVSS score for CVE-2016-0728?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.