From: Cen Zhang <zzzccc427@gmail.com>
To: dhowells@redhat.com, jarkko@kernel.org, paul@paul-moore.com,
jmorris@namei.org, serge@hallyn.com
Cc: keyrings@vger.kernel.org, linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org, baijiaju1990@gmail.com,
jjzuming@gmail.com, zzzccc427@gmail.com
Subject: [PATCH] keys: Protect the update method check against type removal
Date: Thu, 29 Oct 2026 19:58:06 +0800 [thread overview]
Message-ID: <pm-keys-update-type-removal-20261029-v6-3d92b2f9693854230a02@gmail.com> (raw)
key_update() reads key->type->update, ->def_datalen and ->preparse
before it takes key->sem. A reference on the key does not pin the
module that provides its type, so KEYCTL_UPDATE can race with the
unloading of that module, for example dns_resolver:
KEYCTL_UPDATE task Module unload and key GC
------------------ ------------------------
keyctl_update_key()
key_update()
key_permission()
load key->type
exit_dns_resolver()
unregister_key_type()
GC: down_write(&key->sem)
GC: retype to key_type_dead
GC: up_write(&key->sem)
unregister_key_type() returns
free_module()
read saved type's update member
The final access reads freed module memory. With the updating task
held after the key->type load, it faults:
BUG: unable to handle page fault for address: fffffbfff804107f
#PF: supervisor read access in kernel mode
RIP: 0010:key_update+0x12d/0x550
Call Trace:
keyctl_update_key+0x6b/0x110
__do_sys_keyctl+0x21d/0x4f0
This is the same problem that commit 925c84e3cc21 ("keys: Protect the
read method check against type removal") fixed for KEYCTL_READ.
The encrypted and trusted types can be built as modules and have an
update method. For them there is a second window: the GC can move the
key to key_type_dead after the method check and before key_update()
takes key->sem. key_update() then calls the NULL update method of
key_type_dead.
Take key->sem before the first access to key->type and hold it until
the preparsed payload has been freed. Once a key exists, only the GC
changes key->type, and it does so with key->sem held for writing.
unregister_key_type() does not return before the GC has done that for
every key of the type that is still in use, so the type stays valid
for the whole update. If the GC has already moved the key to
key_type_dead when key_update() gets key->sem, there is no update
method and key_update() returns -EOPNOTSUPP.
Assisted-by: LLM
Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
Signed-off-by: Cen Zhang <zzzccc427@gmail.com>
---
security/keys/key.c | 12 +++++++-----
1 file changed, 7 insertions(+), 5 deletions(-)
diff --git a/security/keys/key.c b/security/keys/key.c
index e88548f1a704..bac2333089fc 100644
--- a/security/keys/key.c
+++ b/security/keys/key.c
@@ -1101,9 +1101,13 @@ int key_update(key_ref_t key_ref, const void *payload, size_t plen)
if (ret < 0)
return ret;
+ /* the GC cannot change the key's type while we hold the semaphore */
+ down_write(&key->sem);
+
/* attempt to update it if supported */
+ ret = -EOPNOTSUPP;
if (!key->type->update)
- return -EOPNOTSUPP;
+ goto out;
memset(&prep, 0, sizeof(prep));
prep.data = payload;
@@ -1116,8 +1120,6 @@ int key_update(key_ref_t key_ref, const void *payload, size_t plen)
goto error;
}
- down_write(&key->sem);
-
ret = key->type->update(key, &prep);
if (ret == 0) {
/* Updating a negative key positively instantiates it */
@@ -1125,11 +1127,11 @@ int key_update(key_ref_t key_ref, const void *payload, size_t plen)
notify_key(key, NOTIFY_KEY_UPDATED, 0);
}
- up_write(&key->sem);
-
error:
if (key->type->preparse)
key->type->free_preparse(&prep);
+out:
+ up_write(&key->sem);
return ret;
}
EXPORT_SYMBOL(key_update);
base-commit: 9a2a4c51dccc3168c3dc949fcbaa360a478fa228
--
2.43.0
next reply other threads:[~2026-10-29 11:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-29 11:58 Cen Zhang [this message]
2026-10-29 13:14 ` Jarkko Sakkinen
2026-10-29 14:04 ` Cen Zhang
2026-10-29 15:04 ` Jarkko Sakkinen
2026-10-29 15:49 ` Cen Zhang
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=pm-keys-update-type-removal-20261029-v6-3d92b2f9693854230a02@gmail.com \
--to=zzzccc427@gmail.com \
--cc=baijiaju1990@gmail.com \
--cc=dhowells@redhat.com \
--cc=jarkko@kernel.org \
--cc=jjzuming@gmail.com \
--cc=jmorris@namei.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=serge@hallyn.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®