CVE-2026-99505: Linux kernel · apparmor: fix a use-after-free in aa_lookupn_ns()
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in f292873ceb4bd3a1a0f75f884361cd556e457692 : patch Linux kernel soon.
Data as of 19 Nov 2026, 15:34 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in f292873ceb4bd3a1a0f75f884361cd556e457692, 2588c5693f4535e856841976cb1e1532bae77109, 174b4b90ec6731934cf84eb267a86ad7152267fa +1
Exploitation evidence
Disclosed: evidence found.
CVE published 19 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 18 Nov 2026.
What to do
Upgrade Linux kernel to f292873ceb4bd3a1a0f75f884361cd556e457692, 2588c5693f4535e856841976cb1e1532bae77109, 174b4b90ec6731934cf84eb267a86ad7152267fa or 8db1a8614b4f8f3da11c568e2b5af4fe56eef360.
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– |
AI-suggested
A fix is available and has been applied in the Linux kernel. Users and administrators should update to a kernel version that includes the fix identified by the commits f292873ceb4bd3a1a0f75f884361cd556e457692, 2588c5693f4535e856841976cb1e1532bae77109, 174b4b90ec6731934cf84eb267a86ad7152267fa, or 8db1a8614b4f8f3da11c568e2b5af4fe56eef360. No additional mitigation is required beyond applying the official patch.
Description
A use-after-free vulnerability was identified and fixed in the Linux kernel's AppArmor module in the function aa_lookupn_ns(). This flaw occurs when a namespace's reference count is incorrectly incremented after it has reached zero, leading to potential use of freed memory. The issue can be triggered by a user with CAP_MAC_ADMIN privileges by concurrently removing certain AppArmor namespaces. The fix involves rejecting namespaces whose reference count is zero to prevent this unsafe operation.
References
- git.kernel.org/stable/c/2588c5693f4535e856841976cb1e1532bae77109 (opens in a new tab)
- git.kernel.org/stable/c/174b4b90ec6731934cf84eb267a86ad7152267fa (opens in a new tab)
- git.kernel.org/stable/c/8db1a8614b4f8f3da11c568e2b5af4fe56eef360 (opens in a new tab)
- git.kernel.org/stable/c/f292873ceb4bd3a1a0f75f884361cd556e457692 (opens in a new tab)