apparmor: fix unconfined user namespace restriction forced stack
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s AppArmor handling of unconfined user namespace restrictions does not correctly apply a transition restriction when a task is already confined by a stack. A task that can execute two transitions through an unconfined profile can escape confinement. The input does not specify authentication or user-interaction requirements.
Engineers running Linux kernels with AppArmor should check their systems; affected versions are not specified.