From: David Howells Date: Wed, 3 Aug 2005 12:19:07 +0000 (+0100) Subject: [PATCH] CAN-2005-2099 Destruction of failed keyring oopses X-Git-Tag: v2.6.12.5~2 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=a3692f99ef19cfb7fe0420837852108450dd8124;p=thirdparty%2Fkernel%2Fstable.git [PATCH] CAN-2005-2099 Destruction of failed keyring oopses The attached patch makes sure that a keyring that failed to instantiate properly is destroyed without oopsing [CAN-2005-2099]. The problem occurs in three stages: (1) The key allocator initialises the type-specific data to all zeroes. In the case of a keyring, this will become a link in the keyring name list when the keyring is instantiated. (2) If a user (any user) attempts to add a keyring with anything other than an empty payload, the keyring instantiation function will fail with an error and won't add the keyring to the name list. (3) The keyring's destructor then sees that the keyring has a description (name) and tries to remove the keyring from the name list, which oopses because the link pointers are both zero. This bug permits any user to take down a box trivially. Signed-off-by: David Howells Signed-off-by: Chris Wright Signed-off-by: Greg Kroah-Hartman --- diff --git a/security/keys/keyring.c b/security/keys/keyring.c index e2ab4f8e7481d..9c175c599fc72 100644 --- a/security/keys/keyring.c +++ b/security/keys/keyring.c @@ -188,7 +188,11 @@ static void keyring_destroy(struct key *keyring) if (keyring->description) { write_lock(&keyring_name_lock); - list_del(&keyring->type_data.link); + + if (keyring->type_data.link.next != NULL && + !list_empty(&keyring->type_data.link)) + list_del(&keyring->type_data.link); + write_unlock(&keyring_name_lock); }