netdev - Re: [syzbot] KMSAN: uninit-value in ax88179_led

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <f468c651-4bc7-75f2-e5e3-2b88aaf37cb2@gmail.com>
Date:   Sat, 26 Mar 2022 15:10:54 +0300
From:   Pavel Skripkin <paskripkin@...il.com>
To:     David Kahurani <k.kahurani@...il.com>, davem@...emloft.net,
        jgg@...pe.ca, kuba@...nel.org, linux-kernel@...r.kernel.org,
        linux-usb@...r.kernel.org, netdev@...r.kernel.org,
        phil@...lpotter.co.uk, syzkaller-bugs@...glegroups.com,
        syzbot+d3dbdf31fbe9d8f5f311@...kaller.appspotmail.com,
        arnd@...db.de
Subject: Re: [syzbot] KMSAN: uninit-value in ax88179_led_setting

Hi David,

On 3/26/22 14:47, David Kahurani wrote:
> Same here. My apologies.
> 
> On Sat, Mar 26, 2022 at 2:28 PM David Kahurani <k.kahurani@...il.com> wrote:
>>
>> Hello,
>>
>> syzbot found the following issue on:
>>
>> HEAD commit: 85cfd6e539bd kmsan: core: delete kmsan_gup_pgd_range()
>> git tree: https://github.com/google/kmsan.git master
>> console output: https://syzkaller.appspot.com/x/log.txt?x=12d6c53c700000
>> kernel config: https://syzkaller.appspot.com/x/.config?x=b9807dd5b044fd7a
>> dashboard link: https://syzkaller.appspot.com/bug?extid=d3dbdf31fbe9d8f5f311
>> compiler: clang version 14.0.0 (/usr/local/google/src/llvm-git-monorepo 2b554920f11c8b763cd9ed9003f4e19b919b8e1f), GNU ld (GNU Binutils for Debian) 2.35.2
>>
>> Based off a previous patch to fix a similar issue.
>> -------------------------

Looks sane.

Can you, please, send it as proper patch with explanation in commit 
message and with a bit cutted log, since full ->probe() calltrace is not 
interesting :)




With regards,
Pavel Skripkin