KASAN: vmalloc-out-of-bounds Read in bpf_trace_run1

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 376dcfe3 Merge branch 'bpf, sockmap: allow verdict only sk..
git tree: bpf-next
console output: https://syzkaller.appspot.com/x/log.txt?x=14c8d784500000
kernel config: https://syzkaller.appspot.com/x/.config?x=7b5cc8ec2218e99d
dashboard link: https://syzkaller.appspot.com/bug?extid=7caca50f0beefbe3f96b
compiler: gcc (GCC) 10.1.0-syz 20200507
CC: [and...@kernel.org a...@kernel.org b...@vger.kernel.org dan...@iogearbox.net da...@davemloft.net ha...@kernel.org john.fa...@gmail.com ka...@fb.com kps...@chromium.org ku...@kernel.org linux-...@vger.kernel.org mi...@redhat.com net...@vger.kernel.org ros...@goodmis.org songliu...@fb.com y...@fb.com net...@vger.kernel.org]

Unfortunately, I don't have any reproducer for this issue yet.

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+7caca5...@syzkaller.appspotmail.com

==================================================================
BUG: KASAN: vmalloc-out-of-bounds in __bpf_trace_run kernel/trace/bpf_trace.c:2045 [inline]
BUG: KASAN: vmalloc-out-of-bounds in bpf_trace_run1+0x3b0/0x3c0 kernel/trace/bpf_trace.c:2081
Read of size 8 at addr ffffc90000cb8030 by task syz-executor.2/20571

CPU: 0 PID: 20571 Comm: syz-executor.2 Not tainted 5.9.0-rc6-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x198/0x1fd lib/dump_stack.c:118
print_address_description.constprop.0.cold+0x5/0x497 mm/kasan/report.c:383
__kasan_report mm/kasan/report.c:513 [inline]
kasan_report.cold+0x1f/0x37 mm/kasan/report.c:530
__bpf_trace_run kernel/trace/bpf_trace.c:2045 [inline]
bpf_trace_run1+0x3b0/0x3c0 kernel/trace/bpf_trace.c:2081
__bpf_trace_block_plug+0x8b/0xc0 block/blk-core.c:870
trace_block_plug+0x165/0x2e0 include/trace/events/block.h:470
blk_mq_submit_bio+0xd3f/0x1760 block/blk-mq.c:2213
__submit_bio_noacct_mq block/blk-core.c:1180 [inline]
submit_bio_noacct+0xc78/0x12b0 block/blk-core.c:1213
submit_bio+0x263/0x5b0 block/blk-core.c:1283
ext4_io_submit+0x181/0x210 fs/ext4/page-io.c:382
ext4_writepages+0x91c/0x3960 fs/ext4/inode.c:2739
do_writepages+0xec/0x290 mm/page-writeback.c:2352
__filemap_fdatawrite_range+0x2a1/0x380 mm/filemap.c:422
file_write_and_wait_range+0x169/0x200 mm/filemap.c:761
ext4_sync_file+0x459/0x1090 fs/ext4/fsync.c:151
vfs_fsync_range+0x13a/0x220 fs/sync.c:200
generic_write_sync include/linux/fs.h:2747 [inline]
ext4_buffered_write_iter+0x34a/0x4a0 fs/ext4/file.c:276
ext4_file_write_iter+0x1f0/0x13f0 fs/ext4/file.c:660
call_write_iter include/linux/fs.h:1882 [inline]
new_sync_write+0x422/0x650 fs/read_write.c:503
vfs_write+0x5ad/0x730 fs/read_write.c:578
ksys_write+0x12d/0x250 fs/read_write.c:631
do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46
entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x45de59
Code: 0d b4 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 0f 83 db b3 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007fee376dbc78 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 000000000003ab40 RCX: 000000000045de59
RDX: 0000000000000006 RSI: 0000000020000340 RDI: 0000000000000006
RBP: 000000000118bf60 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 000000000118bf2c
R13: 00007ffeee01383f R14: 00007fee376dc9c0 R15: 000000000118bf2c


Memory state around the buggy address:
ffffc90000cb7f00: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8
ffffc90000cb7f80: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8
>ffffc90000cb8000: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8
^
ffffc90000cb8080: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8
ffffc90000cb8100: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8
==================================================================


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

[syzbot]

Sending this report upstream.