PT-2026-151716
CVE-2026-99505
·
Published
2026-11-19
·
Updated
2026-11-19
Description by
Score
N/A
Not availableNo severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.
In the Linux kernel, the following vulnerability has been resolved:
apparmor: fix a use-after-free in aa lookupn ns()
aa lookupn ns() takes a reference on the namespace it finds with
aa get ns(), which is kref get() on the reference count that the
namespace is released through, without checking whether the namespace
is still in use. A concurrent removal of a ":"-prefixed namespace
looks the same namespace up and only then takes the parent lock to
remove it, so the last reference can be dropped between the lookup and
the aa get ns() call: the reference count then reports the increment on
a zero count and the kernel classifies the following use of the object
as a use-after-free. A user with CAP MAC ADMIN can trigger this by
writing a ":" removal and a ":/" removal to
/sys/kernel/security/apparmor/.remove concurrently.
refcount t: addition on 0; use-after-free.
WARNING: lib/refcount.c:25 at refcount warn saturate+0xc0/0xe0, CPU#6
Call Trace:
aa lookupn ns+0xa9/0xc0
aa remove profiles+0x4fb/0x730
? kvmalloc node noprof+0x219/0x5c0
? pfx aa remove profiles+0x10/0x10
? aa loaddata alloc+0x65/0x1f0
? copy from user+0x2d/0x80
? aa loaddata alloc+0x111/0x1f0
profile remove+0x2ee/0x4a0
vfs write+0x21e/0xcf0
? rcu core+0x29c/0x1740
? timerqueue linked add+0x1f4/0x3d0
? pfx vfs write+0x10/0x10
? mutex lock+0x81/0xe0
? pfx mutex lock+0x10/0x10
? pfx rcu core+0x10/0x10
? pfx hrtimer update next event+0x10/0x10
? mutex unlock+0x7b/0xd0
? fdget pos+0x24d/0x4b0
ksys write+0xf7/0x1c0
? pfx ksys write+0x10/0x10
? restore fpregs from fpstate+0x37/0xc0
do syscall 64+0xf9/0x540
entry SYSCALL 64 after hwframe+0x77/0x7f
Fix by rejecting a namespace whose reference count is zero.
Found an issue in the description? Have something to add? Feel free to write us 👾