apparmor: fix unconfined user namespace restriction forced stack
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 08c2f7c8d4b1434cfae006f3daf4d1bce330b57b, Kernel 7d1099b86356df81c379159bfb8a598aaf83ce81, Kernel 7da0bdf0610f6d35bbb061536a47fc41646306f0 and 1 more.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.7, >=2d9da9b188b8cd3b579d7ef5ba5d334be9dd38fc <08c2f7c8d4b1434cfae006f3daf4d1bce330b57b, >=2d9da9b188b8cd3b579d7ef5ba5d334be9dd38fc <7d1099b86356df81c379159bfb8a598aaf83ce81, >=2d9da9b188b8cd3b579d7ef5ba5d334be9dd38fc <7da0bdf0610f6d35bbb061536a47fc41646306f0, >=2d9da9b188b8cd3b579d7ef5ba5d334be9dd38fc <fdd341654471cae4fbd9635d32b848cd0c8bc437 | 08c2f7c8d4b1434cfae006f3daf4d1bce330b57b, 7d1099b86356df81c379159bfb8a598aaf83ce81, 7da0bdf0610f6d35bbb061536a47fc41646306f0, fdd341654471cae4fbd9635d32b848cd0c8bc437 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket