Description
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.
Fixed in Linux distributions
Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.
Debian
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian 14 | apparmor | 2.11.0-3 | — |
| Debian 13 | apparmor | 2.11.0-3 | — |
| Debian 12 | apparmor | 2.11.0-3 | — |
Ubuntu
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Ubuntu 16.04 LTS | apparmor | 2.10.95-0ubuntu2.6 | USN-3247-1 |
| Ubuntu 14.04 LTS | apparmor | 2.10.95-0ubuntu2.6~14.04.1 | USN-3247-1 |
SUSE
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| SLES 12 SP2 | apparmor | 2.8.2-54.1 | SUSE-SU-2017:1151-1 |
| SLES 12 SP1 | apparmor | 2.8.2-54.1 | SUSE-SU-2017:1151-1 |
Show 2 more (older releases, extended support, other products)Fewer releases
| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| SLES for SAP 12 SP2 | apparmor | 2.8.2-54.1 | SUSE-SU-2017:1151-1 |
| SLES for SAP 12 SP1 | apparmor | 2.8.2-54.1 | SUSE-SU-2017:1151-1 |
Advisories 2
- USN-3247-1 apparmor vulnerability Ubuntu Security Notices (USN) · Apr 22, 2026
- SUSE-SU-2017:1151-1 Security update for apparmor SUSE / openSUSE Security Updates · Feb 4, 2026