From: Oliver Neukum <oneukum@suse.com>
To: syzbot <syzbot+ef5de9c4f99c4edb4e49@syzkaller.appspotmail.com>,
andreyknvl@google.com, syzkaller-bugs@googlegroups.com,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: KASAN: use-after-free Read in usbhid_power
Date: Wed, 24 Jul 2019 16:17:35 +0200 [thread overview]
Message-ID: <1563977855.4670.8.camel@suse.com> (raw)
In-Reply-To: <000000000000bb4247058e589a20@google.com>
Am Dienstag, den 23.07.2019, 05:48 -0700 schrieb syzbot:
>
> Freed by task 243:
> save_stack+0x1b/0x80 /mm/kasan/common.c:71
> set_track /mm/kasan/common.c:79 [inline]
> __kasan_slab_free+0x130/0x180 /mm/kasan/common.c:451
> slab_free_hook /mm/slub.c:1421 [inline]
> slab_free_freelist_hook /mm/slub.c:1448 [inline]
> slab_free /mm/slub.c:2994 [inline]
> kfree+0xd7/0x280 /mm/slub.c:3949
> skb_free_head+0x8b/0xa0 /net/core/skbuff.c:588
> skb_release_data+0x41f/0x7c0 /net/core/skbuff.c:608
> skb_release_all+0x46/0x60 /net/core/skbuff.c:662
> __kfree_skb /net/core/skbuff.c:676 [inline]
> consume_skb /net/core/skbuff.c:736 [inline]
> consume_skb+0xc0/0x2f0 /net/core/skbuff.c:730
> skb_free_datagram+0x16/0xf0 /net/core/datagram.c:328
> netlink_recvmsg+0x65e/0xea0 /net/netlink/af_netlink.c:2001
> sock_recvmsg_nosec /net/socket.c:877 [inline]
> sock_recvmsg /net/socket.c:894 [inline]
> sock_recvmsg+0xca/0x110 /net/socket.c:890
> ___sys_recvmsg+0x271/0x5a0 /net/socket.c:2448
> __sys_recvmsg+0xe9/0x1b0 /net/socket.c:2497
> do_syscall_64+0xb7/0x560 /arch/x86/entry/common.c:301
> entry_SYSCALL_64_after_hwframe+0x49/0xbe
How reliable is this trace? It seems very likely to me that this bug
is the same bug as
syzbot <syzbot+ded1794a717e3b235226@syzkaller.appspotmail.com>
KASAN: use-after-free Read in hidraw_ioctl
which shows a race with disconnect() instead of some networking code,
which I really cannot fathom.
Regards
Oliver
next prev parent reply other threads:[~2019-07-24 14:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-23 12:48 KASAN: use-after-free Read in usbhid_power syzbot
2019-07-24 14:17 ` Oliver Neukum [this message]
2019-07-24 14:24 ` Andrey Konovalov
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=1563977855.4670.8.camel@suse.com \
--to=oneukum@suse.com \
--cc=andreyknvl@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=syzbot+ef5de9c4f99c4edb4e49@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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).