From: Eric Biggers <ebiggers3@gmail.com>
To: syzbot
<bot+0665d43fa62276c7a5e3372929aa0bab96260979@syzkaller.appspotmail.com>
Cc: davem@davemloft.net, linux-kernel@vger.kernel.org,
linux-sctp@vger.kernel.org, netdev@vger.kernel.org,
nhorman@tuxdriver.com, syzkaller-bugs@googlegroups.com,
vyasevich@gmail.com, lucien.xin@gmail.com
Subject: Re: KASAN: slab-out-of-bounds Read in sctp_send_reset_streams
Date: Wed, 31 Jan 2018 21:06:09 +0000 [thread overview]
Message-ID: <20180131210609.bdrbl3tblkcpvbvb@gmail.com> (raw)
In-Reply-To: <001a1140b830592056055fe5ec80@google.com>
On Sat, Dec 09, 2017 at 02:40:00AM -0800, syzbot wrote:
> Hello,
>
> syzkaller hit the following crash on
> 328b4ed93b69a6f2083d52f31a240a09e5de386a
> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/master
> compiler: gcc (GCC) 7.1.1 20170620
> .config is attached
> Raw console output is attached.
> C reproducer is attached
> syzkaller reproducer is attached. See https://goo.gl/kgGztJ
> for information about syzkaller reproducers
>
>
> =================================
> BUG: KASAN: slab-out-of-bounds in sctp_send_reset_streams+0xadf/0xc10
> net/sctp/stream.c:314
> Read of size 2 at addr ffff8801d8a6c048 by task syzkaller104411/3085
>
> CPU: 0 PID: 3085 Comm: syzkaller104411 Not tainted 4.15.0-rc2+ #119
> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
> Google 01/01/2011
> Call Trace:
> __dump_stack lib/dump_stack.c:17 [inline]
> dump_stack+0x194/0x257 lib/dump_stack.c:53
> print_address_description+0x73/0x250 mm/kasan/report.c:252
> kasan_report_error mm/kasan/report.c:351 [inline]
> kasan_report+0x25b/0x340 mm/kasan/report.c:409
> __asan_report_load2_noabort+0x14/0x20 mm/kasan/report.c:428
> sctp_send_reset_streams+0xadf/0xc10 net/sctp/stream.c:314
> sctp_setsockopt_reset_streams net/sctp/socket.c:3905 [inline]
> sctp_setsockopt+0x70d/0x5d50 net/sctp/socket.c:4195
> compat_sock_common_setsockopt+0x104/0x140 net/core/sock.c:2981
> C_SYSC_setsockopt net/compat.c:403 [inline]
> compat_SyS_setsockopt+0x17c/0x410 net/compat.c:386
> do_syscall_32_irqs_on arch/x86/entry/common.c:327 [inline]
> do_fast_syscall_32+0x3ee/0xf9d arch/x86/entry/common.c:389
> entry_SYSENTER_compat+0x51/0x60 arch/x86/entry/entry_64_compat.S:125
> RIP: 0023:0xf7f1bc79
> RSP: 002b:00000000ff9893bc EFLAGS: 00000282 ORIG_RAX: 000000000000016e
> RAX: ffffffffffffffda RBX: 0000000000000005 RCX: 0000000000000084
> RDX: 0000000000000077 RSI: 000000002018b000 RDI: 0000000000000008
> RBP: 000000000000001c R08: 0000000000000000 R09: 0000000000000000
> R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
> R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
>
> Allocated by task 3085:
> save_stack+0x43/0xd0 mm/kasan/kasan.c:447
> set_track mm/kasan/kasan.c:459 [inline]
> kasan_kmalloc+0xad/0xe0 mm/kasan/kasan.c:551
> __do_kmalloc mm/slab.c:3711 [inline]
> __kmalloc_track_caller+0x15e/0x760 mm/slab.c:3726
> memdup_user+0x2c/0x90 mm/util.c:164
> sctp_setsockopt_reset_streams net/sctp/socket.c:3897 [inline]
> sctp_setsockopt+0x6a6/0x5d50 net/sctp/socket.c:4195
> compat_sock_common_setsockopt+0x104/0x140 net/core/sock.c:2981
> C_SYSC_setsockopt net/compat.c:403 [inline]
> compat_SyS_setsockopt+0x17c/0x410 net/compat.c:386
> do_syscall_32_irqs_on arch/x86/entry/common.c:327 [inline]
> do_fast_syscall_32+0x3ee/0xf9d arch/x86/entry/common.c:389
> entry_SYSENTER_compat+0x51/0x60 arch/x86/entry/entry_64_compat.S:125
>
> Freed by task 16:
> save_stack+0x43/0xd0 mm/kasan/kasan.c:447
> set_track mm/kasan/kasan.c:459 [inline]
> kasan_slab_free+0x71/0xc0 mm/kasan/kasan.c:524
> __cache_free mm/slab.c:3491 [inline]
> kfree+0xca/0x250 mm/slab.c:3806
> selinux_cred_free+0x48/0x70 security/selinux/hooks.c:3814
> security_cred_free+0x48/0x80 security/security.c:995
> put_cred_rcu+0x106/0x400 kernel/cred.c:117
> __rcu_reclaim kernel/rcu/rcu.h:195 [inline]
> rcu_do_batch kernel/rcu/tree.c:2758 [inline]
> invoke_rcu_callbacks kernel/rcu/tree.c:3012 [inline]
> __rcu_process_callbacks kernel/rcu/tree.c:2979 [inline]
> rcu_process_callbacks+0xd74/0x17d0 kernel/rcu/tree.c:2996
> __do_softirq+0x29d/0xbb2 kernel/softirq.c:285
>
> The buggy address belongs to the object at ffff8801d8a6c040
> which belongs to the cache kmalloc-32 of size 32
> The buggy address is located 8 bytes inside of
> 32-byte region [ffff8801d8a6c040, ffff8801d8a6c060)
> The buggy address belongs to the page:
> page:000000006b05592a count:1 mapcount:0 mapping:000000001ca7267d
> index:0xffff8801d8a6cfc1
> flags: 0x2fffc0000000100(slab)
> raw: 02fffc0000000100 ffff8801d8a6c000 ffff8801d8a6cfc1 000000010000003f
> raw: ffffea000762f920 ffffea00076133e0 ffff8801db0001c0 0000000000000000
> page dumped because: kasan: bad access detected
>
> Memory state around the buggy address:
> ffff8801d8a6bf00: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
> ffff8801d8a6bf80: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
> > ffff8801d8a6c000: fb fb fb fb fc fc fc fc 00 fc fc fc fc fc fc fc
> ^
> ffff8801d8a6c080: fb fb fb fb fc fc fc fc 00 00 00 00 fc fc fc fc
> ffff8801d8a6c100: fb fb fb fb fc fc fc fc fb fb fb fb fc fc fc fc
> =================================
>
>
> ---
> This bug is generated by a dumb bot. It may contain errors.
> See https://goo.gl/tpsmEJ for details.
> Direct all questions to syzkaller@googlegroups.com.
> Please credit me with: Reported-by: syzbot <syzkaller@googlegroups.com>
>
> syzbot will keep track of this bug report.
> Once a fix for this bug is merged into any tree, reply to this email with:
> #syz fix: exact-commit-title
This crash is no longer occurring. I assume it was fixed by commit
2342b8d95bcae5 (thanks Xin!), so let's tell syzbot:
#syz fix: sctp: make sure stream nums can match optlen in sctp_setsockopt_reset_streams
- Eric
WARNING: multiple messages have this Message-ID (diff)
From: Eric Biggers <ebiggers3@gmail.com>
To: syzbot
<bot+0665d43fa62276c7a5e3372929aa0bab96260979@syzkaller.appspotmail.com>
Cc: davem@davemloft.net, linux-kernel@vger.kernel.org,
linux-sctp@vger.kernel.org, netdev@vger.kernel.org,
nhorman@tuxdriver.com, syzkaller-bugs@googlegroups.com,
vyasevich@gmail.com, lucien.xin@gmail.com
Subject: Re: KASAN: slab-out-of-bounds Read in sctp_send_reset_streams
Date: Wed, 31 Jan 2018 13:06:09 -0800 [thread overview]
Message-ID: <20180131210609.bdrbl3tblkcpvbvb@gmail.com> (raw)
In-Reply-To: <001a1140b830592056055fe5ec80@google.com>
On Sat, Dec 09, 2017 at 02:40:00AM -0800, syzbot wrote:
> Hello,
>
> syzkaller hit the following crash on
> 328b4ed93b69a6f2083d52f31a240a09e5de386a
> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/master
> compiler: gcc (GCC) 7.1.1 20170620
> .config is attached
> Raw console output is attached.
> C reproducer is attached
> syzkaller reproducer is attached. See https://goo.gl/kgGztJ
> for information about syzkaller reproducers
>
>
> ==================================================================
> BUG: KASAN: slab-out-of-bounds in sctp_send_reset_streams+0xadf/0xc10
> net/sctp/stream.c:314
> Read of size 2 at addr ffff8801d8a6c048 by task syzkaller104411/3085
>
> CPU: 0 PID: 3085 Comm: syzkaller104411 Not tainted 4.15.0-rc2+ #119
> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
> Google 01/01/2011
> Call Trace:
> __dump_stack lib/dump_stack.c:17 [inline]
> dump_stack+0x194/0x257 lib/dump_stack.c:53
> print_address_description+0x73/0x250 mm/kasan/report.c:252
> kasan_report_error mm/kasan/report.c:351 [inline]
> kasan_report+0x25b/0x340 mm/kasan/report.c:409
> __asan_report_load2_noabort+0x14/0x20 mm/kasan/report.c:428
> sctp_send_reset_streams+0xadf/0xc10 net/sctp/stream.c:314
> sctp_setsockopt_reset_streams net/sctp/socket.c:3905 [inline]
> sctp_setsockopt+0x70d/0x5d50 net/sctp/socket.c:4195
> compat_sock_common_setsockopt+0x104/0x140 net/core/sock.c:2981
> C_SYSC_setsockopt net/compat.c:403 [inline]
> compat_SyS_setsockopt+0x17c/0x410 net/compat.c:386
> do_syscall_32_irqs_on arch/x86/entry/common.c:327 [inline]
> do_fast_syscall_32+0x3ee/0xf9d arch/x86/entry/common.c:389
> entry_SYSENTER_compat+0x51/0x60 arch/x86/entry/entry_64_compat.S:125
> RIP: 0023:0xf7f1bc79
> RSP: 002b:00000000ff9893bc EFLAGS: 00000282 ORIG_RAX: 000000000000016e
> RAX: ffffffffffffffda RBX: 0000000000000005 RCX: 0000000000000084
> RDX: 0000000000000077 RSI: 000000002018b000 RDI: 0000000000000008
> RBP: 000000000000001c R08: 0000000000000000 R09: 0000000000000000
> R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
> R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
>
> Allocated by task 3085:
> save_stack+0x43/0xd0 mm/kasan/kasan.c:447
> set_track mm/kasan/kasan.c:459 [inline]
> kasan_kmalloc+0xad/0xe0 mm/kasan/kasan.c:551
> __do_kmalloc mm/slab.c:3711 [inline]
> __kmalloc_track_caller+0x15e/0x760 mm/slab.c:3726
> memdup_user+0x2c/0x90 mm/util.c:164
> sctp_setsockopt_reset_streams net/sctp/socket.c:3897 [inline]
> sctp_setsockopt+0x6a6/0x5d50 net/sctp/socket.c:4195
> compat_sock_common_setsockopt+0x104/0x140 net/core/sock.c:2981
> C_SYSC_setsockopt net/compat.c:403 [inline]
> compat_SyS_setsockopt+0x17c/0x410 net/compat.c:386
> do_syscall_32_irqs_on arch/x86/entry/common.c:327 [inline]
> do_fast_syscall_32+0x3ee/0xf9d arch/x86/entry/common.c:389
> entry_SYSENTER_compat+0x51/0x60 arch/x86/entry/entry_64_compat.S:125
>
> Freed by task 16:
> save_stack+0x43/0xd0 mm/kasan/kasan.c:447
> set_track mm/kasan/kasan.c:459 [inline]
> kasan_slab_free+0x71/0xc0 mm/kasan/kasan.c:524
> __cache_free mm/slab.c:3491 [inline]
> kfree+0xca/0x250 mm/slab.c:3806
> selinux_cred_free+0x48/0x70 security/selinux/hooks.c:3814
> security_cred_free+0x48/0x80 security/security.c:995
> put_cred_rcu+0x106/0x400 kernel/cred.c:117
> __rcu_reclaim kernel/rcu/rcu.h:195 [inline]
> rcu_do_batch kernel/rcu/tree.c:2758 [inline]
> invoke_rcu_callbacks kernel/rcu/tree.c:3012 [inline]
> __rcu_process_callbacks kernel/rcu/tree.c:2979 [inline]
> rcu_process_callbacks+0xd74/0x17d0 kernel/rcu/tree.c:2996
> __do_softirq+0x29d/0xbb2 kernel/softirq.c:285
>
> The buggy address belongs to the object at ffff8801d8a6c040
> which belongs to the cache kmalloc-32 of size 32
> The buggy address is located 8 bytes inside of
> 32-byte region [ffff8801d8a6c040, ffff8801d8a6c060)
> The buggy address belongs to the page:
> page:000000006b05592a count:1 mapcount:0 mapping:000000001ca7267d
> index:0xffff8801d8a6cfc1
> flags: 0x2fffc0000000100(slab)
> raw: 02fffc0000000100 ffff8801d8a6c000 ffff8801d8a6cfc1 000000010000003f
> raw: ffffea000762f920 ffffea00076133e0 ffff8801db0001c0 0000000000000000
> page dumped because: kasan: bad access detected
>
> Memory state around the buggy address:
> ffff8801d8a6bf00: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
> ffff8801d8a6bf80: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
> > ffff8801d8a6c000: fb fb fb fb fc fc fc fc 00 fc fc fc fc fc fc fc
> ^
> ffff8801d8a6c080: fb fb fb fb fc fc fc fc 00 00 00 00 fc fc fc fc
> ffff8801d8a6c100: fb fb fb fb fc fc fc fc fb fb fb fb fc fc fc fc
> ==================================================================
>
>
> ---
> This bug is generated by a dumb bot. It may contain errors.
> See https://goo.gl/tpsmEJ for details.
> Direct all questions to syzkaller@googlegroups.com.
> Please credit me with: Reported-by: syzbot <syzkaller@googlegroups.com>
>
> syzbot will keep track of this bug report.
> Once a fix for this bug is merged into any tree, reply to this email with:
> #syz fix: exact-commit-title
This crash is no longer occurring. I assume it was fixed by commit
2342b8d95bcae5 (thanks Xin!), so let's tell syzbot:
#syz fix: sctp: make sure stream nums can match optlen in sctp_setsockopt_reset_streams
- Eric
next prev parent reply other threads:[~2018-01-31 21:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-09 10:40 KASAN: slab-out-of-bounds Read in sctp_send_reset_streams syzbot
2017-12-09 11:35 ` Xin Long
2017-12-09 11:35 ` Xin Long
2017-12-09 11:58 ` Xin Long
2017-12-09 11:58 ` Xin Long
2018-01-31 21:06 ` Eric Biggers [this message]
2018-01-31 21:06 ` Eric Biggers
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=20180131210609.bdrbl3tblkcpvbvb@gmail.com \
--to=ebiggers3@gmail.com \
--cc=bot+0665d43fa62276c7a5e3372929aa0bab96260979@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sctp@vger.kernel.org \
--cc=lucien.xin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=vyasevich@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.