All of lore.kernel.org
 help / color / mirror / Atom feed
From: Herbert Xu <herbert@gondor.apana.org.au>
To: Daehyeon Ko <4ncienth@gmail.com>
Cc: "David S . Miller" <davem@davemloft.net>,
	Stephan Mueller <smueller@chronox.de>,
	linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] crypto: algif_skcipher: rewind rounded output bytes
Date: Thu, 8 Oct 2026 19:36:50 +1100	[thread overview]
Message-ID: <asdWIprHmkPiPgKp@gondor.apana.org.au> (raw)
In-Reply-To: <20261004050946.3131044-1-4ncienth@gmail.com>

On Sun, Oct 04, 2026 at 02:09:46PM +0900, Daehyeon Ko wrote:
> af_alg_get_rsgl() advances the receive iterator by the unrounded RX
> scatterlist length.  For a continuing skcipher request,
> _skcipher_recvmsg() then rounds its local length down to a whole chunksize
> without restoring the iterator.
> 
> A later chunk starts after bytes which the provider never wrote, while the
> syscall returns only the processed length.  When copy_splice_read()
> supplies non-zeroed pages and publishes that return as a dense prefix, the
> gap exposes stale bytes from a previous page lifetime.
> 
> With unprivileged xts(aes), a 31-byte MSG_MORE request followed by one
> final byte advances a 47-byte destination while returning 32 bytes.  A
> hardened v7.2-rc5 image retained all 15 seeded stale bytes in 4,829 of
> 4,829 records.  With init_on_alloc enabled, all 72,345 gap bytes observed
> were zero.
> 
> Rewind the iterator by the tail excluded during rounding, before rejecting
> a zero processed length.  The crypto request uses only the rounded length;
> af_alg_free_resources() releases the entire RX list before another receive
> iteration.
> 
> The fixed target-like kernel returned byte-identical dense 48-byte output
> in 4,771 of 4,771 rounds.  The unmodified kernel returned the vulnerable
> 32-byte short record in 2,409 of 2,409 rounds.
> 
> Fixes: e870456d8e7c ("crypto: algif_skcipher - overhaul memory management")
> Cc: stable@vger.kernel.org
> Assisted-by: LLM
> Signed-off-by: Daehyeon Ko <4ncienth@gmail.com>
> ---
>  crypto/algif_skcipher.c | 8 ++++++--
>  1 file changed, 6 insertions(+), 2 deletions(-)

Patch applied.  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

      reply	other threads:[~2026-10-08  8:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-04  5:09 [PATCH] crypto: algif_skcipher: rewind rounded output bytes Daehyeon Ko
2026-10-08  8:36 ` Herbert Xu [this message]

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=asdWIprHmkPiPgKp@gondor.apana.org.au \
    --to=herbert@gondor.apana.org.au \
    --cc=4ncienth@gmail.com \
    --cc=davem@davemloft.net \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=smueller@chronox.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.