linux-kernel - Re: KASAN: use-after-free Read in hiddev

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CACT4Y+Ya-GEPAezCceKadsXGD0WdAHMeNH=hkkGaM50nP7S6ww@mail.gmail.com>
Date:   Mon, 27 Jan 2020 16:51:05 +0100
From:   Dmitry Vyukov <dvyukov@...gle.com>
To:     Dan Carpenter <dan.carpenter@...cle.com>
Cc:     syzkaller <syzkaller@...glegroups.com>,
        Hillf Danton <hdanton@...a.com>,
        syzbot <syzbot+106b378813251e52fc5e@...kaller.appspotmail.com>,
        Andrey Konovalov <andreyknvl@...gle.com>,
        Benjamin Tissoires <benjamin.tissoires@...hat.com>,
        Jiri Kosina <jikos@...nel.org>,
        "open list:HID CORE LAYER" <linux-input@...r.kernel.org>,
        LKML <linux-kernel@...r.kernel.org>,
        USB list <linux-usb@...r.kernel.org>,
        syzkaller-bugs <syzkaller-bugs@...glegroups.com>
Subject: Re: KASAN: use-after-free Read in hiddev_disconnect

On Mon, Jan 27, 2020 at 4:12 PM Dan Carpenter <dan.carpenter@...cle.com> wrote:
>
> One possible option would be to list the similar bugs at the start of
> the bug report.
>
> See also:
>
>         KASAN: use-after-free Write in hiddev_disconnect
>         https://syzkaller.appspot.com/bug?extid=784ccb935f9900cc7c9e
>
> Then we could just copy and paste to the "#syz dup:" command.  The
> bitmap_port_list() stuff was reported something like 15 times so it was
> really complicated to track.  Hopefully if it were easier to mark things
> as duplicate that would help.
>
> regards,
> dan carpenter

Interesting. This should be doable. I've filed
https://github.com/google/syzkaller/issues/1575 to keep track of this.
If it detects potential dups, then it could auto-dup as well, but it's
not completely trivial (some things are mentioned on the issue).
But note it won't help if the bug happens in different functions (e.g.
I think lots of bitmap_port_list were actually in different
functions). And this is also common for racy bugs -- a racy free
catches use in another thread at different locations.