[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230628140317.756e61d3@kernel.org>
Date: Wed, 28 Jun 2023 14:03:17 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>
Cc: Boris Pismenny <borisp@...dia.com>, John Fastabend
<john.fastabend@...il.com>, glider@...gle.com, herbert@...dor.apana.org.au,
linux-crypto@...r.kernel.org, syzkaller-bugs@...glegroups.com, syzbot
<syzbot+828dfc12440b4f6f305d@...kaller.appspotmail.com>, Eric Biggers
<ebiggers@...nel.org>, Aviad Yehezkel <aviadye@...dia.com>, Daniel Borkmann
<daniel@...earbox.net>, netdev@...r.kernel.org, "David S. Miller"
<davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>, Paolo Abeni
<pabeni@...hat.com>
Subject: Re: [PATCH] net: tls: enable __GFP_ZERO upon tls_init()
On Wed, 28 Jun 2023 22:48:01 +0900 Tetsuo Handa wrote:
> syzbot is reporting uninit-value at aes_encrypt(), for block cipher assumes
> that bytes to encrypt/decrypt is multiple of block size for that cipher but
> tls_alloc_encrypted_msg() is not initializing padding bytes when
> required_size is not multiple of block cipher's block size.
Sounds odd, so crypto layer reads beyond what we submitted as
the buffer? I don't think the buffer needs to be aligned, so
the missing bits may well fall into a different (unmapped?) page.
This needs more careful investigation. Always zeroing the input
is just covering up the real issue.
Powered by blists - more mailing lists