From: Jann Horn <jannh@google.com>
To: Eric Biggers <ebiggers@kernel.org>
Cc: "open list:HARDWARE RANDOM NUMBER GENERATOR CORE"
<linux-crypto@vger.kernel.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
linux-hardening@vger.kernel.org,
Linux API <linux-api@vger.kernel.org>,
kernel list <linux-kernel@vger.kernel.org>,
Kees Cook <keescook@chromium.org>,
Elena Petrova <lenaptr@google.com>,
Vegard Nossum <vegard.nossum@oracle.com>,
"Gustavo A . R . Silva" <gustavoars@kernel.org>,
stable <stable@vger.kernel.org>,
syzbot <syzbot+92ead4eb8e26a26d465e@syzkaller.appspotmail.com>
Subject: Re: [PATCH] crypto: af_alg - avoid undefined behavior accessing salg_name
Date: Mon, 26 Oct 2020 23:40:12 +0100 [thread overview]
Message-ID: <CAG48ez2u-B_DQ5yyiexycTz6okQZvU0rB3+MG1nAFtoahfPa6Q@mail.gmail.com> (raw)
In-Reply-To: <20201026215658.GA185792@sol.localdomain>
On Mon, Oct 26, 2020 at 10:57 PM Eric Biggers <ebiggers@kernel.org> wrote:
> On Mon, Oct 26, 2020 at 10:23:35PM +0100, 'Jann Horn' via syzkaller-bugs wrote:
> > On Mon, Oct 26, 2020 at 9:08 PM Eric Biggers <ebiggers@kernel.org> wrote:
> > > Commit 3f69cc60768b ("crypto: af_alg - Allow arbitrarily long algorithm
> > > names") made the kernel start accepting arbitrarily long algorithm names
> > > in sockaddr_alg.
> >
> > That's not true; it's still limited by the size of struct
> > sockaddr_storage (128 bytes total for the entire address).
>
> Interesting, so the actual limit is 104 bytes. It seems like the intent of that
> commit was to make it unlimited, though...
>
> > If you make it longer, __copy_msghdr_from_user() will silently truncate the
> > size.
>
> That's used for sys_sendmsg(), which AFAICT isn't relevant here. sockaddr_alg
> is used with sys_bind(), which fails with EINVAL if the address is longer than
> sizeof(struct sockaddr_storage).
Ugh, of course you're right, sorry.
> However, since sys_sendmsg() is truncating overly-long addresses, it's probably
> the case that sizeof(struct sockaddr_storage) can never be increased in the
> future...
Eh, I think there'd probably be bigger issues with that elsewhere.
> > > This is broken because the kernel can access indices >= 64 in salg_name,
> > > which is undefined behavior -- even though the memory that is accessed
> > > is still located within the sockaddr structure. It would only be
> > > defined behavior if the array were properly marked as arbitrary-length
> > > (either by making it a flexible array, which is the recommended way
> > > these days, or by making it an array of length 0 or 1).
> > >
> > > We can't simply change salg_name into a flexible array, since that would
> > > break source compatibility with userspace programs that embed
> > > sockaddr_alg into another struct, or (more commonly) declare a
> > > sockaddr_alg like 'struct sockaddr_alg sa = { .salg_name = "foo" };'.
> > >
> > > One solution would be to change salg_name into a flexible array only
> > > when '#ifdef __KERNEL__'. However, that would keep userspace without an
> > > easy way to actually use the longer algorithm names.
> > >
> > > Instead, add a new structure 'sockaddr_alg_new' that has the flexible
> > > array field, and expose it to both userspace and the kernel.
> > > Make the kernel use it correctly in alg_bind().
> > [...]
> > > @@ -147,7 +147,7 @@ static int alg_bind(struct socket *sock, struct sockaddr *uaddr, int addr_len)
> > > const u32 allowed = CRYPTO_ALG_KERN_DRIVER_ONLY;
> > > struct sock *sk = sock->sk;
> > > struct alg_sock *ask = alg_sk(sk);
> > > - struct sockaddr_alg *sa = (void *)uaddr;
> > > + struct sockaddr_alg_new *sa = (void *)uaddr;
> > > const struct af_alg_type *type;
> > > void *private;
> > > int err;
> > > @@ -155,7 +155,11 @@ static int alg_bind(struct socket *sock, struct sockaddr *uaddr, int addr_len)
> > > if (sock->state == SS_CONNECTED)
> > > return -EINVAL;
> > >
> > > - if (addr_len < sizeof(*sa))
> > > + BUILD_BUG_ON(offsetof(struct sockaddr_alg_new, salg_name) !=
> > > + offsetof(struct sockaddr_alg, salg_name));
> > > + BUILD_BUG_ON(offsetof(struct sockaddr_alg, salg_name) != sizeof(*sa));
> > > +
> > > + if (addr_len < sizeof(*sa) + 1)
> > > return -EINVAL;
> > >
> > > /* If caller uses non-allowed flag, return error. */
> > > @@ -163,7 +167,7 @@ static int alg_bind(struct socket *sock, struct sockaddr *uaddr, int addr_len)
> > > return -EINVAL;
> > >
> > > sa->salg_type[sizeof(sa->salg_type) - 1] = 0;
> > > - sa->salg_name[sizeof(sa->salg_name) + addr_len - sizeof(*sa) - 1] = 0;
> > > + sa->salg_name[addr_len - sizeof(*sa) - 1] = 0;
> >
> > This looks like an out-of-bounds write in the case `addr_len ==
> > sizeof(struct sockaddr_storage)`.
Sorry, I've been unusually unconcentrated today. Sorry about the
noise, ignore what I said.
next prev parent reply other threads:[~2020-10-26 22:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <00000000000014370305b1c55370@google.com>
[not found] ` <202010162042.7C51549A16@keescook>
2020-10-17 6:20 ` UBSAN: array-index-out-of-bounds in alg_bind Jann Horn
[not found] ` <CACT4Y+bG=89ii+kzgGvNiZnB9ZEcAsy-3YofJeW5K_rynp_S7g@mail.gmail.com>
2020-10-17 11:02 ` Jann Horn
2020-10-17 14:41 ` Dmitry Vyukov
2020-10-26 20:07 ` [PATCH] crypto: af_alg - avoid undefined behavior accessing salg_name Eric Biggers
2020-10-26 21:21 ` Gustavo A. R. Silva
2020-10-26 23:10 ` Gustavo A. R. Silva
2020-10-26 23:40 ` Eric Biggers
2020-10-26 21:23 ` Jann Horn
2020-10-26 21:56 ` Eric Biggers
2020-10-26 22:40 ` Jann Horn [this message]
2020-11-06 7:01 ` Herbert Xu
2020-11-02 2:17 ` UBSAN: array-index-out-of-bounds in alg_bind syzbot
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=CAG48ez2u-B_DQ5yyiexycTz6okQZvU0rB3+MG1nAFtoahfPa6Q@mail.gmail.com \
--to=jannh@google.com \
--cc=ebiggers@kernel.org \
--cc=gustavoars@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=keescook@chromium.org \
--cc=lenaptr@google.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=syzbot+92ead4eb8e26a26d465e@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=vegard.nossum@oracle.com \
/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;
as well as URLs for NNTP newsgroup(s).