LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Arun Raghavan <arunsr@cse.iitk.ac.in>
To: linux-kernel@vger.kernel.org
Cc: dhowells@redhat.com, satyam@infradead.org
Subject: [PATCH] keyring: Incorrect permissions checking in __keyring_search_one()
Date: Sat, 8 Mar 2008 22:52:47 +0530 (IST) [thread overview]
Message-ID: <Pine.LNX.4.64.0803082235430.27953@peripatetic.hades> (raw)
The __keyring_search_one() function currently has 2 issues with regards
to permissions:
1. It does not check for KEY_SEARCH on the keyring before performing a
search
2. It accepts a "perm" parameter to check whether a given key in the
keyring may be returned. This is incorrect, because it *must* check
for KEY_SEARCH on the key before considering it a candidate for a
match (and only KEY_SEARCH, since it is merely a search function).
In fact, it's only caller, key_create_or_update() passes 0 as the
permissions to check for (=> a key will be returned even if it
doesn't have KEY_SEARCH set)
The second was discovered by Satyam Sharma <satyam@infradead.org>. Here
is a patch that fixes both issues.
Signed-off-by: Arun Raghavan <arunsr@cse.iitk.ac.in>
Acked-by: Satyam Sharma <satyam@infradead.org>
diff --git a/security/keys/internal.h b/security/keys/internal.h
index d36d693..94bffb8 100644
--- a/security/keys/internal.h
+++ b/security/keys/internal.h
@@ -83,8 +83,7 @@ extern int __key_link(struct key *keyring, struct key *key);
extern key_ref_t __keyring_search_one(key_ref_t keyring_ref,
const struct key_type *type,
- const char *description,
- key_perm_t perm);
+ const char *description);
extern struct key *keyring_search_instkey(struct key *keyring,
key_serial_t target_id);
diff --git a/security/keys/key.c b/security/keys/key.c
index ca1d921..524249a 100644
--- a/security/keys/key.c
+++ b/security/keys/key.c
@@ -800,8 +800,7 @@ key_ref_t key_create_or_update(key_ref_t keyring_ref,
* update that instead if possible
*/
if (ktype->update) {
- key_ref = __keyring_search_one(keyring_ref, ktype, description,
- 0);
+ key_ref = __keyring_search_one(keyring_ref, ktype, description);
if (!IS_ERR(key_ref))
goto found_matching_key;
}
diff --git a/security/keys/keyring.c b/security/keys/keyring.c
index 88292e3..c7f6fd2 100644
--- a/security/keys/keyring.c
+++ b/security/keys/keyring.c
@@ -446,17 +446,22 @@ EXPORT_SYMBOL(keyring_search);
*/
key_ref_t __keyring_search_one(key_ref_t keyring_ref,
const struct key_type *ktype,
- const char *description,
- key_perm_t perm)
+ const char *description)
{
struct keyring_list *klist;
unsigned long possessed;
struct key *keyring, *key;
int loop;
+ long err;
keyring = key_ref_to_ptr(keyring_ref);
possessed = is_key_possessed(keyring_ref);
+ /* the keyring must have search permission to begin the search */
+ err = key_permission(keyring_ref, KEY_SEARCH);
+ if (err < 0)
+ return ERR_PTR(err);
+
rcu_read_lock();
klist = rcu_dereference(keyring->payload.subscriptions);
@@ -468,7 +473,7 @@ key_ref_t __keyring_search_one(key_ref_t keyring_ref,
(!key->type->match ||
key->type->match(key, description)) &&
key_permission(make_key_ref(key, possessed),
- perm) == 0 &&
+ KEY_SEARCH) == 0 &&
!test_bit(KEY_FLAG_REVOKED, &key->flags)
)
goto found;
next reply other threads:[~2008-03-08 17:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-08 17:22 Arun Raghavan [this message]
2008-03-10 12:25 ` David Howells
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.64.0803082235430.27953@peripatetic.hades \
--to=arunsr@cse.iitk.ac.in \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=satyam@infradead.org \
--subject='Re: [PATCH] keyring: Incorrect permissions checking in __keyring_search_one()' \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).