CVE-2016-6187 json
The apparmor_setprocattr function in security/apparmor/lsm.c in the Linux kernel before 4.6.5 does not validate the buffer size, which allo…
published 2016-08-06 10 y ago modified 2026-06-17 4 mo ago also EUVD-2016-7120
- cvss
- 7.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.4%
- EPSS 2.4% chance of exploitation in 30 days, percentile 84%
- public exploits
- 1
- Exploit-DB
Summary
The apparmor_setprocattr function in security/apparmor/lsm.c in the Linux kernel before 4.6.5 does not validate the buffer size, which allows local users to gain privileges by triggering an AppArmor setprocattr hook.
Patch / fix
- linux linux_kernel 4.6.5
- linux Debian 14, Debian 13, Debian 12 4.6.4-1
debian advisories DEBIAN-CVE-2016-6187
- kernel-source openSUSE Tumbleweed 4.8.13-1.1
opensuse advisories openSUSE-SU-2024:10128-1
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2016-6187 updated cvss 7.0
kernel: apparmor: Potential privilege escalation via oops in apparmor_setprocattr()
-
Red Hat Enterprise Linux 5 kernel Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise MRG 2 kernel-rt, mrg-rt-release, kernel-rt-trace, kernel-rt-vanilla, kernel-rt-firmwarenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Timeline
- Published
- First public exploit (EDB-44301)
Exploit prediction
2.40% chance of exploitation in the next 30 days, higher than 84% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-44301 Linux Kernel < 4.5.1 - Off-By-One (PoC) dos, 2016-10-16
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.2 | AV:L/AC:L/Au:N/C:C/I:C/A:C |
Classification
- Weakness
- Technology feeds
References
-
github.com
/torvalds/linux/commit/30a46a4647fd1df9cf52e43bf467f0d9265096ca
issue-tracking, patch
-
git.kernel.org
/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=30a46a4647fd1df9cf52e43bf467f0d9265096ca
issue-tracking, patch
-
kernel.org
/pub/linux/kernel/v4.x/ChangeLog-4.6.5
release-notes
-
openwall.com
/lists/oss-security/2016/07/09/2
mailing-list, third-party-advisory
-
marc.info
/?l=linux-kernel&m=146793642811929&w=2
mailing-list, third-party-advisory
-
bugzilla.redhat.com
/show_bug.cgi?id=1354383
issue-tracking
-
securityfocus.com
/bid/91696
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2016-6187
- NVD CVE-2016-6187
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.