From: sashiko-bot@kernel.org
Cc: linux-security-module@vger.kernel.org
Subject: Re: [PATCH v6] KEYS: Protect pkey method checks against type removal
Date: Mon, 09 Nov 2026 06:02:54 +0000 [thread overview]
Message-ID: <sashiko-outbox-204480@kernel.org> (raw)
In-Reply-To: <20261109055204.31673-1-0xbeac@gmail.com>
> keyctl_pkey_query(), keyctl_pkey_e_d_s() and keyctl_pkey_verify() check
> that key->type has the ->asym_*() method they need and call it later,
> without holding key->sem. A reference keeps the key alive, but does not
> pin the module that provides its type.
>
> When that module is unloaded, unregister_key_type() waits for the key GC
> to process every remaining key of the type. For each such key, the GC
> takes key->sem for writing, switches key->type to key_type_dead, whose
> ->asym_*() methods are NULL, and destroys the payload. If this happens
> between the check and the call, the keyctl calls a NULL method:
>
> KEYCTL_PKEY_SIGN task Module unload and key GC
> ------------------------ ------------------------
> keyctl_pkey_e_d_s()
> if (!key->type->asym_eds_op) unregister_key_type()
> [ ... ]
> against type removal").
>
> Fixes: 00d60fd3b932 ("KEYS: Provide keyctls to drive the new key type ops for asymmetric keys [ver #2]")
> Cc: stable@vger.kernel.org
> Signed-off-by: Yuansheng Yang <0xbeac@gmail.com>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261109055204.31673-1-0xbeac@gmail.com?part=1
next prev parent reply other threads:[~2026-11-09 6:02 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 3:29 [PATCH] KEYS: Protect pkey method checks against type removal BeaCox
2026-11-03 3:39 ` sashiko-bot
2026-11-03 15:17 ` Jarkko Sakkinen
2026-11-04 2:14 ` [PATCH v2] " BeaCox
2026-11-04 2:25 ` sashiko-bot
2026-11-04 14:49 ` Jarkko Sakkinen
2026-11-04 23:59 ` Jarkko Sakkinen
2026-11-05 2:24 ` Yuansheng Yang
2026-11-05 3:28 ` Jarkko Sakkinen
2026-11-05 4:38 ` [PATCH v3] " Yuansheng Yang
2026-11-05 4:48 ` sashiko-bot
2026-11-05 16:55 ` Jarkko Sakkinen
2026-11-05 19:36 ` [PATCH v4] " Yuansheng Yang
2026-11-05 19:48 ` sashiko-bot
2026-11-06 14:08 ` Jarkko Sakkinen
2026-11-08 12:59 ` Yuansheng Yang
2026-11-08 13:14 ` [PATCH v5] " Yuansheng Yang
2026-11-08 13:32 ` sashiko-bot
2026-11-08 15:45 ` Jarkko Sakkinen
2026-11-09 5:52 ` [PATCH v6] " Yuansheng Yang
2026-11-09 6:02 ` sashiko-bot [this message]
2026-11-09 15:04 ` Jarkko Sakkinen
2026-11-09 15:06 ` Jarkko Sakkinen
2026-11-10 1:49 ` Jarkko Sakkinen
2026-11-10 3:02 ` Yuansheng Yang
2026-11-10 3:02 ` [PATCH v7] " Yuansheng Yang
2026-11-10 3:06 ` Jarkko Sakkinen
2026-11-10 3:13 ` sashiko-bot
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=sashiko-outbox-204480@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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