An issue was discovered in AppArmor before 2.12. Incorrect handling of unknown AppArmor profiles in AppArmor init scripts, upstart jobs, and/or systemd unit files allows an attacker to possibly have increased attack surfaces of processes that were intended to be confined by AppArmor. This is due to the common logic to handle 'restart' operations removing AppArmor profiles that aren't found in the typical filesystem locations, such as /etc/apparmor.d/. Userspace projects that manage their own AppArmor profiles in atypical directories, such as what's done by LXD and Docker, are affected by this flaw in the AppArmor init script logic.
The bug has been referenced in the following commit(s):
Author: Michael Palimaka <email@example.com>
AuthorDate: 2017-10-30 12:45:18 +0000
Commit: Michael Palimaka <firstname.lastname@example.org>
CommitDate: 2017-10-30 12:52:57 +0000
sys-apps/apparmor: version bump 2.11.1
This resolves CVE-2017-6507.
Package-Manager: Portage-2.3.8, Repoman-2.3.4
sys-apps/apparmor/Manifest | 1 +
sys-apps/apparmor/apparmor-2.11.1.ebuild | 60 ++++++++++++++++++++++
.../files/apparmor-2.11.1-dynamic-link.patch | 11 ++++
3 files changed, 72 insertions(+)}
*** Bug 636044 has been marked as a duplicate of this bug. ***
Thank you, Michael, please let us know when tree is clean.