apparmor: fix unconfined user namespace restriction forced stack
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.12.114, 6.18.52, 7.2.6
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In the Linux kernel, the following vulnerability has been resolved: apparmor: fix unconfined user namespace restriction forced stack If a task is already confined by a stack the unprivileged transition restriction on unconfined is not correctly, applied. This results in an escape if two transitions through an unconfined profile can be executed. Fix this by pushing the check into the per profile label build. The check will always be done against unconfined and result in a stack of just the unconfined component when necessary.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 2d9da9b188b8cd3b579d7ef5ba5d334be9dd38fc · fixed in fdd341654471cae4fbd9635d32b848cd0c8bc437; From 2d9da9b188b8cd3b579d7ef5ba5d334be9dd38fc · fixed in 7d1099b86356df81c379159bfb8a598aaf83ce81; From 2d9da9b188b8cd3b579d7ef5ba5d334be9dd38fc · fixed in 7da0bdf0610f6d35bbb061536a47fc41646306f0; From 2d9da9b188b8cd3b579d7ef5ba5d334be9dd38fc · fixed in 08c2f7c8d4b1434cfae006f3daf4d1bce330b57b
- Linux Linux
6.7
- KernelLinux
From 6.7.0 · fixed in 6.12.114; From 6.13.0 · fixed in 6.18.52; From 6.19.0 · fixed in 7.2.6