* [PATCH 6.1/6.6/6.12.y] crypto: rsa-pkcs1pad: Don't WARN on an empty digest
@ 2026-07-20 19:15 Doruk Tan Ozturk
2026-07-22 0:53 ` Sasha Levin
2026-07-27 10:29 ` Lukas Wunner
0 siblings, 2 replies; 6+ messages in thread
From: Doruk Tan Ozturk @ 2026-07-20 19:15 UTC (permalink / raw)
To: stable; +Cc: herbert, linux-crypto, linux-kernel, Doruk Tan Ozturk
KEYCTL_PKEY_VERIFY lets an unprivileged caller supply a zero-length
digest (in_len == 0). keyctl_pkey_params_get_2() accepts the zero
length and the request reaches pkcs1pad_verify(), where the empty
digest is rejected but only after being passed through
WARN_ON(!digest_size). The warning is therefore directly
user-triggerable, and on kernels built with panic_on_warn=1 an
unprivileged process can panic the machine -- a local denial of
service. Reproduced as UID 65534 in a setuid sandbox.
Keep rejecting the invalid request with -EINVAL, but do not emit a
warning for the user-controlled length.
Mainline does not contain this code path; commit 1e562deacecc
("crypto: rsassa-pkcs1 - Migrate to sig_alg backend") removed
pkcs1pad_verify() in v6.13-rc1. This is a minimal fix for the
affected stable branches. It applies as-is to 6.1.y, 6.6.y and
6.12.y (identical pkcs1pad_verify); the 5.10.y/5.15.y form is sent
as a separate patch due to the older req->dst_len spelling.
Found by 0sec automated security-research tooling (https://0sec.ai).
Fixes: c7381b012872 ("crypto: akcipher - new verify API for public key algorithms")
Cc: stable@vger.kernel.org
Assisted-by: 0sec:multi-model
Signed-off-by: Doruk Tan Ozturk <doruk@0sec.ai>
---
crypto/rsa-pkcs1pad.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/crypto/rsa-pkcs1pad.c b/crypto/rsa-pkcs1pad.c
index cd501195f34a..225fcc3377dd 100644
--- a/crypto/rsa-pkcs1pad.c
+++ b/crypto/rsa-pkcs1pad.c
@@ -557,7 +557,7 @@ static int pkcs1pad_verify(struct akcipher_request *req)
const unsigned int digest_size = req->dst_len;
int err;
- if (WARN_ON(req->dst) || WARN_ON(!digest_size) ||
+ if (WARN_ON(req->dst) || !digest_size ||
!ctx->key_size || sig_size != ctx->key_size)
return -EINVAL;
--
2.43.0
^ permalink raw reply related [flat|nested] 6+ messages in thread* Re: [PATCH 6.1/6.6/6.12.y] crypto: rsa-pkcs1pad: Don't WARN on an empty digest
2026-07-20 19:15 [PATCH 6.1/6.6/6.12.y] crypto: rsa-pkcs1pad: Don't WARN on an empty digest Doruk Tan Ozturk
@ 2026-07-22 0:53 ` Sasha Levin
2026-07-25 19:04 ` Doruk (0sec)
2026-07-27 10:29 ` Lukas Wunner
1 sibling, 1 reply; 6+ messages in thread
From: Sasha Levin @ 2026-07-22 0:53 UTC (permalink / raw)
To: stable; +Cc: Sasha Levin, herbert, linux-crypto, linux-kernel,
Doruk Tan Ozturk
> KEYCTL_PKEY_VERIFY lets an unprivileged caller supply a zero-length
> digest (in_len == 0). keyctl_pkey_params_get_2() accepts the zero
> length and the request reaches pkcs1pad_verify(), where the empty
> digest is rejected but only after being passed through
> WARN_ON(!digest_size).
[...]
> Mainline does not contain this code path; commit 1e562deacecc
> ("crypto: rsassa-pkcs1 - Migrate to sig_alg backend") removed
> pkcs1pad_verify() in v6.13-rc1. This is a minimal fix for the
> affected stable branches.
The fix looks correct to me and matches the mainline end state (the
sig_alg replacement rejects an empty digest with a plain -EINVAL and
no WARN). But since this is a stable-only patch with no upstream
commit to reference, I'd like a crypto maintainer ack before queueing
it.
--
Thanks,
Sasha
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: [PATCH 6.1/6.6/6.12.y] crypto: rsa-pkcs1pad: Don't WARN on an empty digest
2026-07-22 0:53 ` Sasha Levin
@ 2026-07-25 19:04 ` Doruk (0sec)
2026-07-26 23:14 ` Herbert Xu
0 siblings, 1 reply; 6+ messages in thread
From: Doruk (0sec) @ 2026-07-25 19:04 UTC (permalink / raw)
To: stable; +Cc: herbert, linux-crypto, linux-kernel, sashal
Hi Herbert,
Sasha reviewed this as matching mainline’s no-WARN/-EINVAL behavior
and asked for a crypto-maintainer Ack before queueing it. The patch
only removes WARN_ON() for the user-controlled empty digest; invalid
input remains rejected.
Would you be comfortable Acking the attached stable variants?
Thanks,
Doruk
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [PATCH 6.1/6.6/6.12.y] crypto: rsa-pkcs1pad: Don't WARN on an empty digest
2026-07-25 19:04 ` Doruk (0sec)
@ 2026-07-26 23:14 ` Herbert Xu
0 siblings, 0 replies; 6+ messages in thread
From: Herbert Xu @ 2026-07-26 23:14 UTC (permalink / raw)
To: Doruk (0sec), Lukas Wunner, Ignat Korchagin
Cc: stable, linux-crypto, linux-kernel, sashal
On Sat, Jul 25, 2026 at 02:04:14PM -0500, Doruk (0sec) wrote:
> Hi Herbert,
>
> Sasha reviewed this as matching mainline’s no-WARN/-EINVAL behavior
> and asked for a crypto-maintainer Ack before queueing it. The patch
> only removes WARN_ON() for the user-controlled empty digest; invalid
> input remains rejected.
>
> Would you be comfortable Acking the attached stable variants?
Forwarding to Lukas/Ignat for comment.
Thanks,
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [PATCH 6.1/6.6/6.12.y] crypto: rsa-pkcs1pad: Don't WARN on an empty digest
2026-07-20 19:15 [PATCH 6.1/6.6/6.12.y] crypto: rsa-pkcs1pad: Don't WARN on an empty digest Doruk Tan Ozturk
2026-07-22 0:53 ` Sasha Levin
@ 2026-07-27 10:29 ` Lukas Wunner
2026-07-27 22:19 ` Sasha Levin
1 sibling, 1 reply; 6+ messages in thread
From: Lukas Wunner @ 2026-07-27 10:29 UTC (permalink / raw)
To: Doruk Tan Ozturk
Cc: stable, herbert, linux-crypto, linux-kernel, Ignat Korchagin
On Mon, Jul 20, 2026 at 09:15:25PM +0200, Doruk Tan Ozturk wrote:
> KEYCTL_PKEY_VERIFY lets an unprivileged caller supply a zero-length
> digest (in_len == 0). keyctl_pkey_params_get_2() accepts the zero
> length and the request reaches pkcs1pad_verify(), where the empty
> digest is rejected but only after being passed through
> WARN_ON(!digest_size). The warning is therefore directly
> user-triggerable, and on kernels built with panic_on_warn=1 an
> unprivileged process can panic the machine -- a local denial of
> service. Reproduced as UID 65534 in a setuid sandbox.
>
> Keep rejecting the invalid request with -EINVAL, but do not emit a
> warning for the user-controlled length.
>
> Mainline does not contain this code path; commit 1e562deacecc
> ("crypto: rsassa-pkcs1 - Migrate to sig_alg backend") removed
> pkcs1pad_verify() in v6.13-rc1. This is a minimal fix for the
> affected stable branches. It applies as-is to 6.1.y, 6.6.y and
> 6.12.y (identical pkcs1pad_verify); the 5.10.y/5.15.y form is sent
> as a separate patch due to the older req->dst_len spelling.
>
> Found by 0sec automated security-research tooling (https://0sec.ai).
>
> Fixes: c7381b012872 ("crypto: akcipher - new verify API for public key algorithms")
> Cc: stable@vger.kernel.org
> Assisted-by: 0sec:multi-model
> Signed-off-by: Doruk Tan Ozturk <doruk@0sec.ai>
Reviewed-by: Lukas Wunner <lukas@wunner.de>
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: [PATCH 6.1/6.6/6.12.y] crypto: rsa-pkcs1pad: Don't WARN on an empty digest
2026-07-27 10:29 ` Lukas Wunner
@ 2026-07-27 22:19 ` Sasha Levin
0 siblings, 0 replies; 6+ messages in thread
From: Sasha Levin @ 2026-07-27 22:19 UTC (permalink / raw)
To: Doruk Tan Ozturk
Cc: Sasha Levin, stable, herbert, linux-crypto, linux-kernel,
Ignat Korchagin, Lukas Wunner
On Mon, Jul 27, 2026 at 12:29:58PM +0200, Lukas Wunner wrote:
>Reviewed-by: Lukas Wunner <lukas@wunner.de>
Thanks Lukas!
Queued for 6.1, 6.6 and 6.12, thanks.
--
Thanks,
Sasha
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2026-07-27 22:19 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-07-20 19:15 [PATCH 6.1/6.6/6.12.y] crypto: rsa-pkcs1pad: Don't WARN on an empty digest Doruk Tan Ozturk
2026-07-22 0:53 ` Sasha Levin
2026-07-25 19:04 ` Doruk (0sec)
2026-07-26 23:14 ` Herbert Xu
2026-07-27 10:29 ` Lukas Wunner
2026-07-27 22:19 ` Sasha Levin
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox