CVE-2026-90231: Linux kernel · apparmor: fix unconfined user namespace restriction forced stack
Affects Linux kernelSource CVE Database V5
Not known to be exploited · CVSS 8.4 High · fixed in fdd341654471cae4fbd9635d32b848cd0c8bc437 : patch Linux kernel soon.
Data as of 26 Oct 2026, 13:47 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in fdd341654471cae4fbd9635d32b848cd0c8bc437, 08c2f7c8d4b1434cfae006f3daf4d1bce330b57b, 7da0bdf0610f6d35bbb061536a47fc41646306f0 +1
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 17 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade Linux kernel to fdd341654471cae4fbd9635d32b848cd0c8bc437, 08c2f7c8d4b1434cfae006f3daf4d1bce330b57b, 7da0bdf0610f6d35bbb061536a47fc41646306f0 or 7d1099b86356df81c379159bfb8a598aaf83ce81.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
Description
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.
References
- git.kernel.org/stable/c/fdd341654471cae4fbd9635d32b848cd0c8bc437 (opens in a new tab)
- git.kernel.org/stable/c/7d1099b86356df81c379159bfb8a598aaf83ce81 (opens in a new tab)
- git.kernel.org/stable/c/7da0bdf0610f6d35bbb061536a47fc41646306f0 (opens in a new tab)
- git.kernel.org/stable/c/08c2f7c8d4b1434cfae006f3daf4d1bce330b57b (opens in a new tab)