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.
The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data.
Link | Tags |
---|---|
https://github.com/torvalds/linux/commit/30a46a4647fd1df9cf52e43bf467f0d9265096ca | issue tracking patch |
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=30a46a4647fd1df9cf52e43bf467f0d9265096ca | issue tracking patch |
http://www.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.6.5 | release notes |
http://www.openwall.com/lists/oss-security/2016/07/09/2 | third party advisory mailing list |
http://marc.info/?l=linux-kernel&m=146793642811929&w=2 | third party advisory mailing list |
https://bugzilla.redhat.com/show_bug.cgi?id=1354383 | issue tracking |
http://www.securityfocus.com/bid/91696 | vdb entry third party advisory |