linux-kernel - Re: INFO: trying to register non-static key in uhid_char

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]

Date:   Wed, 11 Nov 2020 14:21:01 +0100
From:   Dmitry Vyukov <dvyukov@...gle.com>
To:     syzbot <syzbot+8357fbef0d7bb602de45@...kaller.appspotmail.com>,
        "open list:HID CORE LAYER" <linux-input@...r.kernel.org>,
        LKML <linux-kernel@...r.kernel.org>,
        syzkaller-bugs <syzkaller-bugs@...glegroups.com>
Subject: Re: INFO: trying to register non-static key in uhid_char_release

On Wed, Oct 7, 2020 at 7:01 PM syzbot
<syzbot+8357fbef0d7bb602de45@...kaller.appspotmail.com> wrote:
>
> syzbot suspects this issue was fixed by commit:
>
> commit bce1305c0ece3dc549663605e567655dd701752c
> Author: Marc Zyngier <maz@...nel.org>
> Date:   Sat Aug 29 11:26:01 2020 +0000
>
>     HID: core: Correctly handle ReportSize being zero
>
> bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=12d19370500000
> start commit:   1127b219 Merge tag 'fallthrough-fixes-5.9-rc3' of git://gi..
> git tree:       upstream
> kernel config:  https://syzkaller.appspot.com/x/.config?x=891ca5711a9f1650
> dashboard link: https://syzkaller.appspot.com/bug?extid=8357fbef0d7bb602de45
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=102c472e900000
> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=13081056900000
>
> If the result looks correct, please mark the issue as fixed by replying with:
>
> #syz fix: HID: core: Correctly handle ReportSize being zero
>
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection

#syz fix: HID: core: Correctly handle ReportSize being zero