Netdev Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Eric Biggers <ebiggers@kernel.org>
Cc: Jordy Zomer <jordy@pwning.systems>,
	netdev@vger.kernel.org, Herbert Xu <herbert@gondor.apana.org.au>,
	"David S. Miller" <davem@davemloft.net>,
	linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] crypto: ccm - avoid negative wrapping of integers
Date: Tue, 27 Jul 2021 07:38:09 +0200	[thread overview]
Message-ID: <YP+bwR/Nt/NRYeDz@kroah.com> (raw)
In-Reply-To: <YP+beE4NGUCDIQHR@kroah.com>

On Tue, Jul 27, 2021 at 07:36:56AM +0200, Greg Kroah-Hartman wrote:
> On Mon, Jul 26, 2021 at 10:18:47AM -0700, Eric Biggers wrote:
> > On Mon, Jul 26, 2021 at 07:01:20PM +0200, Jordy Zomer wrote:
> > > Set csize to unsigned int to avoid it from wrapping as a negative number (since format input sends an unsigned integer to this function). This would also result in undefined behavior in the left shift when msg len is checked, potentially resulting in a buffer overflow in the memcpy call.
> > > 
> > > Signed-off-by: Jordy Zomer <jordy@pwning.systems>
> > > ---
> > > To address was corrected, and ccm was added to the topic to indicate that this is just for ccm.
> > > 
> > >  crypto/ccm.c | 2 +-
> > >  1 file changed, 1 insertion(+), 1 deletion(-)
> > > 
> > > diff --git a/crypto/ccm.c b/crypto/ccm.c
> > > index 6b815ece51c6..e14201edf9db 100644
> > > --- a/crypto/ccm.c
> > > +++ b/crypto/ccm.c
> > > @@ -66,7 +66,7 @@ static inline struct crypto_ccm_req_priv_ctx *crypto_ccm_reqctx(
> > >  	return (void *)PTR_ALIGN((u8 *)aead_request_ctx(req), align + 1);
> > >  }
> > >  
> > > -static int set_msg_len(u8 *block, unsigned int msglen, int csize)
> > > +static int set_msg_len(u8 *block, unsigned int msglen, unsigned int csize)
> > >  {
> > >  	__be32 data;
> > 
> > This isn't necessarily a bad change, but the value of csize is clearly in
> > [1, 256] if you read format_input(), and in fact is in [2, 8] if you read the
> > whole file, so please don't claim this is actually fixing anything, as it's not.
> 
> Oh that was not obvious at all, I looked at that for a long time and
> missed the place where this was checked earlier.  Perhaps just make
> csize here a u8 and that would take away all question about what is
> happening?

And part of this effort is to make it obvious that there is no overflow
happening, to allow tools to check this type of thing.  When you have to
work backwards long long ways like this, it makes automatic auditing
almost impossible, along with manual auditing like I tried to do :)

thanks,

greg k-h

      reply	other threads:[~2021-07-27  5:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-26 17:01 Jordy Zomer
2021-07-26 17:18 ` Eric Biggers
2021-07-27  5:36   ` Greg Kroah-Hartman
2021-07-27  5:38     ` Greg Kroah-Hartman [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=YP+bwR/Nt/NRYeDz@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=davem@davemloft.net \
    --cc=ebiggers@kernel.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=jordy@pwning.systems \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --subject='Re: [PATCH v2] crypto: ccm - avoid negative wrapping of integers' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).