CVE-2017-6507 · cross-distro fix matrix

CVE-2017-6507: 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

Affects 3 Linux releases across 3 (distro × package) combinations.

Fix per ecosystem

Each block below is a distro release where CVE-2017-6507 has a known fix. Run the listed command on that distro to remediate.

Debian bullseye

Source: Debian Security Tracker

apparmor→ fixed in2.11.0-3urgency: not yet assigned
```
sudo apt-get install --only-upgrade -y apparmor
```

Debian bookworm

Source: Debian Security Tracker

apparmor→ fixed in2.11.0-3urgency: not yet assigned
```
sudo apt-get install --only-upgrade -y apparmor
```

Debian trixie

Source: Debian Security Tracker

apparmor→ fixed in2.11.0-3urgency: not yet assigned
```
sudo apt-get install --only-upgrade -y apparmor
```

Are YOU affected by CVE-2017-6507?

5-second check on your actual server. Reads /etc/os-release, uname -r, and the distro's package manager; matches against this same cross-source index live.

curl https://mindsparkstack.com/scan.sh | bash

Form-based quickscan View on NVD

Continuous monitoring beats manual checking

CVE-2017-6507dropped silently in your distro's update channel. Every new CVE is the same story. StackPatch runs the matcher hourly against all 5 sources and emails the exact remediation when something new applies to one of your servers. From $9/mo, 14-day free trial, cancel anytime.

See StackPatch (from $9/mo)