From: Greg KH <greg@kroah.com>
To: Connor O'Brien <connoro@google.com>
Cc: stable@vger.kernel.org, Daniel Borkmann <daniel@iogearbox.net>,
Alexei Starovoitov <ast@kernel.org>
Subject: Re: [PATCH] bpf: fix panic due to oob in bpf_prog_test_run_skb
Date: Wed, 15 Dec 2021 14:34:36 +0100 [thread overview]
Message-ID: <Ybnu7GMXglGpcU5A@kroah.com> (raw)
In-Reply-To: <20211215000310.113753-1-connoro@google.com>
On Wed, Dec 15, 2021 at 12:03:10AM +0000, Connor O'Brien wrote:
> From: Daniel Borkmann <daniel@iogearbox.net>
>
> commit 6e6fddc78323533be570873abb728b7e0ba7e024 upstream.
>
> sykzaller triggered several panics similar to the below:
>
> [...]
> [ 248.851531] BUG: KASAN: use-after-free in _copy_to_user+0x5c/0x90
> [ 248.857656] Read of size 985 at addr ffff8808017ffff2 by task a.out/1425
> [...]
> [ 248.865902] CPU: 1 PID: 1425 Comm: a.out Not tainted 4.18.0-rc4+ #13
> [ 248.865903] Hardware name: Supermicro SYS-5039MS-H12TRF/X11SSE-F, BIOS 2.1a 03/08/2018
> [ 248.865905] Call Trace:
> [ 248.865910] dump_stack+0xd6/0x185
> [ 248.865911] ? show_regs_print_info+0xb/0xb
> [ 248.865913] ? printk+0x9c/0xc3
> [ 248.865915] ? kmsg_dump_rewind_nolock+0xe4/0xe4
> [ 248.865919] print_address_description+0x6f/0x270
> [ 248.865920] kasan_report+0x25b/0x380
> [ 248.865922] ? _copy_to_user+0x5c/0x90
> [ 248.865924] check_memory_region+0x137/0x190
> [ 248.865925] kasan_check_read+0x11/0x20
> [ 248.865927] _copy_to_user+0x5c/0x90
> [ 248.865930] bpf_test_finish.isra.8+0x4f/0xc0
> [ 248.865932] bpf_prog_test_run_skb+0x6a0/0xba0
> [...]
>
> After scrubbing the BPF prog a bit from the noise, turns out it called
> bpf_skb_change_head() for the lwt_xmit prog with headroom of 2. Nothing
> wrong in that, however, this was run with repeat >> 0 in bpf_prog_test_run_skb()
> and the same skb thus keeps changing until the pskb_expand_head() called
> from skb_cow() keeps bailing out in atomic alloc context with -ENOMEM.
> So upon return we'll basically have 0 headroom left yet blindly do the
> __skb_push() of 14 bytes and keep copying data from there in bpf_test_finish()
> out of bounds. Fix to check if we have enough headroom and if pskb_expand_head()
> fails, bail out with error.
>
> Another bug independent of this fix (but related in triggering above) is
> that BPF_PROG_TEST_RUN should be reworked to reset the skb/xdp buffer to
> it's original state from input as otherwise repeating the same test in a
> loop won't work for benchmarking when underlying input buffer is getting
> changed by the prog each time and reused for the next run leading to
> unexpected results.
>
> Fixes: 1cf1cae963c2 ("bpf: introduce BPF_PROG_TEST_RUN command")
> Reported-by: syzbot+709412e651e55ed96498@syzkaller.appspotmail.com
> Reported-by: syzbot+54f39d6ab58f39720a55@syzkaller.appspotmail.com
> Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
> Signed-off-by: Alexei Starovoitov <ast@kernel.org>
> [connoro: drop test_verifier.c changes not applicable to 4.14]
> Signed-off-by: Connor O'Brien <connoro@google.com>
> ---
> Hello,
>
> This is a backport for the 4.14 stable tree.
Now queued up, thanks.
greg k-h
prev parent reply other threads:[~2021-12-15 13:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-15 0:03 [PATCH] bpf: fix panic due to oob in bpf_prog_test_run_skb Connor O'Brien
2021-12-15 13:34 ` Greg KH [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=Ybnu7GMXglGpcU5A@kroah.com \
--to=greg@kroah.com \
--cc=ast@kernel.org \
--cc=connoro@google.com \
--cc=daniel@iogearbox.net \
--cc=stable@vger.kernel.org \
/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