Re: [syzbot] [usb?] kernel BUG in register_netdevice

On Wed, Aug 19, 2026 at 11:59:05PM -0700, syzbot wrote:
> syzbot has bisected this issue to:
> 
> commit 425b9c7f51c98443db71ad679893725483b21196
> Author: Vasily Averin <[email protected]>
> Date:   Mon May 2 12:15:51 2022 +0000
> 
>     memcg: accounting for objects allocated for new netdevice
> 
> bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=1212ba25580000
> start commit:   e8bf40d15402 Merge tag 'chrome-platform-firmware-v7.3' of ..
> git tree:       upstream
> final oops:     https://syzkaller.appspot.com/x/report.txt?x=1112ba25580000
> console output: https://syzkaller.appspot.com/x/log.txt?x=1612ba25580000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=46f568dd8d795f6
> dashboard link: https://syzkaller.appspot.com/bug?extid=85ede281798faf736677
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=156b2549580000
> 
> Reported-by: [email protected]
> Fixes: 425b9c7f51c9 ("memcg: accounting for objects allocated for new netdevice")
> 
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection
> 

I strongly doubt this bisection.

Note, syzbot has gone on a tear lately with USB "issues", what happened
to suddenly cause this?  Did some new functionality get added to it such
that it is wanting to stress-test the bind/unbind racing with gadget
device setup suddenly?  What changed to start all of these reports?

thanks,

greg k-h