AppArmor: Fix reference to rcu protected pointer outside of rcu_read_lock
authorJohn Johansen <john.johansen@canonical.com>
Tue, 28 Jun 2011 14:06:38 +0000 (15:06 +0100)
committerGreg Kroah-Hartman <gregkh@suse.de>
Fri, 5 Aug 2011 04:58:41 +0000 (21:58 -0700)
commit0635a74b4ab037ed0c6d628d9cc737b949a15731
tree68ad93832badef6bd961831f9d36a603bc6e1678
parente73ff29041b5f8991ef81669a1a9f0553d14766a
AppArmor: Fix reference to rcu protected pointer outside of rcu_read_lock

commit 04fdc099f9c80c7775dbac388fc97e156d4d47e7 upstream.

The pointer returned from tracehook_tracer_task() is only valid inside
the rcu_read_lock.  However the tracer pointer obtained is being passed
to aa_may_ptrace outside of the rcu_read_lock critical section.

Mover the aa_may_ptrace test into the rcu_read_lock critical section, to
fix this.

Kernels affected: 2.6.36 - 3.0

Reported-by: Oleg Nesterov <oleg@redhat.com>
Signed-off-by: John Johansen <john.johansen@canonical.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
security/apparmor/domain.c