netdev - Re: BUG: unable to handle kernel NULL pointer dereference in cfg80211_wext

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: <CAMrEMU_a9evtp26tYB6VUxznmSmH98AmpP8xnejQr5bGTgE+8g@mail.gmail.com>
Date:   Fri, 10 Jan 2020 21:23:57 -0800
From:   Justin Capella <justincapella@...il.com>
To:     Johannes Berg <johannes@...solutions.net>
Cc:     syzbot <syzbot+34b582cf32c1db008f8e@...kaller.appspotmail.com>,
        "David S. Miller" <davem@...emloft.net>,
        LKML <linux-kernel@...r.kernel.org>,
        linux-wireless@...r.kernel.org, netdev@...r.kernel.org,
        syzkaller-bugs@...glegroups.com,
        Cody Schuffelen <schuffelen@...gle.com>
Subject: Re: BUG: unable to handle kernel NULL pointer dereference in cfg80211_wext_siwrts

I noticed pfifo_qdisc_ops is exported as default_qdisc_ops is it
possible this is how rdev->ops is NULL

Seems unlikely, but thought I'd point it out.


On Fri, Jan 10, 2020 at 11:13 AM Johannes Berg
<johannes@...solutions.net> wrote:
>
> On Fri, 2020-01-10 at 11:11 -0800, syzbot wrote:
> > Hello,
> >
> > syzbot found the following crash on:
> >
> > HEAD commit:    2f806c2a Merge branch 'net-ungraft-prio'
> > git tree:       net
> > console output: https://syzkaller.appspot.com/x/log.txt?x=1032069ee00000
> > kernel config:  https://syzkaller.appspot.com/x/.config?x=5c90cac8f1f8c619
> > dashboard link: https://syzkaller.appspot.com/bug?extid=34b582cf32c1db008f8e
> > compiler:       gcc (GCC) 9.0.0 20181231 (experimental)
> >
> > Unfortunately, I don't have any reproducer for this crash yet.
>
> It's quite likely also in virt_wifi, evidently that has some issues.
>
> Cody, did you take a look at the previous report by any chance?
>
> johannes
>